Meetings & Voice · Integration
Dialpad
Add Dialpad to your product for your customers, and give your AI agents governed access to it.
Dialpad is business telephony with transcription attached, so the useful object is rarely the call record on its own: it is the call plus what was said. Transcripts arrive after the call ends rather than with it, which means a product that reads the call immediately gets metadata and nothing else, and has to come back. Numbers and users are provisioned per company, so the tenancy boundary is clean. Call events are pushed, and they are time-sensitive in a way most integrations are not, because a missed call is only interesting for a few minutes. fastn handles per-customer authorisation and delivers the events rather than making you poll.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Dialpad account so call activity appears next to their records in your product.
Read a call with its transcript once processing completes, rather than metadata alone.
Match a call to the contact or account it belongs to inside your product.
React the moment a call ends or is missed, which is when the follow-up matters.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads a call transcript and drafts the follow-up for a human to send.
An agent logs call outcomes within governed permissions, with the write audited per tenant.
An agent reacts to a missed call and surfaces who should return it.
Example prompt
Summarise the calls with this account this week and flag anything that needs a follow-up.
Set up Dialpad in 4 steps
- 01Enable the Dialpad connector from your fastn dashboard.
- 02Have each customer authorise their own Dialpad 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 Dialpad integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Dialpad integration without building it. Your customers connect their own Dialpad 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 Dialpad update is not your on-call problem.
- One integration serves your product and your agents. The same governed Dialpad 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
ZoomWorks well with
Twilio
Microsoft TeamsOften used alongside
Tools the same teams tend to run next to Dialpad, across other categories.
Slack
Calendly
Google Calendar
AppointletDialpad integration FAQ
How do I add a Dialpad integration to my product?
Enable the Dialpad connector in your fastn dashboard, then let each customer authenticate their own Dialpad account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Dialpad client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Dialpad account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Dialpad 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 Dialpad 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 reads a call transcript and drafts the follow-up for a human to send.
Who maintains the Dialpad integration?
fastn does. When Dialpad 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 Dialpad 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 Dialpad account rather than through a shared one.
Can I get recordings, transcripts and outcomes back from Dialpad?
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 Dialpad integration?
A common starting point: let a customer connect their own Dialpad account so call activity appears next to their records in your product. 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 Dialpad integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Dialpad does not change your per-connector cost. You can start free with 3 connected accounts.
Add Dialpad to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.