Content & Documents · Integration
Vidyard
Add Vidyard to your product for your customers, and give your AI agents governed access to it.
Vidyard hosts video for sales and marketing teams, which means the file is only half of what matters. A video sits in a folder, reaches people through a player, and the thing anybody acts on is who watched it and how far they got. An embedded Vidyard integration uploads video from your product, reads and organises the library, and pulls viewing data back so a rep or a marketer sees engagement beside the record it belongs to rather than in a second tab. Sharing and privacy settings belong to the customer's own account, so a connected integration reaches exactly what that account reaches and nothing wider. Credentials stay with fastn, scoped to whoever granted them, and maintaining the connector is our side of the line.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own Vidyard account so video your product produces is hosted under their brand and their settings.
Upload a recording from your product and file it into the folder the customer nominates, with no manual step in between.
Read viewing engagement per video so your product can show who watched and how much of it they finished.
Read player and folder detail so your product embeds the right video without anybody copying an id by hand.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reports which videos a contact has watched and where they stopped.
An agent puts a newly uploaded video where it belongs in the library, inside the permissions it holds, and the move is logged.
An agent finds the video covering a topic and returns its player rather than describing it from a title.
Example prompt
Which videos has this account watched in Vidyard, and how far through each one did they get?
Set up Vidyard in 4 steps
- 01Enable the Vidyard connector in your fastn dashboard.
- 02Have each customer authorise their own Vidyard account so uploads and sharing settings stay theirs.
- 03Map the video, folder, player and viewing fields your product uses, per customer.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Vidyard integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Vidyard integration without building it. Your customers connect their own Vidyard 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 Vidyard update is not your on-call problem.
- One integration serves your product and your agents. The same governed Vidyard 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
Kaltura
BynderWorks well with
HubSpotOften used alongside
Tools the same teams tend to run next to Vidyard, across other categories.
Shopify
Stripe
Jira
AsanaVidyard integration FAQ
How do I add a Vidyard integration to my product?
Enable the Vidyard connector in your fastn dashboard, then let each customer authenticate their own Vidyard account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Vidyard client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Vidyard account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Vidyard 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 Vidyard 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 a contact has watched and where they stopped.
Who maintains the Vidyard integration?
fastn does. When Vidyard 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 Vidyard integration run under?
Each customer's own Vidyard grant. Where Vidyard 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 Vidyard automatically?
Where Vidyard 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 Vidyard integration?
A common starting point: let each customer connect their own Vidyard account so video your product produces is hosted under their brand and their settings. 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 Vidyard integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Vidyard does not change your per-connector cost. You can start free with 3 connected accounts.
Add Vidyard to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.