Shotstack Get Render Status: Shotstack action

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Render ID render_id	string	Required	The render ID returned by Render Video (`response.id` from that op).

Sample request

{
  "render_id": "e.g. 2abd5c11-0f3d-4c6d-9bff-abc123"
}

Returns

{
  "success": true,
  "response": {
    "id": "2abd5c11-0f3d-4c6d-9bff-abc123",
    "url": "https://shotstack-api-stage-output.s3-ap-southeast-2.amazonaws.com/.../output.mp4",
    "plan": "free",
    "owner": "5y...",
    "status": "done",
    "created": "2026-05-13T08:00:00.000Z",
    "updated": "2026-05-13T08:00:12.400Z",
    "duration": 5,
    "renderTime": 12.4
  }
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Shotstack Get Render Status.

What does the Shotstack Get Render Status action do in Shotstack?

Polls a render by ID; returns the finished MP4 URL when complete. Configure callback URL on Render Video for production push notification.

What inputs does Shotstack Get Render Status require?

Required: Render ID. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Shotstack returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Shotstack Get Render Status support batch operations?

Yes. Run Shotstack Get Render Status inside a Loop node to process arrays. Tiny Command handles Shotstack's rate limits automatically so you don't have to throttle manually.

More actions