Meetings & Voice · Integration
Avoma
Add Avoma to your product for your customers, and give your AI agents governed access to it.
Avoma records and analyses customer-facing meetings, and its API at api.avoma.com uses a bearer API key generated per user; note that the collection paths need the trailing slash, so /v1/meetings redirects with a 301 while /v1/meetings/ returns a proper 401, and clients that drop the redirect body see a confusing empty result. Meetings are the anchor object, with recordings, transcriptions, notes and scorecards hanging off a meeting uuid and each fetched from its own endpoint, so assembling a full picture of one call is several requests. Processing is not instant: a call that has just ended exists as a meeting well before its transcript and AI notes are ready, so anything reading notes needs to tolerate a null while analysis completes. Avoma's smart categories are configured per organisation, which means the keys in the notes payload differ between customers and cannot be hardcoded. Meeting list queries are bounded by a from and to date range rather than being open-ended. fastn holds each customer's Avoma key on their own connection and keeps the meeting, transcript and notes calls working as the API evolves.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Avoma workspace so call notes flow into your product without copy and paste
Attach transcripts and AI notes to the deal or ticket record your application already owns
Surface which meetings still have no transcript so users know analysis is pending rather than missing
Build reporting on talk time and topic coverage across a customer's team from meeting data
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Ask an agent to pull the notes from a named meeting and list the commitments made
Have an agent scan last week's meetings for a tenant and report which mentioned a competitor, audited per tenant
Let an agent check which recent calls have transcripts ready before a summary workflow runs
Example prompt
What did we agree on in the Avoma-recorded call with Acme last Thursday?
Set up Avoma in 4 steps
- 01Enable the Avoma connector from your fastn dashboard.
- 02Have each customer authorise their own Avoma account, so calls run under their credentials rather than a shared key.
- 03Decide which meetings, calls and participants 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 Avoma integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an Avoma integration without building it. Your customers connect their own Avoma 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 an Avoma update is not your on-call problem.
- One integration serves your product and your agents. The same governed Avoma 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
Aircall
Gong
Chorus.aiOften used alongside
Tools the same teams tend to run next to Avoma, across other categories.
Slack
Microsoft Teams
Twilio
CalendlyAvoma integration FAQ
How do I add an Avoma integration to my product?
Enable the Avoma connector in your fastn dashboard, then let each customer authenticate their own Avoma account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Avoma client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Avoma account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Avoma 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 Avoma integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Ask an agent to pull the notes from a named meeting and list the commitments made
Who maintains the Avoma integration?
fastn does. When Avoma 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 Avoma 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 Avoma account rather than through a shared one.
Can I get recordings, transcripts and outcomes back from Avoma?
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 Avoma integration?
A common starting point: let a customer connect their own Avoma workspace so call notes flow into your product without copy and paste. 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 Avoma integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Avoma does not change your per-connector cost. You can start free with 3 connected accounts.
Add Avoma to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.