Resources · Make integration

sendSMS Make integrationAutomate sendSMS with Make.

Can Make send your sendSMS texts for you? The sendSMS Make integration gives you 14 action modules for messages, contacts, groups and block lists. This page is for anyone who already uses sendSMS: link the account, then build a first working scenario step by step.

Try the sendSMS integration on MakeSee the 14 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the sendSMS Make integration do?

The sendSMS Make integration links your sendSMS account to Make, so a scenario (the automation you build in Make, a chain of modules) can send texts and manage your sendSMS contacts without you opening the dashboard. Every one of its 14 modules is an action: something else has to start the scenario.

A text that goes out on its own. Put Send an SMS after a module from another app, such as a new form entry or a new order, and the message leaves as soon as that event reaches Make. If your sending must follow GDPR rules, the app also lists a separate Send an SMS - GDPR module.

A contact list that stays clean. Add a Contact, Update a Contact and Delete a Contact keep sendSMS aligned with your CRM or signup sheet, while Add a Group sorts people into audiences before a campaign.

Opt-outs that are respected. When someone asks to stop receiving texts, Add to Block List records it, and Block List Check lets the scenario look before it sends. Afterwards, Get Message Statuses tells you what happened to what was sent.

What Make will not do here: react to an event inside sendSMS, because the app has no trigger module. The scenario starts from another app or from a schedule. If you also weigh n8n, the n8n vs Make comparison helps you pick a tool, the Make pricing page explains plans, and Make training walks you through the editor.

Connect

How do you connect sendSMS to Make?

  1. 01

    Copy your login name and API key

    Log in to sendSMS and open the Contul meu section, then the Chei API tab. Copy the login name shown on the page and the API key next to it. You need an active sendSMS account to see them.

  2. 02

    Add a sendSMS module in Make

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

  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 login name and API key you copied, or follow the on-screen instructions, and save.

First scenario

Your first scenario with sendSMS

GoalWhen a new lead arrives in another app, Make saves the person in sendSMS and sends a welcome text.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. Pick the app where your leads land first, such as your form tool, since sendSMS has no trigger of its own.

  2. 02

    Add Add a Contact

    Click the + to the right of that first module, search for sendSMS and choose Add a Contact. Create the connection, then map the lead's details from the previous module into the fields Make shows.

  3. 03

    Add Send an SMS

    Add one more module after it: Send an SMS. It reuses the same connection. Write your welcome text and map the recipient from the data the earlier modules passed along.

  4. 04

    Test with Run once

    Click Run once, then create a test lead with your own phone. Open each module's bubble to read the bundle it received (a bundle is one item passing between modules, here one person).

  5. 05

    Schedule and switch on

    Open the clock on the first module to set how often Make checks for new leads, every 15 minutes by default, then switch the scenario on. Every module run on a bundle counts as one operation on your plan.

Modules

What the sendSMS modules do

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

sendSMS1

Add a Contact

ActionIn the docs only

Puts a new person into your sendSMS contacts, so the numbers you collect elsewhere become reachable from sendSMS without any copy and paste.

When to use it
right after a signup, a purchase or a form entry in another app, before any text goes out to that person.
Watch out
if the person might already exist, run Get Contacts first and check whether they are there, so you do not create the same contact twice.
sendSMS2

Add a Group

ActionIn the docs only

Creates a new group in sendSMS, which gives you a named audience you can fill with contacts and target together instead of picking numbers one by one.

When to use it
when a new event, store or product line starts and you want its contacts kept apart from the rest.
Watch out
run it once per audience; placed in a scenario that fires for every lead, it would create a fresh group on each run.
sendSMS3

Add to Block List

ActionIn the docs only

Records a number on your sendSMS block list, so you keep a trace that this person should no longer receive your texts.

When to use it
when an unsubscribe request arrives through a form, a support ticket or a reply handled in another app.
Watch out
the doc does not say how the block list affects sending on its own, so pair it with Block List Check in your sending scenarios.
sendSMS4

Block List Check

ActionIn the docs only

Asks sendSMS whether a number sits on your block list, which lets the scenario decide before a message leaves rather than apologize after.

When to use it
just before Send an SMS in any campaign scenario, followed by a filter that stops blocked numbers.
Watch out
run a test with Run once on a blocked and an unblocked number, and read the output bundle to see what Make gets back.
sendSMS5

Delete a Contact

ActionIn the docs only

Removes a person from your sendSMS contacts, which keeps your list in step with the customers who left your main database.

When to use it
when an account is closed or a record is erased in your CRM and the number has no reason to stay in sendSMS.
Watch out
the app lists no module to restore a contact, so treat a deletion as final; test on a dummy contact with Run once before you point it at real people.
sendSMS6

Delete a Group

ActionIn the docs only

Removes a whole group from sendSMS, which clears out audiences that served a finished campaign so your dashboard stays readable.

