Creatomate

Render finished MP4s, GIFs, and images from Creatomate templates by filling in dynamic text, media, and colors. Agents start renders from a template or raw source JSON, poll render status, and browse templates to batch-produce personalized video and image variations.

6 actions API key available

Creatomate website ↗ Platform Documentation ↗ Capability data verified 2026-07-28

A new campaign batch of product records lands in the shared [Google Sheets](/integrations/google-sheets) workbook

Get Template inspects the promo template's source JSON to confirm the element names the data must fill

Create Render From Template renders samples from the first few records, metadata carrying each record's id

The campaign owner reviews the samples for data mapping, crops, and timing before authorizing the batch

The full batch renders, one job per record, each correlated back to its row through the echoed metadata

Get Render polls each job to succeeded and routes failures to a retry queue with reasons

Finished MP4s archive to [S3](/integrations/s3) and the delivery links post to [Slack](/integrations/slack)

What This Integration Enables

Video is the format that never scales, because editing does not scale. Creatomate's answer is to make a finished MP4, GIF, or image the output of a render call: a template plus a modifications object mapping element names to new text, media, and colors. FlowRunner agents drive it end to end, starting renders from saved templates or from raw source JSON for fully code-generated compositions, polling asynchronous jobs to completion, and correlating every output back to the record that produced it. Batches multiply whatever they are given, correct or wrong, which is why the first renders of any run pass a [human-in-the-loop](/concepts/human-in-the-loop) review before the volume flows. - Render personalized promo videos and social assets from CRM, form, and spreadsheet data - Batch-produce per-product and per-locale variations by swapping only the elements that change - Generate fully dynamic compositions from raw source JSON with no saved template at all - Track render status and collect output URLs for publishing, archiving, and notification - Inspect template source JSON so flows discover overridable elements instead of assuming them

Without FlowRunner

Video does not scale Every variation is an editor's afternoon, so most campaigns get one video or none

Personalization stops at email Per-recipient video is priced like production work, because it is production work

Renders live on laptops Finished files scatter across downloads folders with no record of what produced them

With FlowRunner

Variations are data One template, and only the elements that change get swapped per render

Video behaves like mail merge Rows from a sheet or CRM become finished MP4s, each tied to its source record

Every render is a tracked job Status, output URL, and correlating metadata live on the render, queryable later

Use Case Scenarios

A product line's worth of promo videos

The merchandising team maintains the product sheet, and the agent handles everything after that. For each row in [Google Sheets](/integrations/google-sheets), Create Render From Template fills the promo template's title, price, and product image elements, and the whole batch renders overnight without supervision. Get Render confirms each job succeeded, failures retry with their reasons logged, and the finished files land in [S3](/integrations/s3) keyed by SKU, ready for the storefront and the ad platform alike. When the design team updates the template, next week's batch ships the new look without anyone touching the flow.

The form response that becomes a personal video

A registration lands in [Typeform](/integrations/typeform) and the respondent gets a video with their name, their event track, and their session picks composited into the welcome template. The render's metadata carries the response id, so when the webhook reports completion, the agent knows exactly whose inbox the file belongs in and sends it through [Gmail](/integrations/gmail-service). Personalized video stops being a launch-week stunt and becomes the default confirmation, produced at the cost of a render rather than the cost of an editor.

Compositions that exist only as code

The weekly metrics recap needs a layout that changes with the data: more chart panels on busy weeks, fewer on quiet ones. There is no saved template for that, so the agent builds the Creatomate source JSON programmatically and calls Create Render From Source with an MP4 output. The same pattern produces quote cards sized per platform from one design definition, each variant a small change to the source object rather than a separate design. List Renders keeps the production history auditable, so any published asset traces back to the exact job and data that made it, months after the person who ran the campaign has moved on.

Human-in-Loop Highlight

A batch render is a multiplier with no opinion about what it multiplies. Create Render From Template pointed at a misaligned column renders the wrong price into three hundred finished videos as cheerfully as the right one, spending real render time on every job, and a personalized video that reaches its recipient with someone else's name in it cannot be unsent, only apologized for. So batches start with samples: the agent renders the first handful, presents them beside the source records they were filled from, and the campaign owner checks the data mapping before that approval releases the rest of the run. The review costs minutes. Re-rendering a whole campaign, or explaining to a customer why their personalized video got the person wrong, costs considerably more than minutes.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

6 actions

Renders

Create Render From Template Starts a video or image render from a saved template, with a modifications object mapping element names or property paths to replacement text, media URLs, and colors. Everything not listed keeps the template default. Asynchronous, returning one render job per output, with optional webhook notification and echoed metadata for correlation.
Create Render From Source Starts a render from a raw Creatomate source object instead of a saved template, with the output format chosen per call: MP4, GIF, JPG, PNG, and more. The path for fully dynamic, code-generated designs.
Get Render Retrieves one render's status by id as it moves through planned, waiting, transcribing, and rendering to succeeded or failed, with the downloadable URL populated on success. The polling step in every batch.
List Renders Lists the account's renders, most recent first, with pagination and status filtering. The batch monitor and the audit trail over what was produced.

Templates

List Templates Lists saved templates with pagination and name search. The discovery step that feeds template ids into render calls.
Get Template Retrieves a template's metadata and full source JSON. Inspecting the source reveals the element names a modifications object can override, which is how flows stay correct as designers iterate.

Frequently Asked Questions

What can FlowRunner do with Creatomate?

FlowRunner agents can run Create Render From Template, Create Render From Source, and Get Render in Creatomate, plus 3 more actions.

Does connecting Creatomate to FlowRunner require OAuth?

No. Creatomate connects to FlowRunner with an API key, no OAuth flow required.

Can Creatomate trigger a FlowRunner workflow automatically?

Creatomate doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Creatomate

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us