- Integrations
- /
- Twilio
- /
- Actions
- /
- Send SMS
ActionTwilioUpdated May 2026
How do I send an SMS or MMS via Twilio?
Short answer: Drop the "Twilio → Send SMS" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Inputs
The fields this action accepts.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
To Phone Number To | string | Required | E.164 format |
From Phone Number From | string | Required | Your Twilio phone number in E.164 format |
Message Body Body | string | Required | Message body content. Plain text unless the API specifies HTML/markdown. |
Media URL MediaUrl | string | Optional | URL of media to send (MMS) |
Sample request
{"To": "+15551234567","From": "+15559876543","Body": "e.g. Hi there, thanks for reaching out.","MediaUrl": "https://example.com/image.jpg"}
Returns
{"to": "+15551234567","sid": "SM1234567890abcdef","body": "Hello from Twilio!","from": "+15559876543","status": "queued","date_created": "2024-01-01T00:00:00Z"}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for Send SMS.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Send SMS.
What does the Send SMS action do in Twilio?
Sends an SMS (or MMS, by adding MediaUrl) via Twilio to the destination number. US/Canada destinations require 10DLC or short-code registration to avoid carrier filtering.
What inputs does Send SMS require?
Required: To Phone Number, From Phone Number, Message Body. Every input accepts a static value or a variable from any upstream node in your workflow.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if Twilio returns an error?
The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.
Does Send SMS support batch operations?
Yes. Run Send SMS inside a Loop node to process arrays. Tiny Command handles Twilio's rate limits automatically so you don't have to throttle manually.
More actions
Other Twilio actions.
Action
Get Call
Retrieves details about a specific Twilio call by SID: from, to, duration, status, price, and recording info. Used to read back details after a webhook fires.
ActionGet Message
Retrieves details of a sent Twilio message by SID with status (queued, sent, delivered, undelivered, failed), price, and error code. Used to reconcile sends with carrier-reported state.
ActionList Calls
Lists call records from your Twilio account with filters for to, from, status, and date range. Used for usage reports, billing reconciliation, or quality monitoring.
ActionList Messages
Retrieves a list of sent and received messages on your Twilio account, with filters for to, from, status, and date sent. Used for audit and reporting.
ActionLookup Phone Number
Looks up information about a phone number via Twilio Lookup: country, carrier, line type (mobile/landline/voip), and validity. Use to filter signups, fraud-score, or pre-validate before sending SMS.
ActionMake Call
Initiates an outbound phone call via Twilio. The call flow is driven by either a TwiML URL or by passing inline TwiML; required to specify either url or twiml.
Send send sms from your workflows.
Triggered by anything in the catalog. Free tier available. No credit card.