How to translate video in HeyGen

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
Video URL video_url	string	Required	Video URL (required)
Output Language output_language	string	Required	Spanish, French, Hindi, …
Title title	string	Optional	Title

Sample request

{
  "video_url": "e.g. https://example.com/path",
  "output_language": "Spanish, French, Hindi, …",
  "title": "{{trigger.title}}"
}

Returns

{
  "data": {
    "video_translate_id": "tr_abc"
  },
  "error": null
}

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

FAQ

Questions about Translate Video.

What does the Translate Video action do in HeyGen?

Takes a source video and target language, produces a localised version with lip-sync re-aligned to the new audio. The HeyGen differentiator — best-in-class video translation for global content workflows.

What inputs does Translate Video require?

Required: Video URL, Output Language. 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 HeyGen 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 Translate Video support batch operations?

Yes. Run Translate Video inside a Loop node to process arrays. TinyCommand handles HeyGen's rate limits automatically so you don't have to throttle manually.

More actions