MobileSMS Zapier integrationAutomate MobileSMS with Zapier.
The MobileSMS Zapier integration gives you 8 actions, with no trigger and no search. MobileSMS never starts a Zap on its own: another app does, then MobileSMS gets a number, reads its texts or checks your balance for you.
Verified Trustpilot reviews · AI, automation & growth agency
What the MobileSMS Zapier integration does for you
MobileSMS gives you phone numbers that are not VoIP numbers, so you can receive verification codes by text and manage them. Through Zapier, those numbers and their messages become steps in an automation started by another tool: a row, a form entry or a message elsewhere sets things off, MobileSMS does the rest.
Three results you can build. A number on request: a new row in your spreadsheet starts the automation, Get Number requests a phone number for the Service and Country in that row, and your team chat receives it. A code read for you: Check SMS looks at the texts of a number for a given service and passes them to the next step, so nobody logs in to copy a code. A long-term number ready to use: Get Unexpired Long Term Number returns your available long-term numbers and Set Number to Receive SMS gets one ready for incoming texts.
What Zapier does not do here. MobileSMS has no trigger, so no text arriving on your number can start a Zap by itself; something else always has to. It has no search step either, so a number is only found through an action that lists your numbers, and nothing that happened before you switch the automation on is replayed. To weigh the same flows on other platforms, open our n8n vs Zapier and Make vs Zapier comparisons.
Zapier vocabulary in one minute
Seven words come back all over this page. Here they are in plain English, once, before the details.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run every time that event happens.
- Trigger
- The event in an app that starts the Zap. MobileSMS has none, so the trigger always comes from another app.
- Action
- What the Zap does once it has started: here, get a number, check its texts or read your balance in MobileSMS.
- Task
- The unit Zapier bills: one action your Zap completes successfully. The monthly count on your plan is a count of those.
- Polling vs instant
- Polling: Zapier checks the app on a timer. Instant: the app calls Zapier when the event happens. It depends on the other app's trigger.
- Filter
- A step that lets the Zap go on only when what arrived meets the condition you set, and stops it there otherwise.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A second action or a filter turns it into one, and it then needs a paid plan.
What a MobileSMS Zap really costs
MobileSMS is not a premium app, so it works on the Free plan. The trigger, from another app, never costs a task: each MobileSMS action that succeeds is billed one task.
- Trigger (other app)0 tasks
- Each successful action1 task
- Free plan100 tasks a month, two-step Zaps
- Premium appNo
A Zap that gets a number from each new row uses one task per row; post that number to your team chat as well and every row counts two. An action that fails is not counted, and a few actions take more than one task. The Free plan gives 100 tasks a month and unlimited Zaps, each stopping at two steps, so a filter or a second action needs a paid plan. The interval grid below applies to the trigger of the other app when it is a polling one.
Connect MobileSMS to Zapier
- 01
Open Apps and add a connection
In your Zapier account, open the Apps page and click + Add connection. You need an account on MobileSMS, plus read or write access on anything you do not own yourself and want the Zap to touch.
- 02
Pick MobileSMS
Type the app's name in the search box of the dialog, select MobileSMS, then click Add connection. A new tab opens, and that is where you sign in, on the MobileSMS side.
- 03
Sign in and grant access
Sign in to your MobileSMS account in that tab, then grant Zapier access to it. The connection is saved once and reused by every MobileSMS step of every Zap you build.
Your first Zap: a number for each new request, sent to your team
GoalEach time a new row lands in your spreadsheet with a Service and a Country, get a phone number from MobileSMS and post it in your team chat.
- 01
Create the Zap and set the trigger
Create a Zap and choose your spreadsheet tool as the app that starts it, with its event for a new row. How that trigger fires depends on that tool, not on MobileSMS.
- 02
Test the trigger
Run the trigger test. Zapier brings back the three most recent items of the connected account, so you map the next steps on a real row rather than an empty one.
- 03
Add Get Number
Add the MobileSMS action Get Number, select your connection, then map the Service and the Country from the row. Both are required.
- 04
Add the chat message
Add the action of your team chat and build the message from what Get Number returned at the test. This second action makes the Zap multi-step, which needs a paid plan.
- 05
Test, then publish
Test each step once and read what came back. When the message looks right, click Publish to switch the Zap on. For a guided start, see our Zapier training.
MobileSMS actions
MobileSMS gives you 8 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Check Balance
ActionIn Zapier“Check balance of account.”
Reads the balance of your MobileSMS account and passes it on, with nothing to fill in.
Get Number
ActionIn Zapier“Get a phone number.”
Requests a phone number from MobileSMS for the Service and the Country you give, both required, and hands it to the next steps.
Get Active Numbers
ActionIn Zapier“Get active list of short term numbers with expiration.”
Lists your active short-term numbers together with their expiration.
Check SMS
ActionIn Zapier“Check sms of a number.”
Reads the texts received by a number for one service. Number and Service are both required.
Get SMS History
ActionIn Zapier“Get SMS history from account.”
Pulls the SMS history of your MobileSMS account, with no box to fill.
Get Long Term Number SMS History
ActionIn Zapier“Get long term number sms history.”
Returns the SMS history of one long-term number, picked by its Number Id, which is required.
Get Unexpired Long Term Number
ActionIn Zapier“Response will show your available unexpired long term numbers”
Shows the long-term numbers still available on your account, the ones that have not expired.
Set Number to Receive SMS
ActionIn Zapier“Set your long term number ready to receive SMS.”
Gets one of your long-term numbers ready to receive texts. The Number ID is required, and it comes from Get Unexpired Long Term Number.
When a MobileSMS Zap breaks
Zapier ties no help article to MobileSMS, and no limit specific to the app is documented. What breaks here are the general limits of any Zap, starting with the trigger of the other app.
Each case below comes from the way Zaps work, not from a fault in your account. Read them before you publish, then again when the first real runs come in. If a Zap still misbehaves, our Zapier troubleshooting page is the next stop.
Nothing from before is replayed
A Zap only reacts to what happens after it is switched on. Rows or requests that already existed in the other app are not picked up; moving that backlog is a separate job.A Zap that sets itself off
A Zap that writes into the very place its own trigger watches can start itself again and again and burn through your tasks. Send results somewhere the trigger does not look.A sudden huge batch
After a bulk import or a migration, a trigger that returns a huge batch at once can be held back by Zapier's flood protection.Same item, one run
On a polling trigger of the other app, Zapier keeps track of what it has already seen, so a same item does not start the Zap twice.
Need help automating MobileSMS with Zapier?
A person reads every message.
