Meetings & Voice · Integration
Callingly
Add Callingly to your product for your customers, and give your AI agents governed access to it.
Callingly connects inbound leads to sales agents by ringing agents in a defined order the moment a lead arrives, and its API at api.callingly.com/v1 exposes leads, calls, clients, teams, agents and webhooks. Auth is a bearer token, but the key is not self-serve from the dashboard: it is issued by Callingly support on request, so onboarding a customer takes a human step you should plan for. Requests without a valid Authorization header are redirected to /login rather than returning 401, so a naive client will follow the redirect and parse an HTML page as a success. Agents carry their own schedule objects under /agents/{id}/schedule, and routing behaviour lives on the team rather than the agent, so changing who gets called first means writing to the team, not the person. The clients resource exists for agencies reselling Callingly, which means a single token can span several sub-accounts and you must scope reads carefully. fastn stores each customer's token, disables redirect-following so auth failures surface honestly, and keeps the connection maintained 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 Callingly account so leads captured in your product trigger an immediate callback to their sales team.
Pull call outcomes and recordings back into your own reporting so conversion is attributed to the originating campaign.
Sync your product's user roster into Callingly agents and keep their schedules in step with your rota.
Let customers configure which team a lead routes to from inside your UI instead of switching to Callingly.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Let an agent create a lead and start a callback for a named team, with the created call and the acting tenant recorded in a per-tenant audit trail.
Have an agent summarise yesterday's calls per team and report which agents missed their assigned rings.
Let an agent update an agent's availability schedule when a rota change is approved.
Example prompt
Which Callingly agents missed the most callbacks last week?
Set up Callingly in 4 steps
- 01Enable the Callingly connector from your fastn dashboard.
- 02Have each customer authorise their own Callingly 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 Callingly integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Callingly integration without building it. Your customers connect their own Callingly 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 Callingly update is not your on-call problem.
- One integration serves your product and your agents. The same governed Callingly 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 Callingly, across other categories.
Callingly integration FAQ
How do I add a Callingly integration to my product?
Enable the Callingly connector in your fastn dashboard, then let each customer authenticate their own Callingly account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Callingly client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Callingly account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Callingly 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 Callingly integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Let an agent create a lead and start a callback for a named team, with the created call and the acting tenant recorded in a per-tenant audit trail.
Who maintains the Callingly integration?
fastn does. When Callingly 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 Callingly 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 Callingly account rather than through a shared one.
Can I get recordings, transcripts and outcomes back from Callingly?
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 Callingly integration?
A common starting point: let a customer connect their own Callingly account so leads captured in your product trigger an immediate callback to their sales team. 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 Callingly integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Callingly does not change your per-connector cost. You can start free with 3 connected accounts.
Add Callingly to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.