video.from-script

To generate an MP4 from a script using HeyGen asynchronously, you provide an approved avatar source, voice id, and script text. The process starts an asynchronous render job, polls for status updates, and downloads the completed MP4 artifact directly to your workspace.

Starting a HeyGen avatar video render job requires exactly one avatar source (an avatar id, image URL, or image asset id), a specific voice id, and your approved script text. These validated inputs ensure safer rendering and prevent processing errors.

Asynchronous job polling for avatar video generation works by starting a render job and repeatedly checking its status until completion. Once the job reaches a completed state, the system surfaces the terminal status and retrieves the public HTTPS video URL.

Yes, downloading HeyGen MP4s requires a HybridClaw gateway secret injection for the HEYGEN_API_KEY. This setup validates job states, secures your input constraints, and prevents printing raw API keys while downloading completed public HTTPS video URLs.

Completed HeyGen avatar MP4 artifacts are saved under a workspace-relative .generated-videos directory. The system only downloads these artifacts when the asynchronous render job reaches completion, ensuring you have valid outputs for gateway preview workflows.

When an async HeyGen avatar render job fails, the system surfaces terminal failure details during the polling process. This mechanism stops the workflow, prevents downloading incomplete or invalid video URLs, and helps you diagnose the rendering issue.