MSG91 Zapier integrationAutomate MSG91 with Zapier.
The MSG91 Zapier integration gives you 3 actions and no trigger. Send SMS texts one number or several, Launch Campaign starts a campaign built in MSG91, and Entry in Segmento files contacts in a phonebook. The Zap starts in another app, on the free plan.
Verified Trustpilot reviews · AI, automation & growth agency
What the MSG91 Zapier integration does for you
The MSG91 Zapier integration lets your other apps hand messages and contacts to MSG91, the communication tool that sends SMS and runs multi-channel campaigns. Something happens elsewhere, a form entry, a new contact, an order, and Zapier turns it into a text, a campaign or a phonebook entry in MSG91.
Three results people build first. An SMS that answers a form: a new submission starts the Zap and Send SMS texts the number it carries, with the Sender ID and DLT Template ID you fill in. A phonebook that fills itself: each new contact in your CRM goes into a Segmento phonebook through Entry in Segmento. A campaign started by a sale: a new order in your shop runs Launch Campaign, which can go out on WhatsApp, SMS, email, voice or RCS depending on how you built it in MSG91.
What Zapier does not do here: MSG91 has no trigger in the editor, so a reply, a delivery report or any other MSG91 event never starts a Zap. There is no search step either. Launch Campaign does not build the campaign; it starts one you already created in the MSG91 portal. And nothing that happened in your other apps before the Zap was switched on gets sent later.
Still choosing a tool? See our Make vs Zapier comparison, or our Zapier review.
Zapier words in one minute
Seven words come back all over this page. Here they are, in plain English.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run each time the trigger event happens.
- Trigger
- The event in an app that starts the Zap. With MSG91 it always comes from another app, such as a new form entry.
- Action
- What the Zap does once it has started: the step that writes, sends or moves something for you, like Send SMS.
- Task
- The unit Zapier bills: one action your Zap completes successfully. The count on your plan is a count of those.
- Polling vs instant
- Zapier checks a polling trigger on a timer; an instant trigger is reported by the app itself the moment the event happens.
- Filter
- A step that lets the Zap go on only when what arrived meets the condition you set, and stops it otherwise.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A filter or a second action makes one, and it then needs a paid plan.
What an MSG91 Zap really costs on Zapier
MSG91 is not reserved for paid plans: it works on Zapier's free plan. What you pay for is tasks, and only actions use them.
- Free plan100 tasks a month, unlimited two-step Zaps
- MSG91 on the free planYes, not reserved for paid plans
- One MSG91 actionOne task when it succeeds
- Filter or second actionMulti-step Zap, paid plan
The trigger in the other app costs nothing. Each MSG91 action that succeeds counts as a task; an action that fails is not counted. The free plan gives 100 tasks a month and builds two-step Zaps only, so trigger plus Send SMS fits. Add a filter or a second action and the Zap turns multi-step, which needs a paid plan. The grid below is how often Zapier checks a polling trigger: it applies to the other app's trigger if that one is polling, never to MSG91, which has none.
Connect your MSG91 account in three steps
- 01
Open the Apps page
In your Zapier account, open Apps and click + Add connection. A connection is your MSG91 account linked to Zapier once, then reused by every step that calls MSG91.
- 02
Pick MSG91
Type MSG91 in the search box of the dialog and select it in the results. Then click Add connection; a new tab opens where MSG91 asks you to sign in to the account the Zaps will use.
- 03
Sign in and grant access
Sign in to MSG91 in that tab and grant Zapier access to the account. You need an MSG91 account, plus read or write access on anything you do not own yourself and want the Zap to touch.
Your first Zap: a confirmation SMS for each form entry with a phone number
GoalWhen someone fills in your form and leaves a phone number, send them a confirmation SMS through MSG91, and skip the entries that come without one.
- 01
Create the Zap and set the trigger
Create a new Zap and pick your form tool as the app that starts it, on its new-submission event. Test it so Zapier brings back recent entries and you map a real one.
- 02
Add the filter
Add a Filter step from the plus icon and fill the three boxes: the phone field, the rule, the value. A filter makes the Zap multi-step, so this Zap needs a paid plan.
- 03
Add Send SMS
Add MSG91 and choose
Send SMS. Map the phone number into Send SMS To, in international format with the country code, then write the Message and fill Sender ID, Route and DLT Template ID. - 04
Test on your own number
Run the step test and read what came back before going further. Use an entry that carries a number you can check, so you see the real SMS and its wording.
- 05
Publish
Click Publish to switch the Zap on. Only entries submitted after that point get an SMS; the ones already in your form tool are left alone.
MSG91 actions: send, launch, file
MSG91 gives you 3 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Entry in Segmento
ActionIn Zapier“Push your data into Segmento”
Pushes a contact's data into Segmento, in the phonebook you choose, so later sends and campaigns in MSG91 can reach that person.
Launch Campaign
ActionIn Zapier“Launch a campaign which can include Whatsapp, SMS, Email, Voice, RCS etc to your users.”
Starts a campaign you prepared in the MSG91 portal. That campaign can mix WhatsApp, SMS, email, voice, RCS and other channels, as you set it up there.
Send SMS
ActionIn Zapier“Send SMS to user's number(s).”
Texts one number or several from your MSG91 account. Several numbers go in the same field, separated by commas, each in international format with its country code.
When an MSG91 Zap breaks
Zapier attaches no help article to MSG91, so the cases below are the general limits of any Zap, read for this app.
Each card names a case and what to check. For anything else, open our Zapier troubleshooting guide.
Old contacts never get the SMS
A Zap reacts only to what happens after it is published. Contacts and entries already stored in the other app get nothing; reaching them is a separate job.A Zap that keeps restarting
A Zap that writes into the place its own trigger watches can set itself off again and again, and burn through tasks. Keep what the Zap writes out of the watched place.A big import held back
When a bulk import or a migration makes the other app's trigger return a huge batch at once, Zapier's flood protection can hold it back rather than send it all.The same contact seen twice
On a polling trigger, Zapier keeps track of what it has already seen, so the same entry does not start the Zap twice.
Need help automating MSG91 with Zapier?
A person reads every message.
