Content & Documents · Integration
Wistia
Add Wistia to your product for your customers, and give your AI agents governed access to it.
Wistia keeps video in projects rather than one flat library, so the media id and the project it belongs to are the two things any integration has to get right. An embedded Wistia integration uploads a video into the project a customer nominates, reads and updates media metadata and captions, and pulls statistics back: plays, play rate and the engagement curve showing where people stopped watching. The interesting part is who watched. Wistia ties a viewing session to a person once that viewer has identified themselves through an in-player form, so watch history is attributable rather than anonymous, which is what makes it worth showing beside a contact record in your own product. Uploads and reads run under each customer's own account token, and fastn keeps those tokens per tenant and follows the API.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own Wistia account so video your product renders is hosted, branded and measured under their subscription.
Upload a recording into the project a customer chose, then set its title, description and captions without anybody opening the Wistia dashboard.
Read plays, play rate and the engagement curve per media so your product can show which videos actually hold attention.
Match a viewing session to a known viewer, so watch history sits beside the person it belongs to in your own records.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reports which videos in a project were watched last week and where viewers dropped off.
An agent uploads a file and files it into a nominated project within scoped permissions, with the upload attributed.
An agent finds the media covering a topic and returns its id rather than guessing from a title.
Example prompt
Which videos in this Wistia project lose the most viewers before the halfway mark?
Set up Wistia in 4 steps
- 01Enable the Wistia connector in your fastn dashboard.
- 02Have each customer authorise their own Wistia account so uploads and hosting stay on their subscription.
- 03Choose which projects your product writes into, and map the media, caption and statistics fields you use.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Wistia integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Wistia integration without building it. Your customers connect their own Wistia account inside your product and work their files, documents and versions there, with no per-customer code on your side.
- Handle the part that actually costs time: permissions and versioning are easy to get subtly wrong, and mistakes expose content. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Wistia update is not your on-call problem.
- One integration serves your product and your agents. The same governed Wistia connection powers in-product features and gives AI agents scoped, audited access, so you let your product work with your customers' documents in place without wiring it twice.
Used by these teams
Compare with
Vidyard
Kaltura
CloudinaryOften used alongside
Tools the same teams tend to run next to Wistia, across other categories.
Shopify
Stripe
Jira
AsanaWistia integration FAQ
How do I add a Wistia integration to my product?
Enable the Wistia connector in your fastn dashboard, then let each customer authenticate their own Wistia account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Wistia client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Wistia account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Wistia account and only ever sees their own files, documents and versions. 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 Wistia 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 reports which videos in a project were watched last week and where viewers dropped off.
Who maintains the Wistia integration?
fastn does. When Wistia 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 permissions does the Wistia integration run under?
Each customer's own Wistia grant. Where Wistia holds a library, their existing folder and item permissions apply and your product cannot reach content the connected account could not reach itself. Where it processes content you supply rather than storing it, the call runs under that customer's own credentials and is logged per tenant.
Can my product create or update content in Wistia automatically?
Where Wistia supports writes, documents, entries and assets can be created, updated and filed from your product or by an agent within scoped permissions, with each action logged. Where it is a read surface, the same connection serves reads only.
What can I build with the Wistia integration?
A common starting point: let each customer connect their own Wistia account so video your product renders is hosted, branded and measured under their subscription. 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 Wistia integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Wistia does not change your per-connector cost. You can start free with 3 connected accounts.
Add Wistia to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.