When to use it
once an event or promotion is over and its group has nothing left to send.
Watch out
the doc does not say what happens to the contacts inside the group, so check in sendSMS on a test group before relying on it.
sendSMS7

Delete from Block List

ActionIn the docs only

Takes a number back off your block list, so a person who opts in again can receive your texts once more.

When to use it
when someone ticks a consent box again on a form or asks support to resume messages.
Watch out
only trigger it from a clear consent event, never from a routine sync, or you could undo an unsubscribe by mistake.
sendSMS8

Get Contacts

ActionIn the docs only

Pulls your sendSMS contacts into the scenario, which lets you copy them to a sheet, compare them with your CRM or check who is already there.

When to use it
when you need an export or a lookup before adding or updating someone.
Watch out
if it returns several contacts, each one may travel as its own bundle, and every module after it then runs once per contact.
sendSMS9

Get Groups

ActionIn the docs only

Lists the groups that exist in your sendSMS account, so the scenario can find the right audience instead of relying on a name typed by hand.

When to use it
before Add a Group, to see whether the audience already exists, or to report on the groups you keep.
Watch out
read the output with Run once first to learn what Make returns for each group before mapping it anywhere.
sendSMS10

Get Message Statuses

ActionIn the docs only

Fetches the status of messages you sent, which tells you whether texts reached people instead of assuming they did.

When to use it
after a campaign, to write outcomes to a sheet or flag failed numbers in your CRM for a follow-up.
Watch out
place it in a separate scenario or after a delay; checking the instant a text leaves may not show its final state yet.
sendSMS11

Make an API Call

ActionIn the docs only

Reaches any endpoint of the sendSMS API with the connection you already set up, which covers what the other sendSMS modules leave out.

When to use it
when the sendSMS API documentation offers an operation you need and no listed module handles it.
Watch out
you write the request yourself, so keep the sendSMS API documentation open and test with Run once before any real sending.
sendSMS12

Send an SMS

ActionIn the docs only

Sends a text message through your sendSMS account, turning an event in another app into a message on someone's phone with no manual step.

When to use it
for confirmations, reminders or alerts that follow a booking, an order or a status change elsewhere.
Watch out
each bundle reaching this module sends one text, so a search returning many rows upstream means many messages; test on your own number first.
sendSMS13

Send an SMS - GDPR

ActionIn the docs only

Sends a text through the separate GDPR module that sendSMS lists in Make, which matters when your sending process has to follow that regulation and someone will ask how the text went out.

When to use it
for marketing or customer texts where your legal team asked for the GDPR route rather than the standard one.
Watch out
the doc does not explain how it differs from Send an SMS, so confirm with sendSMS before switching a live scenario.
sendSMS14

Update a Contact

ActionIn the docs only

Changes the details of a contact already stored in sendSMS, so a new number or name in your CRM follows through to your texting list.

When to use it
when a customer edits a profile, or when a record is corrected in the tool you treat as the source of truth.
Watch out
you must point it at the right contact, so pull it first with Get Contacts and map its identifier from there.
Need help

Need help automating sendSMS with Make?

A person reads every message.

FAQ

sendSMS and Make: common questions

01Is the sendSMS Make integration free?
Yes, on the Make side. sendSMS is a standard app, so it works on the Free plan, which gives you 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) lift the interval to 1 minute and allow unlimited active scenarios. Your sendSMS subscription is separate: check the sendSMS pricing page for what it covers.
02What do you need to connect sendSMS to Make?
An active sendSMS account and its API credentials. In sendSMS, open Contul meu, then the Chei API tab, and copy the login name and the API key shown there. In Make, add any sendSMS module, click Create a connection, give it a name if you like, and paste both values. That one connection then serves all 14 modules, so you only do this once per sendSMS account. If you manage several sendSMS accounts, create one connection for each and name them clearly.
03Can the sendSMS Make integration react in real time?
No, not on its own. sendSMS has no trigger module in Make, so nothing inside sendSMS can start a scenario. You begin with a trigger from another app, such as a form or a store, and sendSMS acts afterwards. If that first app offers an instant trigger, the scenario starts as soon as it calls Make. Otherwise Make checks on a schedule, every 15 minutes by default. For a sending flow, that first app is usually where the event you care about happens.
04What if a sendSMS module is missing in Make?
Use Make an API Call. It reaches any endpoint of the sendSMS API with the connection you already created, so an operation that no listed module offers is still within reach. You write the request yourself from the sendSMS API documentation. The Make doc for this app also warns that its content is AI-generated from sendSMS documentation and may contain mistakes, so check important details with sendSMS directly. Test it with Run once first.
05Should you use Make or n8n for sendSMS?
It depends on the tool your team already works in, and on whether n8n offers a node for sendSMS, which is worth checking before you choose. In Make you get 14 ready modules covering texts, contacts, groups, block lists and message statuses, plus Make an API Call for the rest. Look at the other apps in your flow and pick the tool where the whole chain is easiest for you to build and maintain.
Same platform

Other docs you might need on this stack.

Browse all integrations