# Dialpad integrations: calls and contacts

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

**Canonical page:** https://tray.ai/connectors/dialpad-integrations/
**Categories:** Communication
**Connects through:** HTTP Connector

## Overview

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.

## Use cases

### Calls

Read and create calls in Dialpad from any Tray.ai workflow. The Dialpad API covers calls such as list calls and get a call.

- List calls
- Get a call
- Start a call

### Contacts

Read, create, update, and delete contacts in Dialpad from any Tray.ai workflow. The Dialpad API covers calls such as list contacts and get a contact.

- List contacts
- Get a contact
- Create a contact

### Users

Read, create, update, and delete users in Dialpad from any Tray.ai workflow. The Dialpad API covers calls such as list users and get a user.

- List users
- Get a user
- Create a user

### Call centers

Read, create, and update call centers in Dialpad from any Tray.ai workflow. The Dialpad API covers calls such as list call centers and get a call center.

- List call centers
- Get a call center
- Create a call center

### Webhooks

Create webhooks in Dialpad from any Tray.ai workflow. The Dialpad API covers calls such as create a webhook and create a call event subscription.

- Create a webhook
- Create a call event subscription

### Dialpad events

Start a Tray.ai workflow the moment something happens in Dialpad. Dialpad sends events such as call state changed and SMS sent or received to a Tray.ai webhook trigger.

- Call state changed
- SMS sent or received
- Contact created

## Challenges Tray.ai solves

### Keeping Dialpad credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store Dialpad credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the Dialpad API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the Dialpad API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to Dialpad?

Yes. Tray.ai connects to Dialpad through the HTTP Connector, which calls the Dialpad API directly. Any call the Dialpad API documents can run as a step in a Tray.ai workflow.

### 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.

### Can I get a dedicated Dialpad connector?

Dialpad runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Dialpad connector from the Dialpad API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/