Does sending an SMS convert automatically?

Yes, the Send Message action (Send SMS in older versions). It becomes an HTTP Request to Twilio's Messages endpoint with your n8n Twilio credential; From, To and Body are kept, and the account SID is a variable.

What does n8n's Twilio node do?

Two operations: send an SMS, MMS or WhatsApp message, and make a text-to-speech call. Everything else goes through HTTP Request with the Twilio credential.

Is there a Twilio trigger in n8n?

Yes. The Twilio Trigger has two events, On New SMS and On New Call. It subscribes through Twilio Event Streams, not through the phone number's webhook URL.

Auth token or API key?

n8n's docs say Twilio recommends the auth token only for local testing; use an API key (Main or Standard) in production.

Pipedream Twilio steps in n8n

Updated 2026-10-21 · 3 min read · n8n: Twilio (Native n8n node)

Twilio in Pipedream does two jobs: send an SMS when something happens, and react to an incoming SMS or call. n8n has a small native Twilio node, a Twilio Trigger, and the converter turns Pipedream's SMS action into a working call.

The n8n side

Twilio node (n8n-nodes-base.twilio):

SMS: Send (SMS, MMS or WhatsApp)
Call: Make (text-to-speech)

Twilio Trigger: On New SMS, On New Call. It creates a Twilio Event Streams sink and subscription for you, so delivery is asynchronous. n8n notes that a call summary can take Twilio up to 30 minutes to become available.

Everything else (recordings, verification, phone numbers, message lookups) goes through HTTP Request with the Twilio predefined credential.

What maps where

Pipedream (app `twilio`)	In n8n	Status
Send Message (formerly Send SMS)	HTTP Request `POST /2010-04-01/Accounts/{TWILIO_ACCOUNT_SID}/Messages.json` (form: From, To, Body)	automatic
WhatsApp via Twilio (code steps with the `whatsapp:` prefix)	Twilio → SMS → Send with "To Whatsapp" on	manual
Make a Phone Call	Twilio → Call → Make (text-to-speech), or HTTP Request with TwiML URL	manual
Check Verification Token, Create Verification Service	HTTP Request to Twilio Verify	manual
Delete Call, Delete Message, Download Recording Media	HTTP Request	manual
New Incoming SMS (Instant)	Twilio Trigger, On New SMS	manual
New Call (Instant)	Twilio Trigger, On New Call	manual
New Recording, New Transcript Created, New Phone Number	Schedule Trigger + HTTP Request polling	manual

The converted SMS step uses form encoding, as Twilio requires, and reads the account SID from the variable TWILIO_ACCOUNT_SID. Set it once for all workflows.

Credentials

n8n's Twilio credential supports:

Auth Token – Account SID plus Auth Token. Twilio recommends it only for local testing.
API Key – Account SID, API Key SID and secret. Use a Main or Standard key; Standard keys cannot reach API key or Account resources. Restricted keys are untested.

Pipedream's Twilio connection is not exportable.

Typical migration: appointment reminder

Pipedream: Schedule → Google Calendar List Events → code step (loop) → Twilio Send Message. n8n after conversion: Schedule Trigger → HTTP Request (Calendar list, automatic) → Code → HTTP Request (Twilio SMS, automatic). Since n8n runs the SMS node once per item, the code loop can often be replaced by returning one item per event.

Typical migration: SMS auto-reply

Pipedream: New Incoming SMS → OpenAI Chat → Twilio Send Message. n8n: Twilio Trigger (On New SMS) → OpenAI → Twilio → SMS → Send. The trigger sets up its Event Streams subscription when you activate the workflow; the reply goes out as a new outbound message.

Pitfalls

Two listeners during the switch. The n8n trigger uses Event Streams, so it does not replace the number's webhook URL. If Pipedream's source is still active on that number, both workflows react. Turn off the Pipedream workflow when n8n goes live.
Signature validation (only if you use a plain Webhook node as the number's SMS URL instead of the trigger). Twilio signs every webhook with X-Twilio-Signature, an HMAC-SHA1 over the exact URL Twilio called plus all POST parameters, keyed with the auth token. If you validate it yourself in a Code node, use the public URL exactly as configured, including the query string; a reverse proxy that rewrites the URL breaks the check.
TwiML replies. The trigger cannot answer inline. If the Pipedream workflow returned TwiML, use a Webhook node as the number's SMS URL with a Respond to Webhook node that returns TwiML.
Sender rules. US A2P 10DLC registration and alphanumeric sender rules apply the same as on Pipedream; the move does not change them.

How to move your Twilio workflows

Export the workflows from Pipedream.
Upload on /convert; the free report shows the automatic SMS steps and the variables to set.
Download the n8n JSON: 1 workflow is free; full export: $3 per workflow, $19 minimum — coming soon.

See the Pipedream to n8n guide and the code step checker for code using the twilio package. Related: WhatsApp Business, Telegram, Slack.

FAQ

Does sending an SMS convert automatically?: Yes, the Send Message action (Send SMS in older versions). It becomes an HTTP Request to Twilio's Messages endpoint with your n8n Twilio credential; From, To and Body are kept, and the account SID is a variable.
What does n8n's Twilio node do?: Two operations: send an SMS, MMS or WhatsApp message, and make a text-to-speech call. Everything else goes through HTTP Request with the Twilio credential.
Is there a Twilio trigger in n8n?: Yes. The Twilio Trigger has two events, On New SMS and On New Call. It subscribes through Twilio Event Streams, not through the phone number's webhook URL.
Auth token or API key?: n8n's docs say Twilio recommends the auth token only for local testing; use an API key (Main or Standard) in production.