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.
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) |
{"clip_id": "{{trigger.clip_id}}"}
{"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.
Any of these apps can fire this action as part of a workflow.