Short answer: Drop the "Twilio → Send SMS" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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) |
{"To": "+15551234567","From": "+15559876543","Body": "e.g. Hi there, thanks for reaching out.","MediaUrl": "https://example.com/image.jpg"}
{"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.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.