RSS to HeyGen, daily avatar news videos ready

Daily news videos sound simple until you’re doing the same copy-paste routine every morning. Pull headlines, rewrite summaries, format scripts, open HeyGen, paste again, fix a missing line, re-export. It’s repetitive work that’s weirdly easy to mess up when you’re rushing.

This RSS HeyGen automation hits content creators hardest, but marketing leads and small newsroom teams feel it too. If you’re trying to publish daily (or even a few times a week), consistency becomes the problem, not creativity.

This workflow takes an RSS feed and turns each news summary into a HeyGen avatar video request. You’ll see what it automates, what you need to run it, and where to tweak it so the output matches your channel.

How This Automation Works

See how this solves the problem:

n8n Workflow Template: RSS to HeyGen, daily avatar news videos ready

Click to explore

flowchart LR

    subgraph sg0["When clicking ‘Execute workflow’ Flow"]
        direction LR
        n0@{ icon: "mdi:play-circle", form: "rounded", label: "When clicking ‘Execute workf..", pos: "b", h: 48 }
        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/httprequest.dark.svg' width='40' height='40' /></div><br/>Generate Video News"]
        n2@{ icon: "mdi:cog", form: "rounded", label: "Read RSS Feed from Prothom Alo", pos: "b", h: 48 }
        n2 --> n1
        n0 --> n2
    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 n0 trigger
    class n1 api
    classDef customIcon fill:none,stroke:none
    class n1 customIcon

The Challenge: Daily News Videos Become a Copy-Paste Job

If you publish “today’s headlines” style videos, you’re basically running a tiny production line. The inputs change daily, but the steps don’t. You hunt for headlines, grab a summary, paste it into a script, then rebuild the same HeyGen settings for avatar, voice, and video size. Miss one detail and you get a video that’s off-brand, cut short, or simply wrong. The worst part is the mental load: you’re thinking about quality while your hands do repetitive admin work.

And when you try to speed up, the friction compounds. Here’s where it breaks down.

Manual copying from RSS pages into HeyGen invites small errors that turn into re-renders.
Keeping a consistent format across daily updates is hard when you’re rebuilding the same request every time.
Batching multiple headlines takes forever because each item becomes its own little set of steps.
You end up spending your best hours on production glue instead of picking better stories or improving the hook.

The Fix: Automatically Turn RSS Summaries Into HeyGen Video Requests

This n8n workflow reads a live RSS feed (in this case, Prothom Alo’s Bangla feed) and pulls the most recent items, including each item’s summary. For every news item, it sends an automated request to the HeyGen video API, using that summary as the narration/script input. Instead of rebuilding the same HeyGen setup daily, you standardize it once in the request body: avatar, voice, and video dimensions (like 1280×720) stay consistent. Then you run the workflow and HeyGen returns a video generation response you can use for the next step in your publishing pipeline.

The workflow starts with a manual trigger inside n8n. From there, it fetches RSS headlines and passes each summary into a HeyGen API request. The output is a reliable “video job created” response per item, so you can publish faster and with fewer do-overs.

What Changes: Before vs. After

What This Eliminates

Impact You’ll See

Copying each RSS summary into a new HeyGen project by hand.
Re-selecting avatar, voice, and video size every time you create a video.
Rechecking the RSS feed manually to see what’s new.
Accidental formatting changes that creep in when you’re moving fast.

Most teams get about 1 hour back on a “daily update” day.
Videos follow the same template, which makes your channel look tighter.
Fewer re-renders because the workflow sends the same clean structure each time.
You can generate several headline videos in one run instead of restarting the process.
It becomes easier to add publishing steps later (YouTube, Drive, Blotato) without rethinking the core flow.

Real-World Impact

Say you turn 6 RSS items into 6 short avatar videos each morning. Manually, you’ll spend maybe 10 minutes per item copying text, setting voice/avatar, and double-checking settings, which is about 1 hour of repetitive work. With this workflow, starting the run takes about 2 minutes, and the rest is HeyGen processing time while you do something else. You still review the results, but you’re no longer stuck doing the same setup steps six times.

Requirements

n8n instance (try n8n Cloud free)
Self-hosting option if you prefer (Hostinger works well)
HeyGen for avatar video generation via API
RSS feed URL to pull news items from XML
HeyGen API key (get it from your HeyGen dashboard)

Skill level: Intermediate. You’ll paste an API key, confirm the RSS fields, and adjust a request body safely.

Need help implementing this? Talk to an automation expert (free 15-minute consultation).

The Workflow Flow

Manual launch inside n8n. You click run when you’re ready, which is handy if you want a quick review step before generating videos (and it’s easy to swap to a scheduled trigger later).

RSS headlines are fetched. n8n reads the RSS feed and pulls items like title and summary. This workflow is set up for Prothom Alo’s Bangla RSS feed, but it can use any RSS feed that exposes a summary field.

HeyGen receives a video request for each item. The workflow sends an HTTP request to HeyGen’s API and maps the RSS summary into the request body (using the summary field from each RSS item). Your avatar, voice, and video dimensions are defined here, so the style stays consistent.

A generation response comes back. HeyGen returns the response for the created video job, which you can log, poll for completion, or hand off to the next automation that uploads to your platforms.

