Resources · Zapier integration

inMobile - SMS gateway Zapier integrationAutomate inMobile - SMS gateway with Zapier.

The inMobile - SMS gateway Zapier integration offers 6 operations: 0 triggers and 6 actions. It cannot start a Zap on its own side, but any other app can make it send a text, use a template, update a list or block a number.

See the 6 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the inMobile - SMS gateway Zapier integration does

inMobile is an SMS gateway: a service that sends personalised text messages from your account, keeps recipient lists, and stores reusable message templates. On Zapier, it only ever acts. Another app starts the Zap, and inMobile does the sending or the list work.

Three results come up again and again. A signup in your form tool lands in the right inMobile list with Create or Update Contact, then gets a welcome text through Send SMS Using SMS Templates, so the wording stays the one your team approved. An order or a booking somewhere else triggers Send SMS Message with a personal confirmation. And someone who asks to stop receiving texts is added with Add Mobile Number to Blacklist, which blocks any further SMS to that number.

What it cannot do: there is no trigger at all, so an incoming SMS, a delivery report or a new list member in inMobile never starts a Zap. There is no search step either, so a Zap cannot check whether a number already sits on a list before acting. Templates and lists are created in your inMobile account, not from Zapier.

Comparing tools? The inMobile - SMS gateway Make integration covers the same app on Make, and Make vs Zapier explains how each one bills.

Vocabulary

Zapier terms in one minute

Seven words, defined once here and reused without a reminder below.

Zap
An automation on Zapier: one trigger, then one or more actions that run each time the trigger event happens.
Trigger
The event that starts a Zap. inMobile has none, so this first step always comes from another app, like a form or a shop.
Action
What the Zap does once started. Every inMobile operation is an action: send a text, update a list, block a number.
Task
The unit Zapier bills: one action completed successfully. Your plan's allowance is a count of those.
Polling or instant
A polling trigger is checked by Zapier on a timer; an instant one is reported by the app. Which applies depends on the app that starts your Zap.
Filter
A step that lets the Zap continue only when what arrived meets your condition, and stops it otherwise.
Multi-step Zap
Any Zap beyond one trigger and one action. A second action or a filter makes one, and it needs a paid plan.
Cost

What an inMobile Zap costs

inMobile - SMS gateway is not a premium app: you can use it on the free Zapier plan.

  • Free plan100 tasks a month, unlimited Zaps
  • inMobile triggersNone
  • Premium appNo
  • Two actions in one ZapPaid plan required

The trigger of the other app never costs a task. Every inMobile action that succeeds counts once, and an action that fails is not counted. A Zap that adds a contact and then sends a templated text uses two tasks per run. The free plan includes 100 tasks a month but only two-step Zaps, one trigger and one action, so that contact-plus-text Zap already needs a paid plan. How fast it starts depends on the other app's trigger and the grid below.

Connect

Connect inMobile - SMS gateway

  1. 01

    Go to Apps

    In Zapier, open Apps and click + Add connection. A connection is your inMobile account, linked once and reused by every inMobile step in every Zap you build.

  2. 02

    Select inMobile

    Search for inMobile - SMS gateway in the dialog, pick it, then click Add connection. The inMobile account has to exist first; Zapier does not create it.

  3. 03

    Sign in and grant access

    Log in to inMobile in the tab that opens and allow Zapier in. If the lists or templates belong to a colleague's account, check that yours can use them before you build.

First Zap

Your first inMobile Zap

GoalEach new form response that meets your condition adds the person to an inMobile list and sends them a welcome text built from a template.

  1. 01

    Build: start from your form

    Create a Zap and pick your form tool as the trigger app, with its event for a new response. Test it so you have a real response to map from.

  2. 02

    Add the filter

    From the plus icon, add Filter: the field, the rule, the value. Use a text rule on text; picking the wrong rule type is why a filter never passes.

  3. 03

    Add Create or Update Contact

    Pick inMobile - SMS gateway, event Create or Update Contact. Choose the list and map the phone number from the form; both are required.

  4. 04

    Add the templated text

    Add Send SMS Using SMS Templates, choose your template and map the same phone number as receiver. Both fields are required.

  5. 05

    Test, then Publish

    Test each step and check that the text reached a phone you own. Then click Publish. With a filter and two actions, this Zap needs a paid plan.

Actions

inMobile - SMS gateway actions, grouped by job

inMobile - SMS gateway gives you 6 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Add Mobile Number to Blacklist

Action

In Zapier“After this, you will not be able to send SMS messages to the mobile number.”

Blocks a mobile number so your account can no longer text it. A required switch decides whether it also leaves every list.

When to use it
someone replies that they want no more messages through your support tool.
Watch out
once blocked, every send to that number stops until you remove it.
2

Create or Update Contact

Action

In Zapier“Creates a new contact or updates an existing contact.”

Adds a phone number to an inMobile list, or updates it if it is already there, so one step covers both cases.

When to use it
keeping a newsletter list in step with signups from your website.
Watch out
the list is required and must already exist in your inMobile account.
3

Remove Mobile Number From Blacklist

Action

In Zapier“Then you will again be able to send SMS messages to the mobile number.”

