FlowRunner
PricingContact
Theme
Start Free

Dialpad

Communication

Run Dialpad from your workflows: agents place outbound calls, send SMS and MMS, provision users and phone numbers, sync contacts, retrieve AI call transcripts and usage statistics, and register webhooks for call and SMS events.

33 actions API key available
Dialpad website ↗ Platform Documentation ↗ Capability data verified 2026-07-27
A completed sales call lands in the day's call log
Get Call Transcript pulls the speaker-attributed AI transcript
Agent lifts commitments, objections, and next steps from the text
Call summary and follow-up task logged to the CRM contact
Caller matched to an open deal before the recap is drafted
Rep receives the drafted follow-up SMS for review
Rep approves the draft; Send SMS delivers it from their number

What This Integration Enables

The phone is where deals close and problems escalate, and it is also the system of record most companies never read. Dialpad's AI transcripts change that only if something moves them: this integration lets agents pull the speaker-attributed transcript after every call and turn it into CRM history, follow-up tasks, and drafted replies. Agents also run the telephony operation itself: provisioning users, assigning and releasing numbers, syncing the shared contact directory, placing outbound calls that ring the rep's own device first, and sending SMS from users or shared lines. The connector treats outbound communication and account lifecycle as decisions, not just actions. A text reaches a customer; a deleted user releases their numbers permanently. FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop/) model puts a person on exactly those steps while agents carry everything around them: transcript retrieval, statistics exports, webhook and event subscription management for real-time call and SMS automation. Connector capabilities are built and verified against Dialpad's official API.

Without FlowRunner

Calls that vanish What was said on the phone never reaches the CRM record
Manual phone admin New hires wait on IT for a line; departures keep theirs too long
Stats nobody pulls Call volume and answer rates get reviewed when something breaks

With FlowRunner

Every call becomes a record Transcript, summary, and follow-up task logged the same hour
Provisioning as a workflow Users and numbers created, assigned, and released on schedule
Reporting on a cadence Call and text statistics export weekly without anyone asking

Use Case Scenarios

Call wrap-up that writes itself

A sales call ends. The agent retrieves the transcript with Get Call Transcript, extracts what was committed and what stalled, and logs a structured summary and follow-up task against the contact in [HubSpot](/integrations/hubspot). It then drafts the recap text the rep promised on the call and sends it to the rep for review. One tap approves it, and Send SMS delivers the message from the rep's own Dialpad number. The customer sees a fast, personal follow-up. The rep never opened the CRM.

Joiner and leaver workflows for the phone system

HR marks a start date, and the agent calls Create User for the new hire in the right office, then Assign Number so a line is live before day one. Offboarding runs the same discipline in reverse: the agent inventories the departing user's assigned numbers with List Numbers, reassigns the main line to the team with Assign Number, and stages the account removal for approval. Phone provisioning stops being a ticket queue and becomes part of the same workflow that handles laptops and licenses.

A weekly telephony report the ops lead actually reads

On Friday afternoon, an agent calls Request Statistics for the week's calls and texts, polls Get Statistics Result, and posts the download plus a summary to the operations channel in [Slack](/integrations/slack): volumes by office and call center, answer rates, voicemail counts. When a call center's answer rate slides, the agent flags it against prior weeks. The conversation about coverage happens Monday morning with data, not anecdotes.

Human-in-Loop Highlight

Delete User permanently removes a person from the Dialpad company and releases their assigned numbers, and Dialpad cannot undo it. Those numbers may be printed on business cards, saved in customers' phones, or wired into call flows. So the offboarding agent stages rather than executes: it lists the departing user's numbers and their assignments, checks which departments and call centers route through them, and asks the operations owner in Slack: "Offboarding for M. Torres is complete except Dialpad. Deleting the user releases +1 555 0142, which is the after-hours line for the support call center. Reassign that number first, or confirm release?" The agent has already done the audit that usually gets skipped. The person decides what happens to a number customers still dial.

Agent processes routinely
Detects exception requiring judgment
Clear match Continues automatically
Ambiguous Routes to human via Slack
Human decides
Agent resumes with decision

Agent Capabilities

33 actions

Users

