Render whole batches of videos from Creatomate templates
Connect Creatomate to the AI agent: templates, template elements, render jobs and finished files. The agent batch-renders videos and images from your data.
How the agent works with Creatomate
The agent calls the Creatomate API with the project key and starts from the template list: for each one it goes through the elements and editable fields — headlines, prices, images, colours — so it knows exactly what can be filled in. The other half of the work is render jobs: the agent sees their status, the link to the finished file and the reason for a failure, so the queue of clips and covers is handled in chat rather than in the account.
Creatomate is built so that design and data are kept apart: the template is assembled by hand in the editor, and the API only changes the values of its elements. Hence the rule the agent sticks to: it does not rework the composition and does not create new templates, it fills data into prepared fields. It finds those fields by the names set in the editor, so a renamed layer drops out of the substitution — and the agent names the field it could not find.
A batch is the normal mode of work: the agent feeds the whole list of products or rows into the template and fires off the render for the entire batch at once instead of one clip at a time. Then it keeps the queue: checks job statuses, shows the failed ones together with the reason and relaunches them with the same substitutions. Writing covers launching renders and deleting them from the history — the templates themselves stay untouched.
The connection uses the project API key, and from there everything runs over HTTP: the agent holds the cap of 30 requests per 10 seconds itself, and it launches renders asynchronously — the job joins a queue and the link to the file shows up as processing goes on, not in the response. Rendering spends credits: an image costs one, a minute of 720p video around fourteen, so the agent names the price of a batch before it starts. If the project has no templates or a render did not go through, it says so directly.
Integration scenarios
A whole batch of videos from one template
The agent takes a Creatomate template, feeds your product list into its elements and fires off the render for the entire batch at once instead of one clip at a time.
Template review for a project
The agent lists the project templates and shows which elements in each one you can fill in — headlines, prices, images and colours.
Covers built from fresh data
The agent rebuilds promo images and covers from current numbers on a schedule and hands back links to the finished files with no manual rendering.
Keeping the render queue in check
The agent checks render job statuses, shows the failed ones together with the reason and relaunches them with the same substitutions.
What a batch will cost
The agent counts the credits before the launch — how many go on images, how many on minutes of video — and names the price of the batch before jobs join the queue.
Tidying up the render history
The agent walks through the older jobs, shows which files have already been collected and which are left as clutter, and deletes the unneeded ones from the history.
Creatomate examples
Поставил в рендер 40 роликов по шаблону «Product Reel 9:16».
Подставил название, цену и фото из каталога, 37 готовы, три упали на битой ссылке картинки — перезапустил с заменёнными файлами. Ссылки пришлю одним списком.
Партия рендера
Document · DOCXHow to connect
Before you connect
- A creatomate.com account — the API works on every plan
- Render credits on the project balance
- 1
Create an account at creatomate.com
The free trial gives 50 credits with no card, and the API works on every plan. Rendering spends credits: one image costs 1, a minute of 720p video about 14.
- 2
Create at least one template in the editor
The agent reads the project's template list and renders from it. An empty project returns an empty list, so create or open a template in the Creatomate editor.
- 3
Pick the project whose templates you need
Every project has its own key. A neighbouring project's key returns someone else's template list, so pick the project before copying.
FAQ
With the project API key: in your Creatomate account pick the project, open Project Settings and click the API Key field — the value is hidden and reveals on click. Each project has its own key: a neighbouring project key returns someone else's template list.
The templates of the selected project along with their elements and editable fields, plus render jobs: status, link to the finished file and the reason for a failure.
It launches renders and can delete them from the history, but it never edits the templates themselves — you build those in the Creatomate editor and the agent only fills in the values.
The API answers on every plan, with a cap of 30 requests per 10 seconds. Rendering spends credits: one image costs 1 credit, a minute of 720p video around 14.