Communication · wired today
Twilio, wired into your agent workforce
Messages and calls are where work actually gets decided. The Twilio connector is one of 205 executable connectors and gives agents 4 read-only tools, with the credential held in the vault and every call receipted.
Connecting Twilio takes one credential
You provide account sid, auth token from your Twilio account; Quox sends it as HTTP basic credentials. 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: Twilio's own API documentation ↗ covers creating and scoping the credential.
What agents can run against Twilio
get_accountGet the Twilio account this credential belongs to (friendly name, status, type)
list_messagesList recent Twilio SMS/MMS messages, optionally filtered by sender or recipient. Message bodies are not returned
list_callsList recent Twilio voice calls, optionally filtered by caller, callee or status
list_incoming_numbersList the phone numbers owned by this Twilio account
Every tool above is read-only. Write surfaces ship only after live testing, and always behind approval gates.
How proven is this?
This connector was blind shape-proven against the real Twilio 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.
Twilio integration FAQ
What can Quox agents do with Twilio?
Agents can run 4 read-only tools against Twilio: get account, list messages, list calls, list incoming numbers. Every call is receipted in the evidence trail.
What does the Twilio integration need?
You provide account sid, auth token from your Twilio account; Quox sends it as HTTP basic credentials. 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 Twilio 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 Twilio connector?
This connector was blind shape-proven against the real Twilio 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.