Meetings & Voice · Integration
Zoom
Add Zoom to your product for your customers, and give your AI agents governed access to it.
This is Zoom Meetings specifically: the scheduling, the people who join and what the cloud keeps afterwards. The objects are meetings and their occurrences, registrants where registration is switched on, participants once a meeting has actually run, and cloud recordings with their transcripts. Three facts decide whether an integration behaves. Recurring meetings have occurrence ids, so updating the series and updating next Tuesday are different calls. A cloud recording does not exist the moment a meeting ends, it appears when processing completes, which is why the recording completed event exists and why polling for a file is the wrong pattern. And a recording download link is short-lived and credentialed, so it cannot be handed to a browser and forgotten. Authorisation is per user or per account through OAuth, or server-to-server where a business is wiring up its own tenant, and fastn keeps whichever they chose refreshed.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own Zoom account so a meeting your product schedules is owned by them and counts against their own licence.
Create a recurring meeting and update a single occurrence without disturbing the rest of the series.
Read the participant list after a meeting to record who actually attended rather than who was invited.
React to the recording completed event and fetch the recording and its transcript while the download link is still valid.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent schedules a meeting with the right registrants in the customer's own account, and the meeting id is recorded.
An agent summarises what a meeting covered from its cloud recording transcript.
An agent reports which invitees never joined and proposes a follow-up.
Example prompt
Who actually joined yesterday's customer call, and what did the recording say we committed to?
Set up Zoom in 4 steps
- 01Enable the Zoom connector in your fastn dashboard.
- 02Have each customer authorise their own Zoom account, through user OAuth or a server-to-server grant on their own tenant.
- 03Decide which meetings your product creates or watches, then subscribe to the participant and recording completed events you need.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Zoom integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Zoom integration without building it. Your customers connect their own Zoom account inside your product and work their meetings, calls and participants there, with no per-customer code on your side.
- Handle the part that actually costs time: a call or a meeting is a real-time event, so a missed join or a dropped recording cannot be retried later. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Zoom update is not your on-call problem.
- One integration serves your product and your agents. The same governed Zoom connection powers in-product features and gives AI agents scoped, audited access, so you let your product act on the conversations that happen by voice and video, not just the written ones without wiring it twice.
Used by these teams
Compare with
Google Meet
Zoom Phone
Cisco Webex MeetingsOften used alongside
Tools the same teams tend to run next to Zoom, across other categories.
Slack
Microsoft Teams
Twilio
CalendlyZoom integration FAQ
How do I add a Zoom integration to my product?
Enable the Zoom connector in your fastn dashboard, then let each customer authenticate their own Zoom account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Zoom client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Zoom account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Zoom account and only ever sees their own meetings, calls and participants. 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 Zoom 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 schedules a meeting with the right registrants in the customer's own account, and the meeting id is recorded.
Who maintains the Zoom integration?
fastn does. When Zoom 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.
Can my product schedule or act on Zoom conversations automatically?
Yes. Within the permissions each customer grants, your product can create a meeting, place or route a call, add participants, or react when one ends, all inside their own Zoom account rather than through a shared one.
Can I get recordings, transcripts and outcomes back from Zoom?
Yes, scoped per tenant and audited. This matters more here than in most integrations, because the substance of a call usually exists only in its recording or transcript, so a read that fails silently loses the thing you wanted.
What can I build with the Zoom integration?
A common starting point: let each customer connect their own Zoom account so a meeting your product schedules is owned by them and counts against their own licence. 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 Zoom integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Zoom does not change your per-connector cost. You can start free with 3 connected accounts.
Add Zoom to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.