Resources · Make integration

SMSAlert Make integrationAutomate SMSAlert with Make.

Can a text message go out on its own when something happens in your other tools? The SMSAlert Make integration gives you 6 modules: 5 actions and 1 search. This guide covers connecting your API key, building a first scenario and picking the right module.

Try the SMSAlert integration on MakeSee the 6 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the SMSAlert Make integration do?

The SMSAlert Make integration lets Make, a no-code automation tool, send and follow text messages from your SMSAlert account. You build a scenario, which is the automation itself: a chain of modules, each one a brick that does a single job. SMSAlert brings no trigger of its own, so another app or a schedule starts the chain.

Confirm an order by text. A new order lands in your online store, and Send an SMS message texts the buyer. Add Check message delivery status after it when you need to see what became of that text.

Send a reminder at the right moment. A clinic books an appointment in its calendar tool, and Schedule an SMS message queues the reminder for later instead of sending it now. The scenario runs once; SMSAlert holds the message.

Reach a whole team at once. A field technician closes a ticket, and Send an message to WhatsApp group posts the update where the crew already talks. List received messages covers the other direction, pulling the replies people sent back.

Keep the limits in mind. The official documentation for this app is short and flagged by Make as AI-generated, so check field names inside the module itself. When a listed module falls short, Make an API Call reaches the rest of the SMSAlert API with the same connection. If you also weigh n8n, our n8n vs Make comparison lays out the criteria, and the Make training walks you through your first builds. Stuck on an error? See Make troubleshooting.

Connect

How do you connect SMSAlert to Make?

  1. 01

    Copy your API key from SMSAlert

    Log in to SMSAlert and open the area where API settings live, often labeled API or Developer Settings. Copy your API key and your user information, then keep them somewhere safe. An active SMSAlert account is required.

  2. 02

    Add an SMSAlert module in Make

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

  3. 03

    Paste the credentials and save

    Give the connection a clear label in Connection name if you like; the field is optional. Paste the API key and user details you copied, or follow the on-screen instructions, and save.

First scenario

Your first scenario with SMSAlert

GoalWhen a new order arrives in your store app, Make texts the customer through SMSAlert and then checks what happened to the message.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the +. Pick the app that holds your orders as the first module: it is the event that starts everything.

  2. 02

    Add Send an SMS message

    Click the + to the right of the first module, search for SMSAlert and choose Send an SMS message. Select your connection, or click Create a connection if this is your first SMSAlert module.

  3. 03

    Map the phone number and text

    Fill the fields by mapping data from the order module: the customer phone, plus a short text that includes the order reference. Each order travels as a bundle, one item passed from module to module.

  4. 04

    Follow up with the delivery check

    Add Check message delivery status after the send module and map the message details it returned. Your scenario now sends the text, then asks SMSAlert what became of it.

  5. 05

    Test with Run once

    Click Run once and create a test order with your own phone number. Open each module to read the bundles it received; every module run counts as one operation on your Make plan.

  6. 06

    Schedule and switch it on

    Set the schedule on the first module with the clock icon: a new scenario runs every 15 minutes by default. Then switch the scenario on so it keeps working without you.

Modules

What SMSAlert can do in Make

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

SMSAlert1

Check message delivery status

ActionIn the docs only

This action asks SMSAlert about a message you already sent, so your scenario learns what happened to it instead of assuming it arrived. Place it right after a send module.

When to use it
a payment reminder matters and you want to flag the customers whose text did not go through, then follow up another way.
Watch out
the documentation does not list the statuses it returns, so run it once and read the output bundle before building a filter on it.
SMSAlert2

List received messages

SearchIn the docs only

This search pulls the texts people sent back to your SMSAlert account, one bundle per message, so replies can land in a spreadsheet, a CRM or a support tool.

When to use it
customers answer a confirmation text and your team wants those answers logged next to the order.
Watch out
as with any search, it can return zero, one or many bundles, and every following module runs once per bundle, which adds operations.
SMSAlert3

Make an API Call

ActionIn the docs only

This module opens the rest of the SMSAlert API from inside your scenario, reusing the connection you already created, so you are not stuck when no listed module does the job.

When to use it
you need an SMSAlert feature that none of the five other modules covers.
Watch out
you build the request yourself, so keep the SMSAlert API reference open and test the call with Run once before switching the scenario on.
SMSAlert4

Schedule an SMS message

ActionIn the docs only

Here the text is prepared now and handed to SMSAlert for sending later, which means your scenario does not have to stay around until the right moment.

When to use it
an appointment booking should produce a reminder for the day before, not a text at the moment of booking.
Watch out
pick this one over Send an SMS message only when timing matters; check in the module how it expects the send date before you map one.
SMSAlert5

Send an SMS message

ActionIn the docs only

The workhorse of the app: it sends a text through SMSAlert as soon as the scenario reaches it, with the number and wording you map from earlier modules.

When to use it
a form submission, a shipped parcel or a closed deal should reach someone's phone straight away.
Watch out
each bundle that reaches this module sends one text, so a search placed before it can fire many messages; test with your own number first.
SMSAlert6

Send an message to WhatsApp group

ActionIn the docs only

Rather than a single phone, this action posts to a WhatsApp group through SMSAlert, so a whole crew reads the same update in the chat they already use.

When to use it
a warehouse team should see every urgent order the moment it is flagged, without anyone forwarding it.
Watch out
the documentation says nothing about how groups are chosen or set up, so open the module after connecting and check what it asks for.
Need help

Need help automating SMSAlert with Make?

A person reads every message.

FAQ

SMSAlert and Make: common questions

01Is the SMSAlert Make integration free?
Yes, on the Make side. SMSAlert is a standard app, available from the Free plan. That plan allows 2 active scenarios, at least 15 minutes between scheduled runs, up to 5 minutes per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) lower the interval to 1 minute and allow 40 minutes per run, with usage counted in credits each month. Sending texts through SMSAlert itself depends on your SMSAlert account, which this page does not cover.
02What do you need to connect SMSAlert to Make?
You need an active SMSAlert account and its API key. Log in to SMSAlert, open the section that manages API settings, often called API or Developer Settings, and copy the API key along with the user information shown there. In Make, add any SMSAlert module, click Create a connection, optionally name it, then paste those credentials. The same connection then serves all six SMSAlert modules. If the connection fails, check that both the key and the user details were copied.
03Can the SMSAlert Make integration start a scenario on its own?
No. SMSAlert has no trigger module in Make, so it cannot start a scenario by itself. Two options remain. You can open the scenario with a trigger from another app, such as a form tool or an online store, and place SMSAlert modules after it. Or you can open it on a schedule, starting with a module such as List received messages, which Make runs at the interval you set: 15 minutes by default, and never below 15 minutes on the Free plan.
04What if the SMSAlert module you need is missing in Make?
Use Make an API Call. It is part of the SMSAlert app and reaches any endpoint of the SMSAlert API with the connection you already have, so a feature missing from the five other modules is still within reach. You write the request yourself, so the SMSAlert API reference is the guide. Keep in mind that the Make documentation for this app is marked as AI-generated, so confirm important details with SMSAlert directly.
05Should you use Make or n8n for SMSAlert?
It depends on the tool your team already runs. In Make, SMSAlert brings six modules that cover sending, scheduling, delivery checks, WhatsApp groups and incoming replies, plus Make an API Call for anything else. Many apps also have an n8n node, so check whether SMSAlert does before choosing. Compare what each tool offers for this app, the steps you need and how your other automations are built, rather than picking a winner in general.
Same platform

Other docs you might need on this stack.

Browse all integrations