🇪🇸 Español 🇬🇧 English 🇧🇷 Português
Omnifox Omnifox
Sign up

Connect Dialpad (cloud phone)

Connect your Dialpad account to Omnifox to handle inbound and outbound calls from the Inbox.

Jul 11, 2026

Dialpad is another cloud phone system widely used by support and sales teams. Connecting it to Omnifox logs calls alongside the rest of a customer's conversation history in the Inbox.

Requirements

  • A Dialpad account with admin rights
  • An API Key generated at dialpad.com/app/admin/company/api-keys
  • The default agent's User ID (and optionally a Group ID)

Steps to connect

  1. At dialpad.com/app/admin/company/api-keys, generate an API Key.
  2. Find the User ID of the agent who handles calls by default (and the Group ID if you want to route by team).
  3. In Omnifox, go to Channels → Connect New Channel, pick Dialpad, and fill in the API Key and User ID (Group ID and Webhook Secret are optional).
  4. Save the channel: Omnifox gives you the matching webhook URL.
  5. In Dialpad, configure a webhook pointing to that URL; if you enable HMAC signing, paste the same Webhook Secret on both sides.

Configuration

  • API Key: a single bearer token for the entire Dialpad REST API.
  • User ID: the Dialpad user called first before bridging to the destination.
  • Group ID (optional): groups calls by team or department.
  • Webhook Secret (optional): enables HMAC verification on the Dialpad-Signature header; leave it blank to accept without signature verification.

Example

A customer calls your Dialpad number; the system first rings the configured agent and, once they answer, bridges the call to the customer — the same pattern as Aircall and RingCentral. The whole event is visible on that customer's conversation in the Omnifox Inbox.

Tips

  • If you'd rather use JWT verification instead of HMAC, ask Omnifox support — the integration supports both, though the wizard sets up HMAC by default.
  • Use the Group ID if several agents share coverage of the same number.

Troubleshooting

  • Calls don't start from Omnifox: check that the API Key hasn't been revoked in Dialpad's admin panel.
  • Call events don't arrive: confirm the webhook URL configured in Dialpad, and if you're using a Webhook Secret, that it's identical on both sides.
Was this helpful?

Related articles