Automated workflows for generating and translating video
Set the rule once — trigger, condition, action — and videos generate, translate and re-publish themselves. No code, and no opening the panel for every single clip.
What an automated workflow is made of
Generation triggers
A new catalog product, an updated procedure document or a new row in a prospect list starts the render.
Chained automatic translation
After the first render, the same lesson or presentation is dubbed automatically into the languages you picked.
Conditions that filter
Run the workflow only for a given avatar, only for one market, or only while you still have generations left this month.
Re-publishing over the existing version
A workflow can update an already published video while keeping its link and accumulated stats.
A run log
See every run, what triggered it, how long the render took and what got published in the end.
Test before you switch it on
Run the workflow against a single test item before turning it loose on the whole list.
You assemble the rule from three blocks: what triggers it — a new product, an updated document, an imported list — which conditions must hold, and what runs: render, translate, re-publish, notify. Workflows execute on the server, so they run when you're not in the panel, and the log shows every execution.
Frequently asked questions about automated workflows
Let the workflow render and translate for you
Build your first workflow for the material you regenerate most often.