Twilio n8n integrationAutomate Twilio with n8n.
One node turns any workflow step into a text message or a ringing phone. The Twilio n8n integration ships 2 operations over 2 resources, SMS and Call, plus a trigger, the node that starts a workflow, listening to 2 events. For teams whose alerts have to reach a pocket, not an inbox.
Verified Trustpilot reviews · AI, automation & growth agency
What does the Twilio n8n integration actually do?
The Twilio n8n integration wires a Twilio account into n8n workflows in both directions. The Twilio node sends an SMS, an MMS or a WhatsApp message and places phone calls from any step of a workflow, through 2 operations. The Twilio Trigger does the opposite job: it starts a workflow when a text message comes in, or when Twilio finishes the summary of a call. Both ship with n8n, on Cloud and on a self-hosted instance, with nothing to install.
Take the alert nobody is allowed to miss. A workflow watching a payment queue or a health check ends on call.make, and a phone rings with the message the workflow wrote. Incidents that already land in Slack stay there; the call is reserved for the severity that justifies waking someone up.
Second scenario, a support line that answers back. The trigger fires on com.twilio.messaging.inbound-message.received, the workflow reads what the customer wrote, decides on an answer and returns it with sms.send. Writing each exchange to Google Sheets leaves a searchable history behind, without paying for a helpdesk seat.
Third, reminders where people actually read them. The same sms.send operation delivers to WhatsApp once To Whatsapp is switched on, so a booking flow can confirm an appointment on the channel the customer already uses, then fall back to a plain text for numbers that have no WhatsApp account.
The node stops at 2 operations, which covers sending and calling. Anything else in the Twilio API goes through the HTTP Request node, which reuses the same Twilio credential, the connection you save once in n8n, through predefined authentication, so no second key has to be created for the endpoints the node leaves out.
Two limits are worth knowing before building. Both operations write, so nothing in the node reads message history back into a workflow. The trigger exposes 2 events and offers no wildcard, which means each one is ticked by hand in Trigger On, and the call event depends on Twilio producing its summary first. How that compares with other platforms is covered in the n8n review, and credentials, expressions and error branches are walked through in the n8n training.
How do you connect Twilio to n8n?
- 01
Pick an auth type
Create the Twilio credential once from the n8n Credentials menu, then every workflow picks it from a dropdown. The first field is Auth Type, with two choices. Twilio recommends Auth Token for local testing only, and API Key for production, so a flow meant to run for months should start on the API key path.
- 02
Copy the Account SID
Both methods start with the same value. In Twilio, open Console Dashboard > Account Info and copy the Account SID into the n8n credential. With Auth Token selected, that SID acts as the username and the Auth Token from the same panel acts as the password, which is all the credential needs.
- 03
Create the API key
For production, go to the API keys & tokens page of the Twilio account and select Create API Key. Give it a friendly name such as
n8n integration, choose Main or Standard as the key type, then create it. On the Copy secret key page, paste the SID into API Key SID and the secret into API Key Secret.
What starts a workflow from Twilio ?
Twilio Trigger is the node that starts a workflow when something happens in Twilio. It listens to 2 events, listed below by family. Pick one or several, activate the workflow: n8n registers the webhook on your Twilio account.
What you see in n8n
Every event, by family
One row per object, one chip per action. The event to tick in the node is object.action; hover a chip to read exactly when it fires.
com.*2com.twilio. messaging. inbound-message. received
com.twilio. voice. insights. call-summary. complete
Configuration notes
01Twilio Trigger setup
The Twilio Trigger node is version 1 and starts a workflow when Twilio reports activity on the account. It runs on a webhook, a URL that n8n registers when the workflow is activated and that Twilio calls on each event, so each execution matches something that actually happened on the account.
Key parameters
- Trigger On: the events the node reacts to. Two are on offer, New SMS and New Call, and there is no wildcard entry, so each event the workflow depends on has to be selected here.
02On New SMS
Fires when a text message arrives on a Twilio number, under the catalogue value com.twilio.messaging.inbound-message.received. The workflow receives the message a few seconds after it reaches Twilio, because the webhook pushes it rather than n8n asking for it. An automated answer then feels like a conversation instead of a batch job.
Key parameters
- Trigger On: tick New SMS. On its own, this event covers every inbound message on the account, not one number at a time, so any filtering by number or by keyword happens in the workflow that follows.
sms.send in the next node, or a customer reply that reopens a ticket in the tool the team already uses. The number that wrote in comes with the item, so the answer goes back to the right person without a lookup.03On New Call
Starts the workflow once Twilio has finished the summary of a call, under the value com.twilio.voice.insights.call-summary.complete. The event does not land while the phone is still ringing: Twilio can take up to half an hour to build the summary of a completed call, and that delay shapes what this trigger is good for.
Key parameters
- Trigger On: tick New Call. It reacts to the summary being ready, not to the call starting, so a workflow that has to act while someone is on the line belongs to a different design.
What can the Twilio node do?
The Twilio node exposes 2 operations across 2 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.
Call
1 operationMake a call
call.makeWhat you see in n8n
Notes & use cases
Places a phone call from one of your Twilio numbers and delivers the message the workflow prepared, the moment the node runs. It fits the end of an escalation branch.
Key parameters
- From: the Twilio number the call comes from, in international format such as
+14155238886. - To: the number that rings, same format, typed in or pulled from the incoming item with
{{ $json.field }}. - Message: what the call carries. Switch on Use TwiML to pass Twilio Markup Language instead of plain text and drive the call flow yourself.
- Status Callback (Options): a URL that receives the events Twilio raises about the resources it manages.
SMS
1 operationSend an SMS/MMS/WhatsApp message
sms.sendWhat you see in n8n
Notes & use cases
Sends a message from a Twilio number, and the same operation reaches WhatsApp once the option is enabled. Three channels behind one entry, which is why the action name lists all of them.
Key parameters
- From: the sending number, in the
+14155238886shape, owned by the Twilio account. - To: the recipient. In a reply flow, point it at the number carried by the trigger item.
- Message: the text that is delivered, often built from earlier nodes.
- To Whatsapp: on, the message goes to WhatsApp; off, it leaves as a standard text.
- Status Callback (Options): the URL Twilio notifies about the resources tied to the message.
Need help automating Twilio with n8n?
A person reads every message.