Automated HeyGen Video Localisation Batches
When you hand over an approved video, WebRun opens HeyGen, runs the video translation into each language on your market list, waits for every version to finish rendering, collects the share links, posts the set to Slack for review, and drafts a handover email to the regional owners for you to approve.
How do I create localised versions of a video for each market?
Hand WebRun an approved video and it opens HeyGen, runs the translation into every language on your market list, and waits for each version to render. It posts the finished links to Slack for a native speaker check and drafts a handover email per regional owner in Gmail, ready for you to send.
- One approved video becomes a full market set in a single run
- Failed translations are named instead of quietly missing
- Regional owners get their version with the link already attached
Built for marketing teams · content localisation managers · global growth teams · video producers
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
app.heygen.comin a real browser with your saved login - no setup, no API keys. -
1
HeyGen - translate into each market language
heygen.com
WebRun opens HeyGen to translate into each market language. - Open HeyGen and find the approved video you handed over
- Start a video translation for each language on your market list
- Wait for every version to finish rendering, then collect its share link and note any that failed
Done when Every requested language version has finished with a share link, or is listed as failed.
-
2
Slack - post the versions for review
slack.com
WebRun opens Slack to post the versions for review. - Post the finished set to your marketing channel, one line per language with its share link
- List any language that failed to render, with the reason shown by HeyGen
- Ask for a native speaker check before anything is published
Done when The full set of versions is in Slack awaiting review.
-
3
Gmail - draft the handover to regional owners
gmail.com
WebRun opens Gmail to draft the handover to regional owners. - Draft one email per regional owner with their language version and its share link
- Leave every email unsent in your drafts folder for you to review and send
- Note in each draft that the version still needs a native speaker check
Done when A handover email is drafted for every regional owner.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it publish or email the versions on its own?
No. WebRun posts the links to your internal Slack channel and leaves every handover email unsent in drafts. Publishing to a channel or sending to a regional owner stays your call.
What happens if a translation fails?
The failed language is named in the Slack post with the reason HeyGen gave, rather than being left out silently, so you know exactly which market is still missing a version.
Does it spend credits without warning?
It uses the languages on the market list you set, so the number of translations per run is known in advance. Change the list and the next run follows the new one.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.