Resources · Make integration

inMobile - SMS Gateway Make integrationAutomate inMobile - SMS Gateway with Make.

Can Make send your inMobile texts for you? Yes: the inMobile - SMS Gateway Make integration gives you 6 action modules for SMS, contacts and the blacklist. This guide is for teams that already use inMobile, and it walks you to a first working scenario.

Try the inMobile - SMS Gateway integration on MakeSee the 6 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the inMobile - SMS Gateway Make integration do for you?

The integration links your inMobile account to Make so that other apps can send text messages and keep your inMobile contacts up to date without anyone copying data by hand. In Make you build a scenario, the automation itself, from modules, the bricks that each do one job. All 6 inMobile modules are actions: they act when something earlier in the scenario hands them data.

A confirmation text after a booking or an order. Another app starts the scenario, and Send SMS Message writes to the customer with the details it received. If your wording already lives in inMobile, Send SMS Using SMS Templates reuses it instead.

A contact list that follows your CRM. When a record changes elsewhere, Create or Update Contact brings inMobile in line, and Delete Contact removes the person when the record is gone.

An opt-out that sticks. A form answer or an unsubscribe request can call Add Phone Number to Blacklist, and Remove Phone Number From Blacklist reverses it when the person asks again.

What Make does not do here: inMobile has no trigger in Make, so a scenario never starts from an inMobile event, and there is no Make an API Call module to reach anything beyond these six. Make also warns that its documentation for this app is limited. The same app may exist as an n8n node; the n8n vs Make page lays out how the two tools differ, and the Make training covers scenario building from the start.

Connect

How do you connect inMobile - SMS Gateway to Make?

  1. 01

    Add an inMobile module

    In your scenario, click the +, search for inMobile - SMS Gateway and pick any of its modules. Then click Create a connection. A connection is your inMobile account linked to Make once and reused by every inMobile module afterwards.

  2. 02

    Name the connection

    Giving the connection a name is optional, but it helps as soon as you have more than one inMobile account, for example one per brand or per client. A clear name saves you from sending a campaign from the wrong account later.

  3. 03

    Authorize and save

    Authorize Make on the page inMobile shows you, or paste the key inMobile gives you, depending on what the window asks for. Click Save. The module can now use your account and you can fill in its fields.

First scenario

Your first scenario: save the contact, then send the text

GoalWhen another app hands Make a new customer, Make saves them in inMobile - SMS Gateway and sends them a text.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the +. The first module must come from another app, such as your shop, form tool or CRM, because inMobile has no trigger.

  2. 02

    Add Create or Update Contact

    Click the + to the right of the first module, search for inMobile - SMS Gateway and pick Create or Update Contact. Create the connection, then map the name and phone number from the previous module.

  3. 03

    Add Send SMS Message

    Add Send SMS Message after the contact module. Map the phone number again and write the text, dropping in values such as the first name from earlier modules. Each item passing through is a bundle, and each module run on it is an operation.

  4. 04

    Test with Run once

    Click Run once and trigger a test event in your first app, ideally with your own phone number. Open the bundles each module received to check the contact landed in inMobile and the text arrived.

  5. 05

    Schedule and switch on

    Set the schedule on the first module (every 15 minutes by default) and switch the scenario on. From then on, each new customer is saved and texted without you touching anything.

Modules

The 6 inMobile - SMS Gateway modules

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

inMobile - SMS Gateway1

Add Phone Number to Blacklist

ActionIn the docs only

This module puts a phone number on your inMobile blacklist from inside a scenario, so an opt-out recorded in another tool reaches inMobile without a manual step.

When to use it
right after a form, chatbot or support tool records that someone wants no more texts from you.
Watch out
Make documents little about this app, so check in inMobile what the blacklist blocks before relying on it.
inMobile - SMS Gateway2

Create or Update Contact

ActionIn the docs only

You get one inMobile contact per person, created the first time and refreshed after that, which keeps your SMS lists in step with the tool where your customer data really lives.

