Meetings & Voice · Integration
tl;dv
Add tl;dv to your product for your customers, and give your AI agents governed access to it.
tl;dv records the call and then treats the recording as something you navigate rather than something you sit through. Its highlights are timestamped, so a moment can be linked to directly and a clip of it shared with somebody who was not there, which is the habit the product is built around and the reason its transcripts are usually consumed at moment level rather than as a wall of text. An integration reads the meeting with its participants, the transcript with speakers marked, the notes and the highlights, and it is driven by two events worth wiring separately: the recording being ready and the transcript being ready, which do not happen at the same time. Recording works across Zoom, Google Meet and Microsoft Teams, so a customer running more than one still has a single place to read from. fastn keeps each workspace's credentials per tenant and follows the API as it changes.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own tl;dv workspace so recorded calls are readable in your product whichever platform hosted them.
Wait on the transcript ready event rather than the recording one, so your product never reads a transcript that is still being written.
Pull the timestamped highlights and link a user straight to the moment instead of to the start of an hour-long call.
Attach a meeting and its transcript to the account, deal or candidate it concerned, so the conversation is where the work is.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent finds the moment a topic came up across recent calls and gives the timestamped quotes.
An agent drafts the follow-up from a meeting's highlights rather than from the full transcript.
An agent reports which calls this week discussed a competitor and what was said about them.
Example prompt
Find where pricing was discussed in this week's tl;dv calls and give me the exact quotes with their timestamps.
Set up tl;dv in 4 steps
- 01Enable the tl;dv connector in your fastn dashboard.
- 02Have each customer authorise their own tl;dv workspace so recordings stay under their permissions.
- 03Subscribe to the meeting and transcript ready events, then map the meeting fields your product stores.
- 04Call it from your product and expose the same governed connection to your agents.
Why teams use the tl;dv integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a tl;dv integration without building it. Your customers connect their own tl;dv 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 tl;dv update is not your on-call problem.
- One integration serves your product and your agents. The same governed tl;dv 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
Gong
Fireflies.aiWorks well with
Microsoft TeamsOften used alongside
Tools the same teams tend to run next to tl;dv, across other categories.
Slack
Twilio
Calendly
Google Calendartl;dv integration FAQ
How do I add a tl;dv integration to my product?
Enable the tl;dv connector in your fastn dashboard, then let each customer authenticate their own tl;dv account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no tl;dv client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own tl;dv account?
Yes. Every connection is scoped to the individual customer, so each authorises their own tl;dv 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 tl;dv 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 finds the moment a topic came up across recent calls and gives the timestamped quotes.
Who maintains the tl;dv integration?
fastn does. When tl;dv 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 tl;dv 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 tl;dv account rather than through a shared one.
Can I get recordings, transcripts and outcomes back from tl;dv?
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 tl;dv integration?
A common starting point: let each customer connect their own tl;dv workspace so recorded calls are readable in your product whichever platform hosted them. 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 tl;dv integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding tl;dv does not change your per-connector cost. You can start free with 3 connected accounts.
Add tl;dv to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.