HeyGen to YouTube, publish avatar videos hands free
Posting “simple” videos to YouTube shouldn’t require a mini checklist, three tabs, and a half hour of babysitting exports. But once you add AI avatar generation, render waiting, file downloads, and upload settings, the little tasks pile up fast.
Marketing managers feel it when a campaign needs steady weekly output. A solo creator feels it when consistency slips. And agency teams get stuck doing the same setup work for every client. This HeyGen YouTube automation turns one script into a published avatar video, without the repetitive steps.
You’ll see what the workflow does, what you need to run it, and how it cuts down mistakes while making “more posts” realistic again.
How This Automation Works
The full n8n workflow, from trigger to final output:
n8n Workflow Template: HeyGen to YouTube, publish avatar videos hands free
flowchart LR
subgraph sg0["Flow 1"]
direction LR
n0["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/webhook.dark.svg' width='40' height='40' /></div><br/>WebHook"]
n1["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/code.svg' width='40' height='40' /></div><br/>Code"]
n2@{ icon: "mdi:swap-vertical", form: "rounded", label: "Setup Heygen Parameters", pos: "b", h: 48 }
n3["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/httprequest.dark.svg' width='40' height='40' /></div><br/>Create Avatar Video (HeyGen)"]
n4@{ icon: "mdi:cog", form: "rounded", label: "Wait for Video (HeyGen)", pos: "b", h: 48 }
n5["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/httprequest.dark.svg' width='40' height='40' /></div><br/>Get Avatar Video Status (Hey.."]
n6@{ icon: "mdi:swap-horizontal", form: "rounded", label: "If Processing Completed", pos: "b", h: 48 }
n7["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/httprequest.dark.svg' width='40' height='40' /></div><br/>Download Video"]
n8@{ icon: "mdi:cog", form: "rounded", label: "Upload a video", pos: "b", h: 48 }
n1 --> n2
n0 --> n1
n7 --> n8
n6 --> n7
n6 --> n4
n2 --> n3
n4 --> n5
n3 --> n4
n5 --> n6
end
%% Styling
classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
classDef disabled stroke-dasharray: 5 5,opacity: 0.5
class n6 decision
class n0,n3,n5,n7 api
class n1 code
class n2 disabled
classDef customIcon fill:none,stroke:none
class n0,n1,n3,n5,n7 customIcon
The Problem: Avatar video publishing gets messy fast
Most teams don’t struggle with the “idea” part. They struggle with the grind that follows. You write a script, paste it into HeyGen, pick the avatar, pick the voice, wait for rendering, download the file, then upload to YouTube and hope you didn’t forget the category or set it to “Private” again. Do that a few times a week and you start delaying posts, batching work into long afternoons, or worse, skipping entirely because it feels like a chore.
It adds up fast. And the friction compounds once more than one person is involved.
- Rendering is unpredictable, so someone ends up checking status manually over and over.
- YouTube upload settings drift between videos, which makes your channel look inconsistent.
- Copy-paste formatting issues (extra newlines, weird spacing) sneak into the final narration.
- Publishing becomes a “last step” that gets postponed, even when the script is already done.
The Solution: Send a script, get a YouTube upload automatically
This workflow connects three things you already do into one reliable pipeline: receiving a script, generating the HeyGen avatar video, and uploading it to YouTube with consistent settings. It starts with a webhook, so your script can come from a form, a tool you already use, or even a simple “send JSON” action from another automation. n8n cleans the text (so narration doesn’t sound broken), then sends the right parameters to HeyGen, including your chosen avatar and voice IDs. After that, the workflow waits and checks render status until the video is ready, downloads the finished file, and publishes it to your YouTube channel.
The workflow starts when you send title and content to the webhook. HeyGen generates the video and n8n runs a wait-and-poll loop until rendering finishes. Finally, the YouTube node uploads the video using your default settings, so every post goes out the same way.
What You Get: Automation vs. Results
| What This Workflow Automates | Results You’ll Get |
|---|---|
|
|
Example: What This Looks Like
Say you publish 5 avatar videos a week. Manually, you might spend about 10 minutes prepping HeyGen, another 10 minutes checking back on rendering a few times, then 15 minutes handling download and YouTube upload details. That’s roughly 30–40 minutes per video, or about 3 hours a week. With this workflow, you submit the title and script in a quick webhook request (about 2 minutes), then you wait for processing in the background while n8n uploads automatically. You get those hours back without posting less.
What You’ll Need
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- HeyGen for avatar video generation
- YouTube to publish videos to your channel
- HeyGen API key (get it from your HeyGen dashboard)
Skill level: Intermediate. You’ll copy IDs/keys, connect YouTube OAuth, and test a webhook request.
Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).
How It Works
A webhook receives your video title and script. You send a simple payload (title + content) from wherever your scripts live, including other automations. It can be as basic as a POST request.
The script gets cleaned before it hits narration. The workflow removes messy newlines and formatting hiccups so your avatar doesn’t pause in weird places or read out awkward spacing.
HeyGen generates the avatar video and n8n waits intelligently. n8n submits your avatar ID, voice ID, and video settings to HeyGen, then checks render status in a loop. No hovering over a dashboard. Honestly, this is the part most people underestimate until they stop doing it manually.
The finished video is downloaded and uploaded to YouTube. Once HeyGen marks the render as complete, the workflow fetches the video file and publishes it to your connected channel with your configured defaults (category, region, visibility).
You can easily modify YouTube upload settings to match your content type based on your needs. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Webhook Trigger
Set up the inbound endpoint that will receive the script and title for video generation.
- Add the Inbound Webhook Trigger node and set HTTP Method to
POST. - Set Path to
52048302-06bd-4eae-9b004c5ed17d. - Send a JSON body with
body.titleandbody.contentfields when calling the webhook.
body.title and body.content before moving on.Step 2: Set Up Script Cleansing and HeyGen Inputs
Prepare clean text for HeyGen and provide required API inputs.
- In Cleanse Script Text, keep Mode as
Run Once for Each Itemand paste the provided JavaScript that removes line breaks. - Open Configure HeyGen Inputs and add fields for x-api-key, voice_id, and avatar_id as fixed values.
- Set title to
={{ $json.title }}and content to={{ $json.content }}. - Ensure Configure HeyGen Inputs is enabled (it is disabled in the workflow by default).
Step 3: Request and Poll HeyGen Rendering
Send the video generation request and loop until rendering completes.
- In Request HeyGen Video, set URL to
https://api.heygen.com/v2/video/generateand Method toPOST. - Set JSON Body to the provided template and ensure the expressions are preserved for
{{ $json.avatar_id }},{{ $json.content }}, and{{ $json.voice_id }}. - Add a header in Request HeyGen Video: X-Api-Key with value
={{ $json['x-api-key'] }}. - In Delay for Rendering, set Unit to
minutesand Amount to0.1for short polling intervals. - In Retrieve Render Status, set URL to
https://api.heygen.com/v1/video_status.get, enable Send Query, and add video_id as={{ $('Request HeyGen Video').item.json.data.video_id }}. - Add header X-Api-Key with value
={{ $('Configure HeyGen Inputs').item.json['x-api-key'] }}. - In Check Render Complete, set the condition to String notEquals with Left Value
={{ $json.data.status }}and Right Valueprocessing. - Confirm the routing: Check Render Complete sends the “true” output to Fetch Video File and the “false” output back to Delay for Rendering.
Step 4: Configure Upload to YouTube
Download the finished video file and upload it to YouTube with the correct metadata.
- In Fetch Video File, set URL to
={{ $json.data.video_url }}. - Open Upload to YouTube and set Resource to
videoand Operation toupload. - Set Title to
={{ $('Configure HeyGen Inputs').item.json.title }}. - Set Category ID to
28and Region Code toUS. - Credential Required: Connect your youTubeOAuth2Api credentials in Upload to YouTube.
Step 5: Test and Activate Your Workflow
Validate each stage of the workflow and then turn it on for production use.
- Click Execute Workflow and send a POST request to the Inbound Webhook Trigger with a sample
titleandcontent. - Verify that Request HeyGen Video returns a
video_idand that Retrieve Render Status eventually returns a status other thanprocessing. - Confirm Fetch Video File receives a valid
video_urland Upload to YouTube completes successfully. - Once the test run succeeds, toggle the workflow Active to enable production automation.
Common Gotchas
- YouTube OAuth2 credentials can expire or need specific permissions. If things break, check your n8n credential connection status and your Google Cloud project scopes first.
- If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
- Default prompts in AI nodes are generic. Add your brand voice early or you’ll be editing outputs forever.
Frequently Asked Questions
About 30 minutes if you already have your HeyGen API key and YouTube OAuth ready.
No. You’ll mostly paste in IDs/keys and connect your YouTube account. The only “technical” part is sending a webhook test payload, and you can copy one from the example.
Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in HeyGen API usage costs, which depend on video length and your plan.
Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.
Yes, but you’ll add one extra decision point. A common approach is to insert a Google Sheets or database check after the webhook, then only proceed when a “Ready” field is true, and finally set YouTube visibility to “Private” until you’re ready. You can also swap the webhook trigger for a schedule trigger if you want timed batches, while keeping the same HeyGen render loop and YouTube upload steps.
Usually it’s an invalid or expired HeyGen API key, or the key wasn’t actually sent in the request header. Confirm the x-api-key value in the “Configure HeyGen Inputs” step, then run a simple HeyGen “list avatars” request to verify your key works. If it still fails, check that your avatar_id and voice_id exist in your HeyGen account because copied IDs from another workspace will get rejected. Rate limits can also show up if you trigger lots of renders back-to-back.
On n8n Cloud, your limit is tied to monthly executions, and self-hosting has no fixed execution cap (it depends on your server). Practically, HeyGen rendering time is the real bottleneck, so most teams run this comfortably for daily posting and small batches.
Often, yes, because the wait-and-poll render loop is easier to run reliably in n8n without paying extra for complex branching. n8n also gives you more control over formatting the script and handling file downloads before upload. Zapier or Make can still work, but you may end up stitching together workarounds for the “check render status until complete” part. If you’re unsure, Talk to an automation expert and we’ll point you to the simplest option for your setup.
Once this is running, publishing stops being a separate job you have to remember. The workflow handles the repetitive parts so you can focus on the script, the series, and the next idea.
Need Help Setting This Up?
Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.
