ActionD-IDUpdated May 2026

How do I retrieve a D-ID clip result?

Short answer: Drop the "D-ID → Get Clip Result" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Use this action All 6 D-ID actions

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 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 Get Clip Result support batch operations?

Yes. Run Get Clip Result inside a Loop node to process arrays. Tiny Command handles D-ID's rate limits automatically so you don't have to throttle manually.

More actions