At a glance
- Availability: Experimental (how to enable).
- Auth: OAuth 2.0.
- Connection: A user authorizes the connection in the provider’s consent screen.
- Scopes:
offline_access. - Docs: https://developers.dialpad.com/docs/oauth
Credentials
Set these per environment. See Connect an integration. With a managed OAuth app, Connect works without these variables; set them to use your own OAuth app instead.Setup
- Request an OAuth app: Dialpad OAuth clients are issued by Dialpad: contact [email protected] (or your Dialpad account manager) to register an OAuth app with your redirect URI <your-app-url>/api/auth/dialpad/callback and the scopes you need (request offline_access for refresh tokens). See https://developers.dialpad.com/docs/oauth.
- Use the sandbox for testing: Dialpad provides a free developer sandbox at https://sandbox.dialpad.com (see https://developers.dialpad.com/docs/sandbox). Sandbox OAuth uses https://sandbox.dialpad.com/oauth2/authorize and /oauth2/token.
- Set credentials: Add DIALPAD_CLIENT_ID and DIALPAD_CLIENT_SECRET to your .env.
- Verify access: Complete the OAuth flow, then run the List Contacts tool.
- Refresh tokens are only issued when the offline_access scope is requested and approved for your app
- Scopes must be approved by Dialpad when the OAuth app is registered
- This connector targets production (dialpad.com); point your OAuth app at the sandbox host for sandbox testing
Tools
| Tool | Access | Description |
|---|---|---|
| List Contacts | Read | List Dialpad contacts visible to the authenticated user |
| Get Contact | Read | Get details of a Dialpad contact |
| Create Contact | Write | Create a new contact in Dialpad |
| Update Contact | Write | Update an existing Dialpad contact |
| List Users | Read | List Dialpad users in the company |
| Send SMS | Write | Send an SMS message on behalf of a Dialpad user |
Example prompts
- Search my Dialpad contacts for a person and show their phone numbers and emails.
- Send an SMS from my Dialpad number to a contact with a short message.