Resources · Make integration

GatewayAPI SMS Make integrationAutomate GatewayAPI SMS with Make.

Need a text message to go out the moment something happens in another tool? The GatewayAPI SMS Make integration gives you 11 modules: 8 actions and 3 searches. This guide shows how to link your account, build a first scenario and pick the right module.

Try the GatewayAPI SMS integration on MakeSee the 11 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the GatewayAPI SMS Make integration do for you?

The GatewayAPI SMS Make integration links your GatewayAPI account to Make, a visual tool where you build a scenario: an automation made of modules, each one a single brick such as an action or a search. Here, those bricks send text messages, read the ones you receive and report on your balance, prices and usage.

Confirm an order by text. A shop records a new order in its store app, and Send an SMS message tells the buyer it arrived. If the text contains accents or emoji, Send an SMS Message Using any Character or Emoji is the one named for that kind of text.

Stop a campaign before the balance runs dry. Put Check Account Balance at the start of a scenario that sends many messages, and add a filter so nothing goes out when the credit looks low.

Collect replies in one place. A support team runs List Received SMS Messages and copies each reply into a spreadsheet or a help desk, one bundle (one item passed to the next module) per message.

Know the limits before you start. GatewayAPI SMS has no trigger in Make, so something else has to launch the scenario: a trigger from another app or the scenario's own schedule. The Make doc for this app is also marked as AI-generated from GatewayAPI's documentation, so test each module once before you rely on it.

New to the editor? The Make training covers the basics, Make pricing explains how operations are counted, and n8n vs Make helps if you are still choosing a tool.

Connect

How do you connect GatewayAPI SMS to Make?

  1. 01

    Copy your API token

    Log in to GatewayAPI and open the dashboard. Click the API section in the main menu, then API keys, and copy the API token shown on screen. That token is what lets Make act on your account.

  2. 02

    Add a module and create the connection

    In your Make scenario, add any GatewayAPI SMS module and click Create a connection. A connection is your GatewayAPI account linked to Make once; every GatewayAPI module in your scenarios reuses it.

  3. 03

    Name it and paste the credentials

    The Connection name field is optional, but a clear name helps when you run several accounts. Paste the token you copied, or follow the instructions Make shows on screen, then save.

First scenario

Your first scenario with GatewayAPI SMS

GoalWhen a new entry lands in another app, Make sends a text message through GatewayAPI SMS.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. Pick the app that holds the event you care about, such as your form tool or your shop.

  2. 02

    Add the GatewayAPI SMS action

    Click the + on the right of that first module, search for GatewayAPI SMS and choose Send an SMS message. Select the connection you created earlier.

  3. 03

    Map the phone number and the text

    Fill the module fields with data mapped from the first module: the customer's number and a short message built from their name or order. Make shows the available values once the first module has run.

  4. 04

    Test with Run once

    Click Run once to execute the scenario one time. Use your own number for this test, then open each module's bubble to read the bundles it received and check the text you got.

  5. 05

    Schedule and switch it on

    On the first module, open the Scheduling clock. A new scenario checks every 15 minutes by default. Keep that or adjust it within your plan, then switch the scenario on.

Modules

What each GatewayAPI SMS module does

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

GatewayAPI SMS1

Check Account Balance

ActionIn the docs only

This module reads the credit left on your GatewayAPI account and hands it to the next module, so a scenario can react to it instead of failing halfway through.

When to use it
place it first in a scenario that sends a batch of messages, then add a filter so the sending modules only run when the balance is enough.
Watch out
it counts as one operation on your Make plan each time it runs.
GatewayAPI SMS2

Get an SMS Message

ActionIn the docs only

You get back the details of one specific SMS message, which is handy when an earlier step gave you its reference and you want to look at it again.

When to use it
after a send, when a later module needs information about that exact message, for instance to log it in a CRM.
Watch out
it works on a single message; to go through many, use one of the search modules instead.
GatewayAPI SMS3

List Received SMS Messages

SearchIn the docs only

Replies sent to your GatewayAPI number come back into your scenario, one bundle per message, ready to be copied into a sheet, a help desk or a chat channel.

When to use it
when customers answer your texts and someone on the team needs to read those answers without logging in to GatewayAPI.
Watch out
as a search, it can return zero, one or many bundles, and every following module runs once per bundle.
GatewayAPI SMS4

List SMS Prices

SearchIn the docs only

Pricing information from GatewayAPI lands in your scenario, so you can store it or compare it without opening the GatewayAPI site each time.

When to use it
when a finance or ops sheet should hold the current SMS prices before someone approves a large send.
Watch out
as a search, it can return many bundles; add an aggregator or a filter if you only want one line in your sheet.
GatewayAPI SMS5

List Usage Data

SearchIn the docs only

