Meetings & Voice · Integration
Leexi
Add Leexi to your product for your customers, and give your AI agents governed access to it.
Leexi's public API answers at public-api.leexi.ai/v1 with a bearer token issued in the workspace, and the central object is a call that covers both a recorded meeting and a telephony conversation, so the participant list can hold external phone numbers as well as workspace users. Transcription and the AI summary are produced after the recording ends, so a call fetched immediately has metadata and no transcript, and the reliable pattern is to subscribe to the processing webhook rather than to poll on a timer. Summaries follow the template configured in the workspace, which means the sections in a summary vary per customer and cannot be assumed by an integration. Recording consent and retention are workspace settings, and a call can be deleted or fall out of retention while your copy of the id still exists, so lookups need to tolerate a record disappearing. Leexi is used across several languages and the transcript carries its detected language, which is worth reading before feeding text into anything downstream. fastn holds each customer's workspace token, keeps calls attributed to the correct tenant, and handles the upkeep.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Leexi workspace so call transcripts and summaries reach your product without manual export.
Attach the summary of a sales call to the matching opportunity in your own record.
Surface who spoke and for how long so a customer can review talk ratio alongside their pipeline data.
Trigger a follow-up task in your product when a call summary contains an agreed next step.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Ask an agent to summarise this week's calls for one account, with transcript reads audited per tenant.
Let an agent extract commitments and dates from a call and draft follow-ups for human approval.
Have an agent report which calls are still awaiting processing so nothing is missed.
Example prompt
What did we agree on the last call with this customer, and who was on it?
Set up Leexi in 4 steps
- 01Enable the Leexi connector from your fastn dashboard.
- 02Have each customer authorise their own Leexi 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 Leexi integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Leexi integration without building it. Your customers connect their own Leexi 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 Leexi update is not your on-call problem.
- One integration serves your product and your agents. The same governed Leexi 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
Often used alongside
Tools the same teams tend to run next to Leexi, across other categories.
Leexi integration FAQ
How do I add a Leexi integration to my product?
Enable the Leexi connector in your fastn dashboard, then let each customer authenticate their own Leexi account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Leexi client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Leexi account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Leexi 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 Leexi 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 summarise this week's calls for one account, with transcript reads audited per tenant.
Who maintains the Leexi integration?
fastn does. When Leexi 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 Leexi 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 Leexi account rather than through a shared one.
Can I get recordings, transcripts and outcomes back from Leexi?
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 Leexi integration?
A common starting point: let a customer connect their own Leexi workspace so call transcripts and summaries reach your product without manual export. 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 Leexi integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Leexi does not change your per-connector cost. You can start free with 3 connected accounts.
Add Leexi to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.