Lifts the block on a mobile number, so your account can text it again. Only the phone number is required.

When to use it
a former customer opts back in through a new signup form.
Watch out
it only lifts the block; to put the number on a list, add Create or Update Contact.
4

Delete Contact

Action

In Zapier“Deletes a Contact”

Removes a phone number from one list you choose. The list and the number are both required.

When to use it
a customer cancels a subscription and should leave the matching SMS list.
Watch out
it only touches that list. To stop all texts to the number, use the blacklist instead.
5

Send SMS Message

Action

In Zapier“Send SMS messages via your inMobile account from Zapier.”

Sends a text through your inMobile account with the receiver, the message and the sender you set, all three required.

When to use it
a dentist's booking tool confirms each new appointment with a personal text.
Watch out
a text sender holds 3 to 11 characters and a number sender up to 14 digits; anything longer is cut off.
6

Send SMS Using SMS Templates

Action

In Zapier“Create SMS templates at your inMobile account and use the SMS template when you send SMS messages from Zapier.”

Uses a message template saved in inMobile to build the text, so the wording stays consistent from one Zap to the next.

When to use it
a welcome message for every new subscriber, written once by marketing.
Watch out
templates are created and edited in inMobile; the Zap only picks one.
When it breaks

When an inMobile Zap breaks

Zapier attaches no help article to inMobile, so these cases come from the field rules of the app and from Zapier itself.

No rate limit specific to inMobile is on record. What does break is either a field inMobile quietly trims, or a rule Zapier applies to every app. Read these four before you publish, and keep the Zapier troubleshooting page handy for the day a run fails.

  • A long text gets truncated

    The message field accepts up to 10,000 characters. Past that, inMobile cuts the text and still sends it, so the end of your message never arrives.

  • A sender name that is too long

    A text sender holds 3 to 11 characters and a number sender up to 14 digits. A longer value is cut off, and the phone shows a sender you did not intend.

  • Nothing from before the Zap

    A Zap only reacts to events that happen after you switch it on. Contacts or orders that already existed in the other app are not processed.

  • A sudden flood of runs

    If the trigger app suddenly returns a huge batch, after an import for example, Zapier's flood protection can hold the runs back before any text goes out.
Need help

Need help automating inMobile - SMS gateway with Zapier?

A person reads every message.

FAQ

inMobile - SMS gateway Zapier integration: FAQ

01Is the inMobile - SMS gateway Zapier integration free?
On the Zapier side, yes: inMobile - SMS gateway is not a premium app, so it works on the free plan. That plan gives you 100 tasks a month and unlimited Zaps, each limited to two steps: one trigger and one action. Since inMobile has no trigger, that means one inMobile action after a trigger from another app. Add a second action or a filter and the Zap becomes multi-step, which needs a paid plan.
02How many tasks does an inMobile Zap use?
One task per inMobile action that succeeds, and nothing for the trigger. A Zap that only sends a text costs one task per run. A Zap that adds the person to a list and then sends a templated text costs two. An action that fails is not counted. Keep in mind that the trigger comes from another app, and checking that app for new items does not cost anything either, however often Zapier looks.
03Is inMobile real time on Zapier, and how does a Zap start?
inMobile has no trigger, so it never starts a Zap by itself. The speed depends on the app you start from. If that app has an instant trigger, the Zap runs as soon as the event happens, whatever your plan. If it is a polling trigger, Zapier checks on a timer: every 15 minutes on Free, 2 on Professional, 1 on Team and Enterprise. Pick a starting app with an instant trigger when a text must go out fast.
04What does connecting inMobile to Zapier require?
An inMobile account, plus access to the lists and SMS templates your Zaps will use. You add the connection once from Apps with + Add connection, sign in to inMobile in the new tab and grant access. Every inMobile step then reuses it. Create your lists and templates in inMobile beforehand, because the contact actions require a list and the template action requires a template, and Zapier only offers existing ones.
05Which phone number formats does inMobile accept?
Quite a few. The phone number can include the country code or not, start with 00 or +, and contain spaces. inMobile validates it against the country code you set in the next field, so a number written with a plus sign, with a double zero or with no prefix at all goes through. That tolerance helps a lot when numbers come from a form typed by hand, since people write them in every possible way. Test with a number you own before you publish.
06What if an inMobile operation is missing on Zapier?
Then the integration does not offer it today. Zapier lists six actions for inMobile and no trigger or search, so nothing reacts to an incoming SMS and nothing looks up a contact. Sometimes the need can be met another way, for example by starting from the app where the event really happens. If not, ask inMobile whether they plan to add it, or check whether another platform exposes it before building a fragile workaround.
07Zapier, Make or n8n for inMobile - SMS gateway?
Choose by criterion rather than by ranking. On Zapier, inMobile works from the free plan, every successful action counts as a task, and the integration only acts, never triggers. List the inMobile steps your flow needs, then check which platform exposes them, including any trigger you would like to have. Then compare what one run of your flow costs on each. The decision usually comes from those checks, not from a general opinion about the tools.
Same platform

Other docs you might need on this stack.

Browse all integrations