Skip to content
Dialpad logo

Connectors / Communication · HTTP Connector

Automate Dialpad with Tray.ai

Start a call, create a contact and create a call center in Dialpad, and start a workflow when Dialpad sends “Call state changed”.

What can you do with Dialpad on Tray.ai?

Dialpad is a cloud phone system and contact centre with calling, SMS, meetings and AI call transcripts and recaps for sales and support teams. Tray.ai connects to Dialpad through the HTTP Connector, so your workflows can call the Dialpad API alongside the rest of your stack.

  • When Dialpad sends “Call state changed”, log the finished call on the contact in your CRM.
  • Create a contact for each new customer added to your CRM so reps see a name on incoming calls.
  • Post a message in your team chat when Dialpad sends “Agent status changed” during peak support hours.
  • When Dialpad sends “SMS sent or received”, attach the message to the open ticket in your help desk.
Connects through
HTTP Connector
Authentication
A bearer token or OAuth 2.0
Base URL
https://dialpad.com/api/v2

Set it up

Connect Dialpad to Tray.ai

Each step uses Dialpad's own API details, from its documentation.

Step 1

Save Dialpad's API token

Save the token Dialpad issues as a Tray.ai authentication. The HTTP Client sends it as a bearer token on every call. The token stays out of the workflow and out of the logs.

Step 2

Point the HTTP Client at the API

Add an HTTP Client step and use https://dialpad.com/api/v2 as the base URL. Or paste a cURL example from Dialpad's API docs, and Tray.ai fills in the method, URL, and headers.

Step 3

Start with “List calls”

It's one of 21 documented actions, under Calls. The response comes back as data the next step can map into your other apps.

Step 4

Start workflows from Dialpad events

Give Dialpad the URL of a Tray.ai webhook trigger. “Call state changed” can then start a workflow, and so can 5 other events.

Workflows to build with Dialpad

Each one uses actions and events from Dialpad's own API documentation.

Log Dialpad calls on Salesforce records

When

Call state changed

Then

  1. Get a call from Dialpad once it has ended
  2. Log the call on the matching contact or lead in Salesforce

With Salesforce

Add new HubSpot contacts to Dialpad

When

A contact is created in HubSpot

Then

  1. Create a contact in Dialpad with the person's name and phone number
  2. Save the Dialpad contact ID on the HubSpot contact

With HubSpot

Create Dialpad users for new hires in Okta

When

A user is assigned the Dialpad app in Okta

Then

  1. Create a user in Dialpad with the employee's details
  2. Post the new user's number to the IT channel in Slack

With Okta and Slack

Apps you can build on Dialpad data

Internal tools your team can build with an AI assistant, each one using Dialpad calls from its API documentation.

Call center staffing board

Lists call centers and agents with live status so a supervisor can see who is available right now.

Call history lookup

Search recent calls by user or contact and open call details for a support or sales review.

New hire phone setup

Lets an IT admin add a new user to Dialpad and assign them to the right call center.

Give your AI agents Dialpad tools

Build an MCP server on Dialpad in Agent Gateway and choose which actions your agents can call. Every call runs with access control and an audit trail. How Agent Gateway works

  • List calls
  • List contacts
  • List users
  • List call centers
  • Create a webhook
  • Get a call
  • Start a call
  • Transfer a call

What the Dialpad API covers

5 resources and 21 documented actions, each one a call the HTTP Connector can make from a Tray.ai workflow. Connecting it takes a few clicks: here's how.

Calls

  • List calls
  • Get a call
  • Start a call
  • Transfer a call
  • Hang up a call

Contacts

  • List contacts
  • Get a contact
  • Create a contact
  • Update a contact
  • Delete a contact

Users

  • List users
  • Get a user
  • Create a user
  • Update a user
  • Delete a user

Call centers

  • List call centers
  • Get a call center
  • Create a call center
  • Update a call center

Webhooks

  • Create a webhook
  • Create a call event subscription

Events Dialpad can send to a Tray.ai webhook trigger

  • Call state changed
  • SMS sent or received
  • Contact created
  • Contact updated
  • Contact deleted
  • Agent status changed

Checked against Dialpad's own documentation on 2026-10-22

developers.dialpad.com/reference

Frequently asked questions

What can a Tray.ai workflow do in Dialpad?

+

The Dialpad API documents 21 actions across 5 resources (Calls, Contacts, Users, Call centers, Webhooks). For example: List calls; List contacts; List users. A workflow can make any documented call through the HTTP Connector.

How does Tray.ai authenticate with Dialpad?

+

The Dialpad API uses a bearer token and OAuth 2.0. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

Which Dialpad events can start a Tray.ai workflow?

+

Dialpad sends 6 events to a webhook URL, for example: Call state changed; SMS sent or received; Contact created; Contact updated; Contact deleted; Agent status changed. A Tray.ai webhook trigger receives them and starts a workflow.

See Dialpad working against your stack.

We'll walk through a tailored demo with your systems plugged in.

Great — a couple more details

This helps us connect you with the right person. Optional, and you can skip it.