Usage figures from your GatewayAPI account arrive as bundles, which turns a manual export into a report that fills itself.

When to use it
when a manager wants to see how many messages went out, sent to a spreadsheet or a dashboard tool connected to the same scenario.
Watch out
the Make doc lists no fields for this module, so run it once and read the output before you map anything.
GatewayAPI SMS6

Make an API Call

ActionIn the docs only

Any endpoint of the GatewayAPI API becomes reachable from your scenario, with the connection you already set up, so you are not stuck when no ready-made module fits.

When to use it
when the other ten modules do not cover the task you have in mind and GatewayAPI's own API does.
Watch out
you have to read GatewayAPI's API documentation to know the path and the body to send.
GatewayAPI SMS7

Send a Scheduled SMS Message

ActionIn the docs only

As its name says, this action prepares a text that goes out later rather than straight away, which suits reminders tied to a date you already know.

When to use it
a booking is created in your calendar app, and the customer should get a reminder closer to the appointment.
Watch out
the Make doc does not describe how the send time is set, so test it on your own number before going live.
GatewayAPI SMS8

Send a Secret SMS Message

ActionIn the docs only

This action sends a message that, going by its name, is meant to stay confidential, such as an access code or a one-off password for a customer.

When to use it
when the content of the text is sensitive and you would rather not use the standard send module.
Watch out
the Make doc gives no detail on what makes it secret; check with GatewayAPI before you rely on that behavior.
GatewayAPI SMS9

Send an Instant-Charge SMS message

ActionIn the docs only

Going by its name, this module sends a text linked to an instant charge, something the plain send module never mentions.

When to use it
only if your GatewayAPI setup already uses instant charging and you want Make to trigger those messages from another app.
Watch out
the Make doc says nothing about who pays or how much, so confirm the terms with GatewayAPI first.
GatewayAPI SMS10

Send an SMS Message Using any Character or Emoji

ActionIn the docs only

Texts written with accents, non-Latin alphabets or emoji go out through this module, which the standard send action is not named for.

When to use it
a restaurant confirming bookings in several languages, or a brand that signs its texts with an emoji.
Watch out
keep a plain version of the message as a fallback, and test it once on a real phone to see how it displays.
GatewayAPI SMS11

Send an SMS message

ActionIn the docs only

The everyday module: one text leaves GatewayAPI for one recipient each time a bundle reaches it, with the number and content mapped from earlier modules.

When to use it
order confirmations, delivery notices or alerts to a technician, any time a plain message is enough.
Watch out
if the previous module returns many bundles, this one sends one text per bundle, so check the count with Run once first.
Need help

Need help automating GatewayAPI SMS with Make?

A person reads every message.

FAQ

GatewayAPI SMS and Make: common questions

01Is the GatewayAPI SMS Make integration free?
Yes on the Make side: GatewayAPI SMS is a standard app, available from the Free plan. That plan allows 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans lower the interval to 1 minute and remove the cap on active scenarios. Each module run counts as one operation. Your GatewayAPI subscription is separate: the doc points to the GatewayAPI pricing page for that part, and nothing about its cost is covered here.
02What do you need to connect GatewayAPI SMS to Make?
You need an active customer account on GatewayAPI and support for TLS, as the doc requires. In GatewayAPI, open the dashboard, go to the API section, then API keys, and copy the API token. In Make, add any GatewayAPI SMS module, click Create a connection, optionally fill the Connection name field, and paste the credentials. The connection is then reused by every GatewayAPI module in your scenarios, so you do this only once per account.
03Can a GatewayAPI SMS scenario start on its own?
Not from GatewayAPI itself: the app has no trigger module in Make, neither scheduled nor instant. You have two ways to start a scenario anyway. Put a trigger from another app first, such as a new form entry or a new order, and add a GatewayAPI module after it. Or begin with a GatewayAPI search like List Received SMS Messages and let the scenario's schedule launch it, every 15 minutes by default, or every minute at the fastest on a paid plan.
04What if the GatewayAPI SMS module you need is missing?
Use Make an API Call. It reaches any endpoint of the GatewayAPI API with the connection you already have, so a feature without its own module is still within reach. You will need GatewayAPI's API documentation to know which path and body to send. Also keep in mind that the Make doc for this app is flagged as AI-generated from GatewayAPI's own material and may contain mistakes, so check anything important with GatewayAPI directly.
05Should you use Make or n8n for GatewayAPI SMS?
It depends on the tool your team already works in. On Make, GatewayAPI SMS comes with 11 modules, a connection you set up once and a Free plan to test on. Whether n8n offers a GatewayAPI node is not covered by this page, so check its node list before comparing. If you run both tools, pick the one where your other apps are already connected, since the SMS step usually sits at the end of a flow that starts elsewhere.
Same platform

Other docs you might need on this stack.

Browse all integrations