Communication · wired today
What can agents actually do with Dialpad?
Messages and calls are where work actually gets decided. The Dialpad connector is one of 205 executable connectors and gives agents 3 read-only tools, with the credential held in the vault and every call receipted.
The Dialpad tool list, exactly as agents see it
list_users— List the users of a Dialpad company (name, job title, emails, extension, state, licence, office membership)get_user— Get one Dialpad user by id (identity, extension, state, duty status, licence, office). Pass 'me' with a user-level API key to get the key's own userlist_calls— List concluded Dialpad calls, most recent first, optionally bounded by start time (direction, state, duration, numbers, target)
Every tool above is read-only. Write surfaces ship only after live testing, and always behind approval gates.
What the Dialpad connector needs
You provide API key from your Dialpad account; Quox sends it as a bearer token. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.
Where to get it: Dialpad's own API documentation ↗ covers creating and scoping the credential.
How proven is this?
This connector was blind shape-proven against the real Dialpad API: every endpoint it declares answered measurably differently from a deliberately bogus control request, without any account or credential involved. It is Beta: proven against the live API surface, not yet run with a real credential.
Dialpad integration FAQ
What can Quox agents do with Dialpad?
Agents can run 3 read-only tools against Dialpad: list users, get user, list calls. Every call is receipted in the evidence trail.
What does the Dialpad integration need?
You provide API key from your Dialpad account; Quox sends it as a bearer token. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.
Do agents see my Dialpad credentials?
No. Credentials live encrypted in the Quox vault and are resolved server-side at call time. Agents invoke tools; they never receive the underlying secret.
How proven is the Dialpad connector?
This connector was blind shape-proven against the real Dialpad API: every endpoint it declares answered measurably differently from a deliberately bogus control request, without any account or credential involved. It is Beta: proven against the live API surface, not yet run with a real credential.