You can easily modify the RSS source to another publication based on your needs. See the full implementation guide below for customization options.

Step-by-Step Implementation Guide

Step 1: Configure the Manual Trigger

Start by setting up the manual trigger so you can run the workflow on demand while testing.

Add the Manual Launch Trigger node to the canvas.
Leave all fields at their defaults (no parameters are required for this trigger).
Connect Manual Launch Trigger to Fetch RSS Headlines.

Step 2: Connect RSS Feed Data

Pull the latest news items from the RSS feed to use as input for video generation.

Select the Fetch RSS Headlines node.
Set the URL field to https://prod-qt-images.s3.amazonaws.com/production/prothomalo-bangla/feed.xml.
Verify the execution flow: Manual Launch Trigger → Fetch RSS Headlines → HeyGen Video Request.

If the RSS feed is unreachable, the next node won’t receive summary data. Test the RSS URL in a browser first to confirm it returns items.

Step 3: Configure the Video Generation Request

Send the RSS summary text to HeyGen’s API to generate a video with an avatar and voice.

Open the HeyGen Video Request node.
Set the URL to https://api.heygen.com/v2/video/generate.
Set the Method to POST.
Enable Send Body and Send Headers.
Set Specify Body to JSON.
In JSON Body, paste the exact payload: ={ "video_inputs": [ { "character": { "type": "avatar", "avatar_id": "Lina_Dress_Sitting_Side_public", "avatar_style": "normal" }, "voice": { "type": "text", "input_text": "{{ $json.summary }}", "voice_id": "119caed25533477ba63822d5d1552d25", "speed": 1.1 } } ], "dimension": { "width": 1280, "height": 720 } }
Under Header Parameters, add X-Api-Key and paste your HeyGen API key as the value.
Confirm the Content-Type header value is application/json.

⚠️ Common Pitfall: The X-Api-Key header must have your valid HeyGen API key. If it’s blank, the request will fail with an authorization error.

Step 4: Test and Activate Your Workflow

Run a manual test to confirm the RSS data is pulled and the video generation request succeeds.

Click Execute Workflow to run Manual Launch Trigger.
Check that Fetch RSS Headlines outputs items with a summary field.
Open the output of HeyGen Video Request and confirm a successful API response from HeyGen.
Once validated, toggle the workflow to Active for production use (then replace the manual trigger with a scheduled trigger if needed).

🔒

Unlock Full Step-by-Step Guide

Get the complete implementation guide + downloadable template

Watch Out For

HeyGen credentials can expire or need specific permissions. If things break, check your HeyGen API key status in the HeyGen dashboard 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.

Common Questions

How quickly can I implement this RSS HeyGen automation?

About 30 minutes if you already have your HeyGen API key.

Can non-technical teams implement this RSS HeyGen automation?

Yes, but you’ll want someone comfortable pasting API keys and testing a run. No coding, just careful setup and a quick review of the RSS fields.

Is n8n free to use for this RSS HeyGen automation workflow?

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 how many videos you generate.

Where can I host n8n to run this automation?

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.

How do I adapt this RSS HeyGen automation solution to my specific challenges?

You can swap the RSS feed URL in the RSS Read node to use a different publisher, as long as it outputs a usable summary field. In the HeyGen HTTP Request node, change the avatar ID and voice ID to match your channel’s style, then adjust video dimensions if you’re targeting vertical platforms. Common tweaks include limiting how many RSS items you process per run, adding a review step via Gmail, or logging responses to Google Sheets so you can track what was generated.

Why is my HeyGen connection failing in this workflow?

Usually it’s an expired or incorrect X-Api-Key header value in the HTTP Request node. Regenerate your HeyGen API key in your HeyGen dashboard and update it in n8n, then run a single-item test from the RSS output. If it still fails, check that your HeyGen plan includes API access and that you haven’t hit usage limits for the day. Also confirm the workflow is sending a real summary value; empty summaries can cause request validation errors.

What’s the capacity of this RSS HeyGen automation solution?

It depends on your n8n plan and your HeyGen API limits. On n8n Cloud Starter, you can run a healthy number of daily executions for a small content operation; higher tiers handle more volume. If you self-host, there’s no execution cap from n8n, but your server resources still matter. In practice, generating videos is usually the bottleneck because HeyGen processing takes time per item.

Is this RSS HeyGen automation better than using Zapier or Make?

For this workflow, n8n has a few advantages: more complex logic with unlimited branching at no extra cost, a self-hosting option for unlimited executions, and native HTTP request flexibility that many Zapier setups gate behind higher tiers. Zapier or Make can still work if you only want a very simple “RSS in, webhook out” flow. Where they tend to get annoying is when you need better control over request bodies, error handling, or batching multiple items. If you’re unsure, Talk to an automation expert and we’ll map the simplest path for your exact stack.

Once this is running, “daily avatar news video” stops being a production task and turns into a quick review step. The workflow handles the repetitive parts so you can focus on what actually makes people watch.

RSS to HeyGen, daily avatar news videos ready

How This Automation Works

n8n Workflow Template: RSS to HeyGen, daily avatar news videos ready

The Challenge: Daily News Videos Become a Copy-Paste Job