Chorus.ai

Enable the Chorus.ai connector in your fastn dashboard, then let each customer authenticate their own Chorus.ai account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Chorus.ai client code in your app and no per-customer branch in your codebase. Setup is 4 steps.

Yes. Every connection is scoped to the individual customer, so each authorises their own Chorus.ai 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.

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 summarises the last call with an account before a follow-up meeting.

fastn does. When Chorus.ai 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.

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 Chorus.ai account rather than through a shared one.

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.

A common starting point: read their own call recordings and transcripts into your product, tied to the right account or deal. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.

It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Chorus.ai does not change your per-connector cost. You can start free with 3 connected accounts.