Short answer: Drop the "HeyGen → Create HeyGen Video" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Avatar ID avatar_id | string | Required | HeyGen avatar id |
Voice ID voice_id | string | Required | HeyGen voice id |
Script input_text | string | Required | Script (required) |
Background Color background_color | string | Optional | Background Color |
Width width | string | Optional | Width |
Height height | string | Optional | Height |
{"avatar_id": "e.g. Daisy-inskirt-20220818","voice_id": "e.g. 1bd001e7e50f421d891986aad5158bc8","input_text": "{{trigger.input_text}}","background_color": "{{trigger.background_color}}","width": "{{trigger.width}}"}
{"data": {"video_id": "vid_abc123"},"error": null}
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.
Triggered by anything in the catalog. Free tier available. No credit card.