Twilio

Overview

The Twilio connector sends messages through your Twilio account and receives webhooks for replies, calls and delivery status. Each inbound message becomes a typed event with the sender, body and media links, and status callbacks update the run that sent the message.

Teams use it to text drivers when an order is ready, to confirm appointments booked in Salesforce and to page an on-call engineer when a Kafka consumer falls behind.

Supported channels

• SMS and MMS on long codes, toll-free numbers and short codes

• WhatsApp Business senders approved in your Twilio account

• Voice calls and Verify for one-time codes

How webhooks work

Tessel sets the messaging and voice webhook URLs on the numbers or Messaging Service you pick. Every request is checked against the X-Twilio-Signature header before it becomes an event, and status callbacks are matched to the original message SID.

twilio api:messaging:v1:services:update \
  --sid MG3f9a2c1e7b \
  --inbound-request-url https://hooks.tessel.dev/twilio \
  --status-callback https://hooks.tessel.dev/twilio/status

twilio api:messaging:v1:services:update \
  --sid MG3f9a2c1e7b \
  --inbound-request-url https://hooks.tessel.dev/twilio \
  --status-callback https://hooks.tessel.dev/twilio/status

twilio api:messaging:v1:services:update \
  --sid MG3f9a2c1e7b \
  --inbound-request-url https://hooks.tessel.dev/twilio \
  --status-callback https://hooks.tessel.dev/twilio/status

Rate limits

Twilio queues messages per sender. Tessel spreads sends across the numbers in a Messaging Service and backs off on error 20429, so a large batch never drops a message or sends it twice.

Permissions needed

Create a dedicated API key instead of using your auth token. A standard key can send messages and update webhooks. Keep the key in the workspace's region with your other credentials.

• Account SID and a standard API key (SK...)

• Access to the Messaging Service (MG...) or numbers you send from

• Webhook signing with your account's auth token