Open app

DocumentationWorkflowsApps and services

Twilio node

Send SMS messages via the Twilio API, e.g. order confirmations, 2FA codes, or alerts straight from your workflow. Learn how to configure it, map inputs and outputs, run a test and resolve common errors.

8 min readUpdated

What this node does

Send SMS messages via the Twilio API, e.g. order confirmations, 2FA codes, or alerts straight from your workflow.

Use Twilio as a clearly defined step in an anymize workflow.

  • Processes one input.
  • Provides one output for following steps.
  • Runs as a regular step in the flow.

Set up the node

  1. 01Open a workflow and add Twilio from the node catalog.
  2. 02Complete the required fields and map values from previous steps.
  3. 03Run the node with a small test record and inspect its output.
  4. 04Connect the successful output and activate the workflow after an end-to-end test.

Operations and modes

Choose the required function in Action. The panel then shows the relevant settings.

  • Send SMS

Settings

FieldMeaningArea
Twilio credentialsSelect your Twilio connection from Secrets. The Account SID and Auth Token are stored separately and encrypted there, here, you only select the ready connection.Protected
ActionChoices: Send SMSStandard
To (phone number)Recipient number in E.164 format (with country code, e.g. +1...).Standard
From (Twilio number)Your Twilio sender number in E.164 format. You can leave this empty if you provide a Messaging Service SID instead.Standard
Messaging Service SID (optional)Alternative to 'From': the SID of a Twilio Messaging Service to send through.Standard
Message bodySMS text (up to 1600 characters; long texts are split into multiple segments and billed accordingly by Twilio).Standard
Status callback URL (optional)Optional webhook URL Twilio calls with delivery status updates.Standard
Run once per itemOff (default): the node runs once for the whole input. On: if it receives several items (e.g. from Split Out), it runs once PER item, and {{ $json }} is that one item each time. This is how you work through a file list entry by entry.Standard
If one item fails"Skip" writes an `error` field for the failed item and keeps processing the rest, instead of losing the whole run to a single unreadable file.Standard
Pause between items (milliseconds)Wait before every run except the first. 1000 = 1 second per item. Useful when the other side would otherwise throttle you. Maximum 300000 (5 minutes).Standard

Inputs and outputs

InputMeaningType
StandardReceives the complete result from the previous step.JSON
OutputMeaningType
StandardMakes the result available to the next step as JSON.JSON

This node can process lists item by item. Error handling and the delay between items are available in advanced settings.

Example and test run

Send an order confirmation SMS after payment: begin with a small, recognizable record. Inspect the output and only map fields that are present there.

Test-run example

{
  "to": "+15558675310",
  "from": "+15017122661",
  "body": "Danke für deine Bestellung! Sie ist unterwegs und kommt in 2-3 Werktagen an."
}

Access and security

Before activation, review which data enters this step and what its output contains.

Store keys and credentials in the protected connection manager. Never paste them into normal workflow fields, test data or descriptions.

Troubleshooting

  • No output: inspect the latest run and confirm that the previous node returned the expected fields.
  • Empty variable: open the previous step output and use a field name from the real test data.
  • List processed once: enable per-item execution in advanced settings.

Related articles