Dialpad

Calls, texts, contacts, and call transcripts.

You connect Dialpad with your Dialpad sign-in or an API key, and workflows can then read and update what that account can in Dialpad, through its API.

Use it in a workflow

Tell the architect, the AI that builds your workflows, what you want done in your own words. For example:

After each support call, add a summary of the Dialpad call to the customer's ticket.

Access and security

With a sign-in, you grant access on Dialpad's own consent screen, and Malleable stores the resulting token, never your password.
An API key you enter never appears in chat and is hidden from the AI. A key saved as a reusable connection is stored with your Malleable account and only sent to Dialpad.
Every run uses the connection the workflow's owner set up, so anyone who can run the workflow acts with that account's access in Dialpad. Connect an account or key with only the access the workflow needs.
You can revoke access at any time in Dialpad's settings.

Malleable is SOC 2 Type II certified and doesn't train AI models on your data. More in Security & data handling and our Trust Center.

Connection details for IT

Workflows reach Dialpad through its public API, with the sign-in or API key you connect. Your Dialpad admin may need to turn on API access first.