What can you do with the Dialpad integration?

LiveContext exposes 16 operations on Dialpad, covering call, contact, recording and transcript. Common uses include CRM sync, reporting and routing config.

LiveContext

All integrations

Dialpad integration

AI-powered cloud communications platform API for voice, video, messaging, and contact center operations. Make and manage calls, access call recordings and transcripts, handle SMS messaging, and integrate with CRM systems. Perfect for building communication workflows, analytics, and customer service integrations.

16 toolsOAuthAPI docs

Connect Dialpad How integrations work

Common Dialpad use cases

CRM sync
reporting
routing config
call review
address book
org structure
caller ID
compliance export
training materials
dispute resolution

What you can do with Dialpad

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Call, 3 operations

GETget_call
Retrieves detailed information about a specific call including duration, participants, recordings, and state.
POSTinitiate_call
Initiates an outbound call from a Dialpad user's application to a phone number.
GETlist_calls
Lists call records with filtering by date, target, direction, and state. Returns call metadata and recording status.

Contact, 3 operations

POSTcreate_contact
Creates a new shared contact in the Dialpad directory with name, phones, emails, and company info.
GETget_contact
Retrieves a contact by ID with name, phone, email, and type.
GETlist_contacts
Lists shared company contacts or user's local contacts with pagination.

Recording, 2 operations

POSTcreate_recording_sharelink
Creates a shareable link for a call recording.
GETget_recording_sharelink
Gets a recording share link by ID for accessing call recordings.

Transcript, 2 operations

GETget_transcript
Retrieves AI-generated call transcript with Dialpad AI moments for a specific call.
GETget_transcript_url
Gets the transcript URL for a specific call.

User, 2 operations

GETget_user
Retrieves detailed information about a user including phone numbers, admin status, and settings.
GETlist_users
Lists all users in your Dialpad company with optional email and state filters and pagination.

Call center, 1 operation

GETlist_call_centers
Lists all call centers for your company.

Department, 1 operation

GETlist_departments
Lists all departments for an office with their configuration and member information.

Office, 1 operation

GETlist_offices
Lists all offices accessible with your API key.

Sms, 1 operation

POSTsend_sms
Sends an SMS message from a Dialpad user to up to 10 recipients.

Dialpad API rate limits

20 requests per second

Rate limits are applied at the company level (20 req/s per company). Individual endpoints may have lower limits (e.g., initiate_call: 5/min, call get: 10/min, create contacts: 100/min, send SMS: 100/min).

These are the limits Dialpad documents, not ones LiveContext measured. They can change and often depend on your plan, so check the Dialpad documentation for current values.

Use Dialpad from Claude Code, Cursor or Codex

Connect Dialpad in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Dialpad operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Dialpad

Create your workspace
Sign up free. Nothing to install.
Connect Dialpad once
Add your Dialpad connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Dialpad integration FAQ

What can you do with the Dialpad integration?: LiveContext exposes 16 operations on Dialpad, covering call, contact, recording and transcript. Common uses include CRM sync, reporting and routing config.
What are the Dialpad API rate limits?: Dialpad documents 20 requests per second. Rate limits are applied at the company level (20 req/s per company). Individual endpoints may have lower limits (e.g., initiate_call: 5/min, call get: 10/min, create contacts: 100/min, send SMS: 100/min). Limits are set by Dialpad and can depend on your plan.