MSG91 n8n integrationAutomate MSG91 with n8n.
One node, one job: finish a workflow with a text message. The MSG91 n8n integration ships with n8n and exposes 1 operation, Send SMS, on 1 resource. No MSG91 trigger exists, so the workflow always starts somewhere else. It fits ops and support teams whose alerts have to land on a phone.
Verified Trustpilot reviews · AI, automation & growth agency
What does the MSG91 n8n integration actually do?
The MSG91 n8n integration is the built-in MSG91 node plus an MSG91 credential, which is the stored API key n8n uses to talk to your account. The node turns that connection into a single action: sending an SMS. The resource list is just as short, 1 resource named SMS, so there is nothing to dig for in the dropdown.
Everything else in the workflow does the thinking. MSG91 does the texting.
Start with a sheet. A Schedule Trigger opens a Google Sheets tab every morning, keeps only the rows where a payment is still missing, and each surviving row reaches the MSG91 node with the phone number already sitting in the item. One row, one text.
Second pattern: escalation. A team already reads incident notices in Slack, which works during office hours and fails at two in the morning. Split the branch with an IF node. Routine noise stays in the channel, and anything above your severity bar goes to the person on call through MSG91.
Third pattern: confirmation. An n8n Webhook, meaning a URL that n8n exposes and your site calls, receives a booking. One branch stores the record, another branch texts the customer, and a third can ping the team in Telegram so nobody refreshes a dashboard waiting for it.
The node covers the SMS resource. For an MSG91 endpoint outside that catalog, the HTTP Request node calls it directly and reuses the same credential through predefined authentication, so you never manage a second key. The n8n template library also carries a bare workflow named Send an SMS using MSG91, numbered 511, worth opening once to see the three fields filled in context rather than in a field reference.
Nothing here starts by itself: there is no MSG91 trigger in n8n, and the first node is a Schedule Trigger on a fixed interval, an n8n Webhook called by a third party service, or the trigger of another tool. If you are still weighing the platform, the n8n review digs into that, and the n8n training covers building the branch that feeds the node.
How do you connect MSG91 to n8n?
- 01
Copy your Authentication Key
Authentication runs on an API key. In MSG91, open the user menu and select Authkey to copy your Authentication Key. Back in n8n, open the Credentials menu, create an MSG91 credential and paste the key there. A credential is created once and reused: it lives in n8n rather than inside a single workflow, and every MSG91 node you add later offers it in a dropdown. You need an MSG91 account before any of this.
- 02
Pick up your Sender ID
Log in to the MSG91 dashboard and select Sender Id in the left panel. If the list is empty, select Add Sender Id +, fill in the details, then Save Sender Id. This is the number the message is sent from, and the node asks for it on every send, so keep it within reach while you build.
- 03
Run the node on its own
Drop the MSG91 node into a workflow and choose your credential in the dropdown. Leave the resource on SMS and the operation on Send SMS. Put a phone number you can check yourself in To, country code included, type a short Message, and execute that node alone. A text that arrives before anything is wired upstream tells you the credential and the Sender ID are both fine.
What the MSG91 node can do
The MSG91 node exposes 1 operations across 1 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.
SMS
1 operationSend an SMS
sms.sendWhat you see in n8n
Notes & use cases
Send SMS pushes one transactional text message out of your MSG91 account. Three fields, all required, and the node runs.
Key parameters
- Sender ID: the number the message is sent from, in the shape of
4155238886. Create it in the dashboard first. - To: the destination number, written with its country code, as in
+14155238886. Coming from an earlier node, map it with an expression such as{{ $json.field }}. - Message: the text itself. Plain words and expressions mix freely, which is how each send ends up personal.
Need help automating MSG91 with n8n?
A person reads every message.
