Skip to main content
Integrations · Twilio
Guild agents send SMS, place and inspect calls, manage recordings, conferences, and queues, and administer phone numbers and SIP domains in Twilio. Guild offers two Twilio integrations: one covers the full Twilio REST API, the other covers voice only. Both keep your Twilio credentials server-side, and credential policies decide which operations each agent may call.

Book a demo

See how teams govern agents that use Twilio.

Talk to sales

Get access to Guild, then connect Twilio to your first agent.

Choose an integration

Both integrations call https://api.twilio.com with the same credential format. They differ in what they cover. Use Twilio when an agent needs to send or read messages, or when you want one integration for everything. Use Twilio Voice for an agent that only works with calls, so its tool set stays small.

How it works

1

Encode your Twilio credentials

Join an API key SID and secret, or your Account SID and Auth Token, with a colon, then base64-encode the result. Find them in the Twilio Console under Account Info and API keys & tokens.
2

Connect the credential in Guild

Go to Access & setup > Credentials, click Connect, select twilio or twilio-voice-api-key, and paste the encoded string into API Key.
3

Import tools and pick what you need

Import the integration’s tools and use pick() from the Guild Agent SDK to include only the tools your agent needs.

Why Twilio access needs governing

Twilio tools can send messages that cost money, place calls, and delete phone numbers, recordings, and SIP domains. Guild’s credential proxy checks every outbound request against the credential policies you define before the request reaches Twilio. A policy can restrict an agent to specific operations using exact names or wildcard patterns, and a DENY rule always overrides any ALLOW rule. You can scope rules to specific agents or workspaces, so one agent can read call logs while another can send messages, on the same connected credential. Credentials are stored and injected server-side; agent code never sees your SIDs, secrets, or Auth Token. You can scope a credential to the whole account, a single workspace, a single member, or one agent using the options described in Credentials. An API key is easier to revoke than your Auth Token, so prefer one for agents.

Authentication

  • Type: API key, sent as HTTP Basic authentication
  • Applies to: both integrations
Guild sends the value you enter as Authorization: Basic <value>, so enter your credentials joined by a colon and base64-encoded:
An Account SID and Auth Token work the same way. Most tools also take your Account SID as account_sid, because Twilio’s paths include it. See Credentials for workspace, member, and agent-scoped credentials.

Usage

Twilio

Twilio Voice

Tools

Twilio tools

Tools in the latest published version of guildai~twilio:

Twilio Voice tools

Tools in the latest published version of guildlabs~twilio-voice-api-key:

Frequently asked questions

Yes, with the Twilio integration (guildai~twilio) and its twilio_create_message tool. The Twilio Voice integration doesn’t send SMS.
Yes. Each integration has its own credential, and you can paste the same encoded value into both.
Yes. Write a credential policy that allows only operations such as twilio_voice_api_key_v2_list_calls and twilio_voice_api_key_v2_fetch_call, then add a DENY rule covering create and delete operations. Guild’s credential proxy enforces the policy before any request reaches Twilio. See Credential policies for the rule syntax.
Not yet. Neither integration defines webhook events, so Twilio events can’t trigger agents through Guild.

Put a governed agent on Twilio this week

Book a demo

See how teams govern agents that use Twilio.

Talk to sales

Get access to Guild, then connect Twilio to your first agent.
Also runs on Guild: Discord · Email · Gmail · SendGrid Read: Docs: Credential policies · Credentials · Tools in agents
Last modified on November 16, 2026