AI & Models · Integration
HeyGen
Add HeyGen to your product for your customers, and give your AI agents governed access to it.
HeyGen generates video from a script and an avatar, and the thing that shapes any integration is that generation is asynchronous. You submit a request, get an identifier, and poll or wait for a callback while a render completes, so a product that expects a synchronous response will appear broken on exactly the jobs users care about. Avatars and voices are the catalogue worth surfacing, because the choice between them is the creative decision a user wants to make rather than a technical one. Output is a rendered asset with a URL rather than a stored record, so treat it as a file to move somewhere durable. fastn scopes each customer's key and keeps the callback handling out of your product.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own HeyGen account so generated video is billed to them and stays in their workspace.
Submit a video generation job from your product and track it to completion without blocking a request.
List the avatars and voices a customer has access to, so they choose rather than accepting a default.
Collect the finished asset when a render completes, rather than polling a job that takes minutes.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent drafts a script and submits a render within governed permissions, with the job audited per tenant.
An agent reports which renders are still in progress and which failed, and why.
An agent picks an avatar and voice matching a brand profile the customer configured.
Example prompt
Which video renders are still processing, and how long has each been running?
Set up HeyGen in 4 steps
- 01Enable the HeyGen connector from your fastn dashboard.
- 02Have each customer authorise their own HeyGen account, so calls run under their credentials rather than a shared key.
- 03Decide which models, requests and outputs your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the HeyGen integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a HeyGen integration without building it. Your customers connect their own HeyGen account inside your product and work their models, requests and outputs there, with no per-customer code on your side.
- Handle the part that actually costs time: per-customer keys, quotas and cost attribution matter more than schema here, because every call is billed. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a HeyGen update is not your on-call problem.
- One integration serves your product and your agents. The same governed HeyGen connection powers in-product features and gives AI agents scoped, audited access, so you give your product and your agents a model call each customer pays for themselves without wiring it twice.
Used by these teams
Compare with
OpenAIWorks well with
Canva
FigmaOften used alongside
Tools the same teams tend to run next to HeyGen, across other categories.
Snowflake
Airtable
PostgreSQL
AmplitudeHeyGen integration FAQ
How do I add a HeyGen integration to my product?
Enable the HeyGen connector in your fastn dashboard, then let each customer authenticate their own HeyGen account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no HeyGen client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own HeyGen account?
Yes. Every connection is scoped to the individual customer, so each authorises their own HeyGen account and only ever sees their own models, requests and outputs. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this HeyGen integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent drafts a script and submits a render within governed permissions, with the job audited per tenant.
Who maintains the HeyGen integration?
fastn does. When HeyGen changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Whose HeyGen API key and quota does each call use?
Each customer authorises their own HeyGen account, so usage, rate limits and cost land on the customer that caused them. You are not metering a shared key and re-billing it, and one heavy customer cannot exhaust another's quota.
Are inputs and outputs auditable?
Yes. Every call is logged per tenant with the call, the input and the result, so an output can be traced back to what produced it. That matters more here than in most integrations, because a generated answer or an extracted field cannot be reconstructed from the request alone.
What can I build with the HeyGen integration?
A common starting point: let a customer connect their own HeyGen account so generated video is billed to them and stays in their workspace. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the HeyGen integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding HeyGen does not change your per-connector cost. You can start free with 3 connected accounts.
Add HeyGen to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.