5
  • List Users Lists users in the company, filterable by email, office, or state. Used in provisioning audits and offboarding sweeps.
  • Get User Retrieves a user's full profile, numbers, office, and license. Pass "me" to resolve the account behind the API key.
  • Create User Provisions a new user in an office with an email and license type. Used in new-hire workflows so a line exists before day one.
  • Update User Updates a user's name, office, admin status, job title, or license. Only provided fields change.
  • Delete User Permanently deletes a user and releases their numbers. The gated action in this connector: offboarding workflows require human confirmation first.

Calls

2
  • Initiate Call Places an outbound call that rings the user's own device first, then connects to the destination. Used for tracked callbacks that feel personal because they are.
  • Get Call Transcript Retrieves the AI-generated, speaker-attributed transcript of a completed call. The raw material for wrap-up summaries, CRM logging, and coaching workflows.

Messaging

1
  • Send SMS Sends an SMS or MMS from a user or shared line to up to 10 recipients. Outbound to real customers, so drafts route through rep approval before sending.

Contacts

5
  • List Contacts Lists the company address book with cursor pagination. Used to sync the directory with external CRMs.
  • Get Contact Retrieves a contact's names, emails, numbers, company, and title.
  • Create Contact Creates a shared company contact, or a personal one when an owner is set. Used to push CRM records into the phone system so callers are recognized.
  • Update Contact Updates a contact's fields; array fields replace existing values. Used in directory sync workflows.
  • Delete Contact Permanently deletes a contact from the address book. Used in reviewed directory cleanup.

Organization

6
  • List Departments Lists departments, optionally scoped to an office. Used to understand routing before changing it.
  • Get Department Retrieves a department's name, office, and assigned numbers.
  • List Offices Lists offices, the top-level unit containing departments, call centers, and users.
  • Get Office Retrieves an office's numbers, country, and plan details.
  • List Call Centers Lists call centers, optionally scoped to an office. Used in coverage and staffing reports.
  • Get Call Center Retrieves a call center's routing configuration and numbers.

Numbers

3
  • List Numbers Lists company phone numbers with type and current assignment. Used to audit what routes where before offboarding or reorganization.
  • Assign Number Assigns a number to a user, office, department, or call center, either a specific number or auto-selected by area code. Used in provisioning and reassignment.
  • Unassign Number Releases a number back to the available pool. Cannot be undone, so reassignment workflows confirm the routing impact first.

Statistics

2
  • Request Statistics Starts an asynchronous export of call, text, recording, or voicemail statistics for a date range. Used for the weekly reporting cadence.
  • Get Statistics Result Polls an export job and returns the download URL when processing completes.

Webhooks

4
  • List Webhooks Lists configured webhooks and their destination URLs.
  • Get Webhook Retrieves a webhook's URL and signature configuration.
  • Create Webhook Creates a webhook endpoint, optionally with an HMAC secret, to receive event payloads. The foundation for real-time call and SMS automation.
  • Delete Webhook Permanently deletes a webhook and stops all deliveries attached to it. Used in reviewed cleanup.

Event Subscriptions

5
  • List Event Subscriptions Lists subscriptions of a given kind: call, SMS, or agent status.
  • Create Call Event Subscription Subscribes a webhook to call events such as ringing, connected, and hangup, scoped to a target and call states. Used to trigger wrap-up workflows the moment a call ends.
  • Create SMS Event Subscription Subscribes a webhook to SMS events by target and direction. Used to route inbound texts into triage workflows.
  • Create Agent Status Subscription Subscribes a webhook to agent availability changes in a call center or department. Used for live coverage monitoring.
  • Delete Event Subscription Permanently deletes an event subscription, stopping its deliveries. Used in reviewed cleanup.

Frequently Asked Questions

What can FlowRunner do with Dialpad?

FlowRunner agents can run List Users, Get User, and Create User in Dialpad, plus 30 more actions.

Does connecting Dialpad to FlowRunner require OAuth?

No. Dialpad connects to FlowRunner with an API key, no OAuth flow required.

Can Dialpad trigger a FlowRunner workflow automatically?

Dialpad doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Dialpad

$100 in credits. No card required. Connect in minutes.