Synthesia

Generate AI avatar videos with Synthesia. Agents create videos from scripts or reusable templates, track rendering through webhooks, upload media assets, and save finished MP4s into FlowRunner file storage for durable URLs.

13 actions API key available

Synthesia website ↗ Platform Documentation ↗ Capability data verified 2026-07-27

A new customer signs up and their name, company, and plan arrive from the CRM

Get Template reads the welcome template's variables so the customer data maps cleanly

Create Video From Template renders a watermarked preview using the Test flag, spending no quota

The lifecycle marketer watches the preview and approves the production render

Create Video From Template runs the real render and saves the finished MP4 to FlowRunner file storage

The durable URL in savedFile is verified before anything ships, since raw Synthesia download links expire

The welcome email goes out with the customer's personal video link, and the URL posts to the launch channel

What This Integration Enables

Synthesia removes the camera from video production, and this connector removes the human bottleneck from everything around it. FlowRunner agents create AI avatar videos from script clips or reusable templates, feed template variables from CRM and product data, upload image and audio assets for backgrounds and voice, and track rendering through polling or webhooks. Because Synthesia's own download URLs expire, the connector downloads finished MP4s into FlowRunner file storage and returns durable URLs that downstream steps and customers can rely on. The position worth taking: personalized video only matters if it is cheap enough to send to everyone. When a render is just another workflow step, the welcome video, the renewal reminder, and the localized product update stop being campaigns and become defaults, with a [human-in-the-loop](/concepts/human-in-the-loop) approval standing between the watermarked preview and the render that spends real quota.

Without FlowRunner

Video as a production project Every customer-facing video needs studio time, a presenter, and a two-week lead

Personalization stops at first name The welcome email swaps a merge tag; the actual content is identical for everyone

Expiring links in the wild Someone shares a raw download URL and it dies before the customer clicks it

With FlowRunner

Video as a render step A script or template plus CRM data becomes a finished MP4 inside the flow

Per-recipient video at list scale One template renders per customer, per language, per plan, without a human in the studio

Durable URLs by default Finished MP4s land in FlowRunner file storage, so the link in the email keeps working

Use Case Scenarios

A welcome video for every customer, not just the big ones

A signup lands from the CRM. The agent pulls the welcome template's variables with Get Template, fills in the customer's name, plan, and the three features that match their use case, and renders with Create Video From Template. The finished MP4 saves to file storage, and the durable URL goes out through [Gmail](/integrations/gmail-service) in the onboarding email. What used to be reserved for enterprise accounts runs for every signup, because the marginal cost of the next video is a render, not a film crew.

One template, every language

A product announcement needs to reach six markets. The agent uploads localized background images with Upload Asset, then loops Create Video From Template once per language with translated script variables. Each render saves to file storage, and the six durable URLs post to [Slack](/integrations/slack) for regional teams to publish. The localization matrix that used to mean six studio bookings is one template and a loop.

Release notes with a face

When the release ships, the agent turns the changelog into a short script, calls Create Video From Script with the standard avatar and background, and registers Create Webhook for video.completed so the flow resumes the moment rendering finishes. The finished video lands in the release channel for review, then the durable URL is embedded in the update email and the in-app announcement. List Videos keeps the back catalog auditable, and Delete Video retires outdated announcements deliberately.

Human-in-Loop Highlight

The gate in this connector sits between the preview and the production render. Create Video From Script and Create Video From Template consume paid render quota on a plan with API access, and the videos they produce are aimed at customers: a mispronounced name, a wrong plan detail, or a stale claim renders at full quality and lands in an inbox. So the agent renders first with the Test flag, which produces a watermarked preview without touching quota. The marketer watches thirty seconds, approves or edits the script, and only then does the production render spend quota and reach the recipient. Delete Video exists for cleanup, but it cannot recall an email that already shipped, which is exactly why the approval happens before the render, not after.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via email

Human decides

Agent resumes with decision

Agent Capabilities

13 actions

Videos

Create Video From Script Creates an AI avatar video from script clips, each pairing text or recorded audio with an avatar and background. Polls to completion by default and can save the MP4 to FlowRunner file storage for a durable URL. The Test flag renders a watermarked, quota-free preview.
Create Video From Template Creates a video from an existing template by filling its variables with text, media URLs, or avatar and background overrides. The engine behind per-recipient and per-language production.
Get Video Retrieves a video's render status, metadata, and, once complete, an ephemeral download URL. The polling step when a flow starts a render without waiting.
List Videos Lists the account's videos newest first with status and visibility. Used to audit the back catalog and find IDs to retrieve or retire.
Delete Video Permanently deletes a video and its share page. Cannot be undone, so retirement flows run it with review.
Save Video to File Storage Downloads a completed video's MP4 into FlowRunner file storage and returns a durable URL, replacing Synthesia's expiring download links.

Templates

List Templates Lists the account's templates with the variables each one exposes. The catalog an agent chooses from when a flow needs a video.
Get Template Retrieves one template's full variable list, so the agent knows exactly which keys to supply before rendering.

Assets

Upload Asset Uploads an image, video, or audio file from a URL for use as a background, script audio, or clip image. How localized and branded material enters a render.

Webhooks

Create Webhook Registers a webhook for video.completed and video.failed events, with an optional signing secret. Lets flows resume on render completion instead of polling.
List Webhooks Lists registered webhooks with their URLs, events, and status. Used to audit what is listening.
Get Webhook Retrieves a single webhook's configuration by ID.
Delete Webhook Deletes a webhook and stops its deliveries. Cannot be undone.

Frequently Asked Questions

What can FlowRunner do with Synthesia?

FlowRunner agents can run Create Video From Script, Create Video From Template, and Get Video in Synthesia, plus 10 more actions.

Does connecting Synthesia to FlowRunner require OAuth?

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

Can Synthesia trigger a FlowRunner workflow automatically?

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

Start building with Synthesia

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

Start Building Free Talk to us