ActionD-IDUpdated September 2026

How do I retrieve a D-ID clip result?

Short answer: You can get clip result in D-ID by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the D-ID Get Clip Result action to a workflow, map its 1 input from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Get Clip Result in D-ID — start free All 6 D-ID actions

Get Clip Result in D-ID — start free

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
Clip ID clip_id	string	Required	Clip ID (required)

Sample request

{
  "clip_id": "{{trigger.clip_id}}"
}

Returns

{
  "id": "clp_abc",
  "status": "done",
  "duration": 8.5,
  "result_url": "https://x.com/v.mp4"
}

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

Triggered by

Apps that pair well as the trigger for Get Clip Result.

Any of these apps can fire this action as part of a workflow.

2 Google Sheets triggers

HubSpot → D-ID

18 HubSpot triggers

FAQ

Questions about Get Clip Result.

What does the Get Clip Result action do in D-ID?

Polls the clip ID for status; returns the result video URL once status is done. For production, configure D-ID's webhook on the generation request to skip polling.

What inputs does Get Clip Result require?

Required: Clip 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 D-ID returns an error?

The run history shows the failed step with its input and the error message D-ID returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does Get Clip Result support batch operations?

Run Get Clip Result inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within D-ID's rate limits.

More actions