Resources · Make integration

SMSEdge Make integrationAutomate SMSEdge with Make.

Can a signup in another tool land in an SMSEdge list and get a text right away? The SMSEdge Make integration gives you 10 modules for lists, numbers and messages. This guide connects your account and walks you through a first scenario, no code.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the SMSEdge Make integration do for you?

The SMSEdge Make integration links your SMSEdge account to Make so texts and contact lists move without copy and paste. In Make you build a scenario, which is the automation itself: a chain of modules, each module being one brick that performs a single action or search in one app.

Welcome text for every new lead. A lead form in another app starts the scenario, Add a Number to a List files the phone number in the right SMSEdge list, and Send an SMS greets the person. A gym or an online shop can set this up without writing code.

Clean opt-outs. When a customer asks to stop receiving texts in your helpdesk or CRM, Unsubscribe a Number records the request in SMSEdge, so the stop request is logged in the tool that sends your campaigns.

Check an audience before a campaign. List Numbers by a List returns the numbers of a list, one bundle per number (a bundle is one item passed from module to module), and Get List Information reads the list itself. Send the result to a sheet or a chat so someone reviews it first.

SMSEdge has no trigger in Make, so every scenario starts from another app or from a schedule. The Make documentation for SMSEdge also warns that it is AI-generated and may contain mistakes, so test with a real number you own. Compare both platforms in n8n vs Make, learn the editor in Make training, and fix failed runs with Make troubleshooting.

Connect

How do you connect SMSEdge to Make?

  1. 01

    Copy your API key from SMSEdge

    Your SMSEdge account needs to be active. Sign in to SMSEdge, open the settings page of your user profile and copy the API key shown on screen. Make asks for it in the next step, so keep the tab open.

  2. 02

    Add an SMSEdge module and create the connection

    In your Make scenario, add any SMSEdge module and click Create a connection. A connection is your SMSEdge account linked to Make once, then reused by every SMSEdge module. The Connection name field is optional; a clear name helps when you run several accounts.

  3. 03

    Paste the key and save

    Paste the API key you copied from SMSEdge into the connection window, or follow the instructions Make displays, then save. Once it is saved, the module shows your connection and you can fill in its fields.

First scenario

Build your first scenario with SMSEdge

GoalWhen a new lead reaches another app, Make adds the phone number to an SMSEdge list and sends a welcome text.

  1. 01

    Create the scenario

    Open the Scenarios page in Make, create a new scenario and click the big + to place the first module. Pick the app where your leads arrive, such as your form or CRM, since SMSEdge has no trigger.

  2. 02

    Add Add a Number to a List

    Click the + on the right of that first module, search for SMSEdge and choose Add a Number to a List. Create the connection, pick the list, and map the phone number coming from the first module.

  3. 03

    Chain Send an SMS

    Add one more module with the + and choose Send an SMS. It reuses the same connection. Map the phone number again from the first module and write your welcome message.

  4. 04

    Test with Run once

    Click Run once and submit a test lead with your own phone number. Open each module to read the bundles it received, and check that the number and the text arrived as planned.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module, which is every 15 minutes by default, then switch the scenario on. Each module run counts as an operation, the unit Make tracks on your plan.

Modules

What each SMSEdge module does in Make

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

SMSEdge1

Add a Number to a List

ActionIn the docs only

This action puts a phone number into one of your SMSEdge lists, so a new contact joins the right audience without anyone typing it in.

When to use it
right after a signup, a purchase or a booking recorded in another app, feeding the number from that module.
Watch out
it acts on one number per bundle, so a scenario that receives many contacts runs it once for each and uses one operation each time.
SMSEdge2

Create a New List

ActionIn the docs only

You get a fresh, empty SMSEdge list created from your scenario, ready to receive numbers for a new campaign or a new segment.

When to use it
when an event in another tool, such as a new store or a new product launch, calls for its own audience.
Watch out
a scenario that runs repeatedly may create a list on every run; add a filter so it only fires when a new audience is really needed.
SMSEdge3

Delete a List

ActionIn the docs only

This module removes a whole list from your SMSEdge account, which keeps your workspace tidy once a campaign is over.

When to use it
after a one-off promotion ends and its temporary list has served its purpose.
Watch out
a deletion cannot be taken back from Make, so test it with Run once on a throwaway list before pointing it at real data.
SMSEdge4

Delete a Number from a List

ActionIn the docs only

Here you take one phone number out of a specific list while the list itself stays in place, so the contact stops being part of that audience.