When to use it
whenever a CRM record, a signup or an order should feed inMobile, and you would rather not check first whether the contact exists.
Watch out
run it with a test contact first, since Make does not document how inMobile matches an existing one.
inMobile - SMS Gateway3

Delete Contact

ActionIn the docs only

Delete Contact removes a person from inMobile when their record disappears elsewhere, so you stop keeping numbers you no longer have a reason to hold.

When to use it
after an account is closed or a data removal request is handled in your main system.
Watch out
a deletion cannot be undone from Make, so test the scenario on a dummy contact and add a filter before you switch it on.
inMobile - SMS Gateway4

Remove Phone Number From Blacklist

ActionIn the docs only

Here the scenario takes a number back off your inMobile blacklist, which lets a customer who opts in again receive your messages without someone editing the list by hand.

When to use it
when a person ticks a consent box again in a form or updates their preferences in your CRM.
Watch out
only call it on a clear new consent, never as a side effect of an ordinary contact update.
inMobile - SMS Gateway5

Send SMS Message

ActionIn the docs only

The core of the integration: Make sends a text through your inMobile account, with a message you write in the module and personalize with data from earlier modules.

When to use it
for one-off messages whose wording depends on the event, such as a delivery update or a booking reminder.
Watch out
each bundle sends one message, so a scenario fed by a long list texts every person on it. Test with Run once on your own number.
inMobile - SMS Gateway6

Send SMS Using SMS Templates

ActionIn the docs only

Instead of typing the message in Make, this module sends a text built from a template you already keep in inMobile, so the wording stays in one place for your whole team.

When to use it
when marketing or support owns the text and changes it in inMobile without opening the scenario.
Watch out
Make gives few details about templates for this app, so create and check the template in inMobile before mapping it.
Need help

Need help automating inMobile - SMS Gateway with Make?

A person reads every message.

FAQ

Questions about the inMobile - SMS Gateway Make integration

01Is the inMobile - SMS Gateway Make integration free?
Yes, on the Make side. inMobile - SMS Gateway is a standard app, so it works on the Free plan, which gives you 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and remove the cap on active scenarios. Usage is counted in operations, one per module run. What inMobile itself charges for texts is a separate question to check with inMobile.
02What does the inMobile - SMS Gateway Make integration require?
An inMobile account and a Make account. Make's documentation lists no special prerequisite for this app and gives no specific connection steps, so the standard Make flow applies. You add an inMobile module, click Create a connection, give it a name if you like, then authorize Make on the inMobile page or paste the key inMobile provides, and click Save. The connection is then reused by every inMobile module in your scenarios, so you only do this once per account.
03Does the inMobile - SMS Gateway integration react in real time?
No, because inMobile has no trigger module in Make, so nothing in inMobile can start a scenario. The scenario starts from another app instead, such as a form, a shop or a CRM, and inMobile acts afterwards. If that first app offers an instant trigger, the one with the lightning badge, the text goes out as soon as the event happens. Otherwise the scenario runs on its schedule, every 15 minutes by default, or at an interval you set on the first module.
04What if an inMobile - SMS Gateway module is missing in Make?
This app has no Make an API Call module, so Make offers only the 6 modules listed on this page and Make itself notes that its documentation for inMobile is limited. If you need something else, such as reading delivery reports, first check whether another SMS app in Make covers it. If not, the help form on this page reaches the team, who can look at your case and suggest another way to build the flow.
05Is Make or n8n better for inMobile - SMS Gateway?
It depends on the rest of your stack more than on inMobile. In Make you get 6 action modules for texts, contacts and the blacklist, no trigger and no generic API module. The same app may also exist as an n8n node, so compare what each tool offers for inMobile before choosing. If your other scenarios already run in one of the two tools, keeping inMobile in the same place is usually the simplest choice for your team to maintain.
Same platform

Other docs you might need on this stack.

Browse all integrations