Resources · Make integration

SMS Everyone Make integrationAutomate SMS Everyone with Make.

Can a text go out on its own the moment something happens in your other tools? The SMS Everyone Make integration gives you 3 action modules, no trigger. This guide is for ops and marketing folks: link your account, build a first scenario that sends a text, and learn where each module fits.

Try the SMS Everyone integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the SMS Everyone Make integration do for you?

It lets Make send and handle text messages through your SMS Everyone account, with no code. You build a scenario (the automation you assemble in Make, a chain of modules), and each module is one brick of it. Here all 3 SMS Everyone modules are actions: something else has to start the scenario.

Order updates that reach the phone. A store owner starts the scenario from the shop app, then Send an SMS texts the buyer. Each item that moves between modules is a bundle (one order, one contact), and every module run on a bundle is one operation, the unit Make counts on your plan.

Replies pulled into the flow. A support lead can add Receive an SMS to bring messages into a scenario. Its exact behavior isn't described in the documentation, so test it with Run once before relying on it.

Anything the list doesn't cover. Make an API Call reaches any endpoint of the SMS Everyone API with the same connection. A sibling example of messaging setups sits on the 2Chat Make integration page.

What Make won't do here: there is no trigger, so SMS Everyone can't start a scenario by itself. The documentation also warns its content is AI-generated and may contain mistakes, so check anything important with SMS Everyone directly. Plan limits are on Make pricing, and if you also weigh the other tool, read n8n vs Make.

Connect

How do you connect SMS Everyone to Make?

  1. 01

    Get your SMS Everyone credentials

    Sign up for an SMS Everyone account and say during registration that you need credentials for the Make integration. A username and a password then arrive by email. Keep that email close, Make will ask for both.

  2. 02

    Add a module and open the connection

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

  3. 03

    Paste the credentials and save

    Enter the username and the password from the email, or follow the on-screen instructions, and save. Make now shows the connection in the module, and the next SMS Everyone module you add can pick it from the list.

First scenario

Build your first scenario with SMS Everyone

GoalWhen a new order lands in your shop app, Make sends the buyer a text through SMS Everyone.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big +. That first module will not be SMS Everyone, since the app has no trigger: pick the app where your orders appear.

  2. 02

    Set the starting module

    Choose the module of that other app that watches new orders and link its account. Make lists what it can read once the connection exists, so you just pick the right store or list.

  3. 03

    Add Send an SMS

    Click the + on the right, search SMS Everyone and pick Send an SMS. Select your connection, then fill the module fields by mapping data from the order, such as the buyer's details.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time and shows the bundles each module received. Place a test order with your own number first, so the text lands on your phone.

  5. 05

    Schedule it and switch it on

    Open the clock on the first module under Scheduling. A new scenario runs every 15 minutes by default, the Free plan minimum. Keep that or pick another interval, then switch the scenario on.

Modules

What each SMS Everyone module does

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

SMS Everyone1

Make an API Call

ActionIn the docs only

This one gives you the whole SMS Everyone API when the two other modules fall short, and it reuses the connection you already made, so there is nothing new to log into.

When to use it
you need an SMS Everyone feature that neither Send an SMS nor Receive an SMS offers.
Watch out
you write the request yourself, so it suits someone who already knows the SMS Everyone API.
SMS Everyone2

Receive an SMS

ActionIn the docs only

Its name points to bringing text messages into your scenario, so later modules can work with them. In the module list it is filed as an action, not a trigger, so it only runs when something earlier in the scenario starts the flow.

When to use it
a support flow where replies need to reach a ticket or a sheet.
Watch out
the documentation doesn't describe its output, so click Run once and read the bundles before mapping them.
SMS Everyone3

Send an SMS

ActionIn the docs only

Sends a text from your SMS Everyone account the moment the scenario reaches it, with content you map from earlier modules. Most first scenarios end here.

When to use it
a customer should hear about an order, a booking or a delivery without anyone typing a message.
Watch out
every run texts a real phone, so test with your own number before switching the scenario on.
Need help

Need help automating SMS Everyone with Make?

A person reads every message.

FAQ

Questions about the SMS Everyone Make integration

01Is the SMS Everyone Make integration free?
Yes, on the Make side. SMS Everyone is a standard app, available from the Free plan. That plan allows 2 active scenarios, runs scheduled scenarios at most every 15 minutes, and caps each run at 5 minutes. Paid plans go down to a 1 minute interval and allow longer runs. Make counts operations, one per module run on a bundle, so each text sent uses at least one. Your SMS Everyone subscription is separate: check their own pricing page for it.
02What do you need to connect SMS Everyone to Make?
An active SMS Everyone account with a username and a password meant for Make. When you register, state that you need credentials for the Make integration, and SMS Everyone sends both by email. In Make, add any SMS Everyone module, click Create a connection, optionally name it, and paste the two values. That connection then serves all 3 modules, so you only do this once per account, and every new SMS Everyone module picks it from the list.
03Does the SMS Everyone Make integration work in real time?
Not by itself, because SMS Everyone has no trigger module in Make. Something else has to start the scenario. The first option is a trigger from another app, such as your shop or form tool, and SMS Everyone runs right after it. The second is a schedule on the first module: every 15 minutes by default, and never shorter on the Free plan. Whether the whole flow reacts instantly depends on that first app's trigger type.
04What if the SMS Everyone module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the SMS Everyone API with the connection you already set up, so it covers what Send an SMS and Receive an SMS don't. You write that request yourself, so it takes some knowledge of the SMS Everyone API. Also keep in mind that the Make documentation for this app says its content is AI-generated and may contain mistakes, so confirm any important detail with SMS Everyone.
05Should you use Make or n8n for SMS Everyone?
It depends on what your team already runs. On Make, SMS Everyone comes with 3 modules, a guided connection and Make an API Call for the rest, all available from the Free plan. Apps often have an n8n node as well, so check whether one exists for SMS Everyone and what it covers before you decide. Pick the tool where your other apps already live, since your scenario will start from one of them anyway.
Same platform

Other docs you might need on this stack.

Browse all integrations