When to use it
a customer upgrades from trial to paid and should no longer sit in the trial list.
Watch out
leaving a list is not an opt-out. Someone asked you to stop texting them? Reach for Unsubscribe a Number.
SMSEdge5

Get List Information

ActionIn the docs only

With this module your scenario reads what SMSEdge holds about one list, so later modules can use those details instead of guessing.

When to use it
before a send, to confirm the list you are about to target exists and is the one you expect.
Watch out
run it once with Run once and open the bundle to see exactly which details come back before you map them.
SMSEdge6

Get a Number Info

ActionIn the docs only

You look up a single phone number in SMSEdge and receive what the account knows about it, which helps a scenario decide what to do next.

When to use it
when a number arrives from a form or a CRM and you want to check it before adding it or texting it.
Watch out
the returned details are not documented on the Make side, so read the output of a test run before building filters on it.
SMSEdge7

List Numbers by a List

SearchIn the docs only

This search returns the numbers stored in one list, one bundle per number, so you can export an audience or act on each contact.

When to use it
to copy a list into a spreadsheet for review, or to loop over its members with another module.
Watch out
a search can return zero, one or many bundles, and every module placed after it runs once per number, which adds up in operations.
SMSEdge8

Make an API Call

ActionIn the docs only

This module lets you reach any endpoint of the SMSEdge API with the connection you already set up, which covers what the nine other modules leave out.

When to use it
when a feature you need in SMSEdge has no dedicated module in Make.
Watch out
you describe the request yourself, so keep the SMSEdge API documentation open and test each call with Run once before activating.
SMSEdge9

Send an SMS

ActionIn the docs only

This is the module that actually sends a text message through your SMSEdge account, so an event anywhere in your stack can reach a phone.

When to use it
for a welcome message, an order update or a reminder triggered by another app in the scenario.
Watch out
every run sends a real text, so test with your own number and keep an eye on the schedule before switching the scenario on.
SMSEdge10

Unsubscribe a Number

ActionIn the docs only

Use this action to mark a phone number as unsubscribed in SMSEdge, so the person's request to stop receiving texts is recorded where campaigns are sent.

When to use it
when a stop request lands in your helpdesk, your CRM or a form and should reach SMSEdge without manual work.
Watch out
this differs from Delete a Number from a List; pick it whenever the contact asked to stop.
Need help

Need help automating SMSEdge with Make?

A person reads every message.

FAQ

SMSEdge and Make: frequent questions

01Is the SMSEdge Make integration free?
Yes, on the Make side. SMSEdge is a standard app, so its modules work on the Free plan. That plan allows 2 active scenarios, a minimum of 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 and Enterprise) bring the interval down to 1 minute and remove the cap on active scenarios. Your SMSEdge subscription is separate: check the SMSEdge pricing page for that part.
02What do you need to connect SMSEdge to Make?
You need an active SMSEdge account and its API key. Sign in to SMSEdge, open your user settings page and copy the API key displayed there. In Make, add any SMSEdge module, click Create a connection, give it a name if you like, and paste the key. The same connection then serves all 10 SMSEdge modules, so you only do this once per account. If the connection fails, copy the key again and check that the account is still active.
03Can SMSEdge start a Make scenario in real time?
No. SMSEdge has no trigger module in Make, scheduled or instant, so it cannot start a scenario on its own. You start the scenario from another app instead, for example the form, shop or CRM where the event happens, and place SMSEdge modules after it. You can also start from a schedule set on the first module, which is every 15 minutes by default. On the Free plan the minimum interval is 15 minutes; paid plans go down to 1 minute.
04What if an SMSEdge module is missing in Make?
Use Make an API Call. It reaches any endpoint of the SMSEdge API with the connection you already have, so a feature without its own module is still within reach. You write the request yourself, which means reading the SMSEdge API documentation and testing with Run once. Keep in mind that the Make documentation for SMSEdge is flagged as AI-generated and may contain mistakes: when a detail matters, confirm it with SMSEdge directly before relying on it.
05Should you use Make or n8n for SMSEdge?
It depends on the platform your team already runs. On Make, SMSEdge offers 10 modules covering lists, numbers, opt-outs and sending, plus Make an API Call for the rest, and it works on the Free plan. Many apps also have an n8n node, so check whether SMSEdge has one before you choose. Base the decision on the modules you need and on which editor your team is comfortable in; the n8n vs Make comparison on this site lays out the criteria.