Resources · Make integration

NIMBA SMS Make integrationAutomate NIMBA SMS with Make.

Can Make send your SMS for you when something happens in another app? The NIMBA SMS Make integration gives you 7 action modules and no trigger. This page shows how to link your account, build a first scenario and pick the right module.

Try the NIMBA SMS integration on MakeSee the 7 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the NIMBA SMS Make integration do for you?

The NIMBA SMS Make integration lets a Make scenario (the automation you build, a chain of modules) act on your NIMBA SMS account: send a text, store a contact, check your balance. Each module is one brick of that chain, and all 7 are actions, so the scenario always starts from another app or from a schedule.

Text a customer the moment an order lands. Your shop or CRM module starts the scenario, then Send a text message uses the phone number it passed along. Nobody has to copy numbers by hand.

Keep your SMS audience in sync. Put Add a Contact after a form or signup module and every new person also lands in NIMBA SMS, ready for your next campaign.

Watch your credit before it runs dry. A scheduled scenario can call Account Balance and route the result to your team chat. A new scenario runs every 15 minutes by default, and you can change that clock.

What Make will not do here: react on its own to something that happens inside NIMBA SMS, since the app has no trigger. The Make documentation for this app is also marked as AI-generated from the vendor docs, so check anything critical with NIMBA SMS. The same app may exist as an n8n node too; the n8n vs Make comparison lays out the criteria, and our Make review covers the editor itself. If you want the basics first, the Make training starts from zero.

Connect

How do you connect NIMBA SMS to Make?

  1. 01

    Grab your keys in NIMBA SMS

    You need an active NIMBA SMS account. In its dashboard, open the API Keys section: the Service ID is your API key and the Secret token is your API token. Keep both at hand.

  2. 02

    Add a module and create the connection

    In your Make scenario, add any NIMBA SMS module and click Create a connection. A connection is your NIMBA SMS account linked to Make once, then reused by every module of the app. The Connection name field is optional.

  3. 03

    Paste the credentials and save

    Paste the Service ID and the Secret token into the matching fields, or follow the instructions Make shows on screen, then save. The module can now talk to your account.

First scenario

Your first scenario with NIMBA SMS

GoalWhen a new lead shows up in another app, Make adds it to NIMBA SMS and sends a welcome text.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. Pick the app where your leads arrive, such as a form tool or your CRM, and set its trigger.

  2. 02

    Add the contact to NIMBA SMS

    Click the + on the right, search NIMBA SMS, pick Add a Contact and create the connection. Fill its fields with the lead data the first module passes along.

  3. 03

    Send the welcome text

    Add Send a text message after it. Make shows the data of the earlier modules, so map the lead's phone number and write a short welcome message.

  4. 04

    Test with Run once

    Click Run once and create a test lead. Each module shows the bundles it received, a bundle being one item passed along, here one lead. Check that the text reached your own phone.

  5. 05

    Set the schedule and switch it on

    Open the clock on the first module. Every 15 minutes is the default, and the Free plan cannot go lower. Then switch the scenario on and it runs by itself.

Modules

What each NIMBA SMS module does

NIMBA SMS gives you 7 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

NIMBA SMS1

Account Balance

ActionIn the docs only

Account Balance reads your NIMBA SMS credit from inside a scenario, so you know what is left without opening the dashboard. Its name is all the doc gives, so run it once and look at the bundle it returns.

When to use it
before a large send, or on a schedule that alerts your team when credit gets low.
Watch out
each run counts as an operation, one module execution that Make bills on your plan.
NIMBA SMS2

Add a Contact

ActionIn the docs only

Every person who signs up somewhere else can end up in your NIMBA SMS contacts with this module, without anyone retyping a number. It acts on one contact per bundle.

When to use it
right after a form, a checkout or a CRM module, to grow the list you text later.
Watch out
the doc lists no fields, so open the module after creating the connection to see exactly what it asks for.
NIMBA SMS3

