Resources · Make integration

SMSKUB Make integrationAutomate SMSKUB with Make.

Can Make send a text or a login code through SMSKUB when something happens in another tool? Yes. The SMSKUB Make integration gives you 4 action modules. This guide shows what each one does, how to link your account and how to build a first working scenario.

Try the SMSKUB integration on MakeSee the 4 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the SMSKUB Make integration do?

The SMSKUB Make integration lets a Make scenario, meaning the automation you build as a chain of steps, act on your SMSKUB account without code. It has 4 modules, all actions: they do something when the scenario reaches them, and none of them starts a scenario on its own.

An order confirmation that leaves by itself. A web shop records a new order, and the next step, Send a Message, sends the buyer a text written from the order data. Nobody copies a phone number by hand.

A one-time code for a sign-up. A new account appears in your membership tool, Send an OTP sends a one-time code, and later Verify an OTP checks the code the person typed back. It is a simple way to confirm a number belongs to someone.

Anything the list misses. Make an API Call reaches other endpoints of the SMSKUB API with the same account link.

What to keep in mind: Make's own documentation for SMSKUB is limited, because little public information exists about the app. Test every module with real data before you rely on it, and keep the Make troubleshooting guide nearby. SMSKUB may also exist as an n8n node; the n8n vs Make comparison sets the two tools side by side. To learn the editor step by step, see the Make training.

Connect

How do you connect SMSKUB to Make?

  1. 01

    Add an SMSKUB module

    In your scenario, add any SMSKUB module and click Create a connection. A connection is your SMSKUB account linked to Make once, then reused by every SMSKUB module you add later.

  2. 02

    Name the connection

    Giving it a name is optional, but it helps when you run more than one SMSKUB account, for example one per brand. A clear name saves you from picking the wrong sender later.

  3. 03

    Authorize and save

    Either approve Make on the SMSKUB page that opens, or paste the key SMSKUB gives you into the field Make shows. Then click Save and the module is ready to fill.

First scenario

Build your first scenario with SMSKUB

GoalWhen a new order comes in from another app, Make sends the customer a text through SMSKUB.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. Since SMSKUB has no trigger, the first module comes from the app where your orders live.

  2. 02

    Add the starting module

    Search that app by name, pick the module that notices new orders and click Create a connection to link that account. Each order then flows through as a bundle, one item passed to the next step.

  3. 03

    Add Send a Message

    Click the + on the right of the first module, search SMSKUB and choose Send a Message. Connect your account, then map the phone number and the order details from the first module.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time and shows the bundles each module received, so you can confirm the text reached your own test phone.

  5. 05

    Schedule and switch on

    Open the clock on the first module and set how often Make checks for orders, every 15 minutes by default. Switch the scenario on and it keeps working without you.

Modules

What can SMSKUB do in Make?

SMSKUB gives you 4 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

SMSKUB1

Make an API Call

ActionIn the docs only

This module opens the rest of the SMSKUB API to your scenario, reusing the connection you already made. You get access to features the other three modules do not cover.

When to use it
you need an SMSKUB feature that none of the ready-made modules offers.
Watch out
Make documents little about SMSKUB, so you will need the app's own API reference to know which endpoint to call.
SMSKUB2

Send a Message

ActionIn the docs only

Here is the everyday workhorse: a text goes out to a contact the moment your scenario reaches this step, filled with data from earlier modules. Reminders, confirmations and alerts all fit here.

When to use it
an event in another tool, such as a booking or a paid invoice, should warn someone right away.
Watch out
each message is one operation, which is what Make counts on your plan.
SMSKUB3

Send an OTP

ActionIn the docs only

With this action, a person receives a one-time code, the classic way to prove a phone number is really theirs. It is the first half of a check, and Verify an OTP is the second.

When to use it
a sign-up or a sensitive request needs a quick proof of identity before you go further.
Watch out
sending the code is not enough; plan where the person types it back.
SMSKUB4

Verify an OTP

ActionIn the docs only

As its name suggests, this module checks the code someone types back against the one sent, and tells your scenario whether it matches. The answer lets later steps approve or refuse the request.

When to use it
in a separate scenario that starts when the person submits the code, for example from a form tool.
Watch out
it only makes sense after Send an OTP; add a filter so a wrong code stops the flow.
Need help

Need help automating SMSKUB with Make?

A person reads every message.

FAQ

SMSKUB and Make: common questions

01Is the SMSKUB Make integration free?
Yes, SMSKUB is a standard app in Make, so it works on the Free plan. That plan allows 2 active scenarios, runs a scheduled scenario at most every 15 minutes, caps each run at 5 minutes and includes 512 MB of data transfer. Paid plans lower the interval to 1 minute and remove the limit on active scenarios. Make counts usage in operations, one per module run. The cost of your SMSKUB account itself is a separate matter between you and SMSKUB.
02What do you need to connect SMSKUB to Make?
You need two things: an SMSKUB account and a Make account. Make's documentation gives no specific prerequisite and no official connection steps for this app, so you follow the generic flow: add a SMSKUB module, click Create a connection, optionally name it, then either approve Make on the SMSKUB page or paste the key SMSKUB provides, and click Save. The connection is then reused by every SMSKUB module in your scenarios.
03Does SMSKUB trigger Make scenarios in real time?
No, SMSKUB has no trigger module in Make, so it cannot start a scenario by itself. You start the scenario another way: with a trigger from a different app, such as a form or a shop, or with Make's own schedule on the first module, every 15 minutes by default and down to 1 minute on paid plans. SMSKUB then acts as a step inside the flow, sending a message or a code when the scenario reaches it.
04What if the SMSKUB module you need is missing in Make?
Use Make an API Call. It is part of the SMSKUB app in Make and calls any endpoint of the SMSKUB API with the same connection, so features outside the 4 listed modules stay within reach. Keep in mind that Make states its SMSKUB documentation is limited for lack of public information, so rely on SMSKUB's own API reference to build the request and test it with Run once first.
05Should you use Make or n8n for SMSKUB?
It depends on the tool your team already uses. The same app often has an n8n node, and the choice then comes down to the editor you find clearer and the other apps in your workflow. On the Make side, SMSKUB offers 4 modules: sending a message, sending and verifying a one-time code, and an open call to the SMSKUB API. Try the scenario that matters to you in both tools before deciding.
Same platform

Other docs you might need on this stack.

Browse all integrations