Meetings & Voice · Integration

CallPage

Add CallPage to your product for your customers, and give your AI agents governed access to it.

CallPage puts a callback widget on a website and rings a sales rep within seconds of a visitor requesting a call, and its REST API lives at core.callpage.io/api/v1/external rather than on the marketing domain callpage.io. The API key goes in the Authorization header as a bare value with no Bearer prefix, which breaks clients that add one automatically. Version numbering is not uniform: widgets, users, managers, voice messages and SMS sit under v1, while call history and single call detail moved to v3 at /api/v3/external/calls/history, so a single base URL constant is not enough. Every response is wrapped in an envelope with hasError, an optional errorCode and message, and a data field, so HTTP 200 does not mean the operation succeeded and you must inspect hasError. Managers are the join between a user and a widget and carry their own business hours, so who actually gets rung is decided by manager records rather than by the user or the widget alone. fastn holds each customer's API key, handles the mixed v1 and v3 base paths, and keeps the connection working as CallPage moves more endpoints across.

Start freeBook a demo

In your product

Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.

Let a customer connect their own CallPage account so callback requests from their site appear as leads in your product.

Provision widgets programmatically when a customer adds a new website or landing page in your app.

Mirror your product's user roster into CallPage users and assign them as managers on the right widget.

Pull call history into your analytics so callback volume is reported alongside your other lead sources.

For your AI agents

Governed, audited access for the agents you build, through the MCP server.

Let an agent add or remove a manager on a widget when cover changes, with the widget, the manager and the tenant recorded in a per-tenant audit log.

Have an agent report call history for a date range and flag widgets where no manager was available during business hours.

Let an agent update the SMS notification template for a customer's widget after wording is approved.

Example prompt

How many CallPage callbacks came through our pricing page widget last month, and how many went unanswered?

Set up CallPage in 4 steps

  1. 01Enable the CallPage connector from your fastn dashboard.
  2. 02Have each customer authorise their own CallPage account, so calls run under their credentials rather than a shared key.
  3. 03Decide which meetings, calls and participants your product needs, map those fields, then enable the actions and triggers you want.
  4. 04Call it from your product and expose it to your agents through the same governed connection.

Why teams use the CallPage integration

What you get by embedding it with fastn instead of building it yourself.

  • Ship a CallPage integration without building it. Your customers connect their own CallPage 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 CallPage update is not your on-call problem.
  • One integration serves your product and your agents. The same governed CallPage 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

SalesCustomer SupportHR & People Ops

Compare with

AircallGongChorus.ai

Often used alongside

Tools the same teams tend to run next to CallPage, across other categories.

SlackMicrosoft TeamsTwilioCalendly

CallPage integration FAQ

How do I add a CallPage integration to my product?

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

Do my customers each connect their own CallPage account?

Yes. Every connection is scoped to the individual customer, so each authorises their own CallPage 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 CallPage 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 add or remove a manager on a widget when cover changes, with the widget, the manager and the tenant recorded in a per-tenant audit log.

Who maintains the CallPage integration?

fastn does. When CallPage 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 CallPage 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 CallPage account rather than through a shared one.

Can I get recordings, transcripts and outcomes back from CallPage?

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 CallPage integration?

A common starting point: let a customer connect their own CallPage account so callback requests from their site appear as leads 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 CallPage integration cost?

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

Add CallPage to your product

Start free with 3 connected accounts. No sales call required, and no per-customer integration code.

Start freeRead the docs
← All integrations