Make an API Call

ActionIn the docs only

This one covers everything the six other modules leave out: it calls any endpoint of the NIMBA SMS API with the connection you already set up, no new keys needed.

When to use it
when the action you want has no dedicated module in the list.
Watch out
you write the request yourself, so keep the NIMBA SMS API documentation open while you fill it in.
NIMBA SMS4

Purchase

ActionIn the docs only

Purchase handles buying on your NIMBA SMS account from a scenario, going by its name; the Make doc publishes no description for it. Open it and read its fields before you plan anything around it.

When to use it
only once you have checked what it buys and how it bills you.
Watch out
anything that spends money deserves a Run once on a test scenario first, never a blind activation.
NIMBA SMS5

Send a text message

ActionIn the docs only

The heart of the app, going by its name: your scenario sends an SMS through NIMBA SMS, using data mapped from earlier modules. One bundle in, one message out.

When to use it
order confirmations, appointment reminders, alerts to a field team, any moment another app already knows the phone number.
Watch out
when an upstream module returns many bundles, this module runs once per bundle, so check the count in Run once.
NIMBA SMS6

Sender Name

ActionIn the docs only

Sender Name deals with the name your recipients see as the sender, going by its title, since the doc adds no description. Open the module to see whether it creates, reads or lists sender names.

When to use it
when your texts should show a brand name set up in NIMBA SMS rather than a number.
Watch out
confirm in your NIMBA SMS dashboard what the module actually changed after your first test.
NIMBA SMS7

Verification OTP

ActionIn the docs only

Verification OTP is the module to reach for when you need a one-time code by SMS, based on its name; the doc says nothing else about it. It fits sign-in or phone check flows built in Make.

When to use it
when a form or app step must confirm that a person really owns the number given.
Watch out
test it with your own number and read the returned bundle before you connect it to real users.
Need help

Need help automating NIMBA SMS with Make?

A person reads every message.

FAQ

NIMBA SMS and Make: common questions

01Is the NIMBA SMS Make integration free?
Yes, on the Make side. NIMBA SMS is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution per run and 512 MB of data transfer. Paid plans go down to 1 minute and remove the cap on active scenarios. Your NIMBA SMS account is billed separately, so check its own pricing page for the SMS cost. The Make pricing page on our site breaks down what each Make plan includes.
02What do you need to connect NIMBA SMS to Make?
An active NIMBA SMS account and its API credentials. In the NIMBA SMS dashboard, the API Keys section shows a Service ID, which Make calls the API key, and a Secret token, which Make calls the API token. Add any NIMBA SMS module, click Create a connection, give it a name if you like, paste the two values and save. That connection is then shared by all 7 modules, so the setup happens only once per account.
03Does the NIMBA SMS Make integration react in real time?
No, because NIMBA SMS has no trigger in Make: nothing inside the app can start a scenario. The scenario starts elsewhere. Either another app's trigger fires it, for example a new order or a new form entry, or you set a schedule on the first module, every 15 minutes by default. If the other app offers an instant trigger, meaning it calls Make through a webhook as soon as something happens, your text leaves right after that event.
04What if the NIMBA SMS module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the NIMBA SMS API with the connection you already created, so an action with no dedicated module is still possible. You will need the NIMBA SMS API documentation to fill in the request. Keep in mind that the Make documentation for this app is flagged as AI-generated from the vendor docs and may contain mistakes, so confirm important details directly with NIMBA SMS.
05Should you use Make or n8n for NIMBA SMS?
It depends on the tool your team already uses. On Make, NIMBA SMS brings 7 ready modules, from sending a text to adding a contact, plus Make an API Call for the rest, and it runs on the Free plan. The same app often has an n8n node as well. Neither choice is better by default: compare the modules each side offers for what you need to send, and build where the rest of your automations already live.
Same platform

Other docs you might need on this stack.

Browse all integrations