Skip to content

Start building

Integration · Phone and contact center

AI agents for Dialpad

Read Dialpad calls with their recordings, transcripts and AI moments, look up users and contacts, send SMS from a Dialpad number, and start outbound calls that ring a user's Dialpad devices.

Actions
9
Read
6
Write
3

Actions

What your agents can do in Dialpad

9 actions. Each one is a tool your agents can call and a step your workflows can run.

Read 6

Look things up. Nothing changes.

  • List users

    Lists the company's Dialpad users at items[]: each with id (for send_sms, start_call and list_calls), display_name, first_name, last_name, emails, phone_numbers.

  • Get a user

    Reads one Dialpad user by id (or me for the key's own user, with a user-level key).

  • List calls

    Lists concluded calls, newest first, at items[]: each with call_id, direction, state, external_number and internal_number, contact (name, phone, email), target.

  • Get a call

    Reads one concluded call by call_id: direction, state, numbers, contact, target, times and duration, recording_details and recording share links, voicemail links, csat_score.

  • Get a call transcript

    Reads the Dialpad AI transcript of a call at lines[].

  • List contacts

    Lists the company's shared Dialpad contacts (or one user's local contacts with owner_id) at items[].

Write 3

Create, change or send.

  • Send an SMS

    Sends a text message on behalf of a Dialpad user to up to 10 phone numbers (E.164), from that user's number, or from from_number.

  • Start a call

    Starts an outbound call for a Dialpad user: their Dialpad devices ring first (all of them, or one device_id), and when they answer Dialpad dials phone_number.

  • Create a contact

    Creates a Dialpad contact: shared with the whole company, or local to one user when owner_id is set.

A person can approve first

Any write action can be set to wait for a person's approval before it runs, so an agent asks before it changes anything.

Connection

How it connects

Connect it once in the console, then give it to the agents and workflows that need it.

API key

Paste an API key from your Dialpad account.

What you enter

  • API key

Kept safe

  • Credentials are stored encrypted with your organization's own keys.
  • They are opened only by the process that makes the call, at the moment it runs, and never go into a prompt or the browser.
  • Calls go only to the tool's own servers.

How we protect your data

Ideas

Ideas to start with

Starting points made only from the actions above. Mix them with any other tool your agents can use.

  • 01

    Ask about your Dialpad data

    Ask a question in plain words. The agent can list users, get a user or list calls in Dialpad, then answers with what it found.

  • 02

    Let an agent update Dialpad

    Have the agent send an SMS or start a call in Dialpad as part of a larger task. Turn on approval and a person signs off on each change first.

  • 03

    Work from your CRM

    Give one agent HubSpot and Dialpad: it can search contacts in HubSpot and send an SMS in Dialpad in the same run.

FAQ

Dialpad and MyDeepAgents

Can MyDeepAgents connect to Dialpad?

Yes. The Dialpad connector has 9 actions: 6 read and 3 make changes. Your agents can call them as tools, and your workflows can run them as steps.

How do I connect Dialpad?

Paste an API key from your Dialpad account. You'll need: API key. Credentials are stored encrypted with your organization's own keys and are opened only at the moment of a call.

Can an agent change data in Dialpad without asking?

Only if you let it. Each of the 3 actions that change data can be set to wait for a person's approval before it runs.

Can I use Dialpad in workflows as well as agents?

Yes. Every Dialpad action also works as a step in a workflow, and the same connection serves your agents and your workflows.

Early access

Put Dialpad to work

Connect it in a few minutes, give an agent the actions it needs, and decide which changes wait for a person.