Resources · Make integration

sms77.io Make integrationAutomate sms77.io with Make.

Can Make send a text when something happens in your other tools? The sms77.io Make integration gives you 16 modules: texts, voice calls, contacts and number checks. This guide links your account and walks you through a first scenario, step by step.

Try the sms77.io integration on MakeSee the 16 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the sms77.io Make integration let you automate?

The sms77.io Make integration lets a Make scenario, meaning the automation you build as a chain of bricks called modules, send texts, place voice calls and manage contacts in your sms77.io account. There is no code to write: you pick modules, fill in fields and test the result.

Customers hear from you without anyone typing a message. A form, a CRM or a shop starts the scenario, and Send SMS texts the person with the details you mapped from the previous step. For a reminder that has to be heard rather than read, Make a Voice Call does the same job by phone.

Your contact list stays in step with the rest of your tools. Create a Contact, Update a Contact and Delete a Contact mirror what changes elsewhere, and List Contacts tells you who is already there before you add someone twice.

You can check a number before paying to reach it. The lookup modules (Lookup Format, Lookup HLR, Lookup MNP, Lookup CNAM) and Validate for Voice let a scenario inspect a number first, while Get Balance keeps an eye on your credit.

What the app does not offer: a trigger. No sms77.io module starts a scenario by itself, so the first step comes from another app or from the Make schedule. For anything the listed modules miss, Make an API Call reaches the rest of the sms77.io API. If you are still choosing a platform, read the n8n vs Make comparison, then see what a plan costs on Make pricing. The Make training covers the editor in depth.

Connect

How do you connect sms77.io to Make?

  1. 01

    Create an API key in sms77.io

    You need an active sms77.io account first. Log in, open the Developer area, click Create API key and copy the key shown on screen. That key is what lets Make act on your account.

  2. 02

    Add a module and open the connection window

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

  3. 03

    Paste the key and save

    Give the connection a clear label in Connection name if you like; the field is optional. Paste the API key you copied, or follow the on-screen instructions, and save. The module is now ready to fill.

First scenario

Build your first scenario with sms77.io

GoalWhen a new order lands in your shop, Make texts the buyer through sms77.io.

  1. 01

    Create the scenario

    Open the Scenarios page in Make, create a new scenario and click the +. Since sms77.io has no trigger, the first module comes from the app that holds your orders.

  2. 02

    Pick the starting module

    Search for your shop or form app, choose the module that watches new orders and link its account. Each order it finds becomes a bundle, meaning one item passed on to the next module.

  3. 03

    Add Send SMS

    Click the + on the right of the first module, search for sms77.io and pick Send SMS. Select your connection, then map the buyer's phone number and a short message from the order data.

  4. 04

    Test with Run once

    Click Run once to execute the scenario a single time. Open the bubble above each module to read the bundles it received, and check that the text reached the phone you used for the test.

  5. 05

    Schedule and switch on

    Set the schedule on the first module: a new scenario checks every 15 minutes by default. Then switch the scenario on. Each module run is an operation, which is what Make counts on your plan.

Modules

What can sms77.io do in Make?

sms77.io gives you 16 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

sms77.io1

Create a Contact

ActionIn the docs only

Adds a person to your sms77.io contacts, so the people you text later are already on file in the app rather than scattered across other tools.

When to use it
right after someone fills in a sign-up form, so each new lead lands in sms77.io with a name and phone number.
Watch out
put List Contacts in front of it if the same person can sign up twice, otherwise duplicates pile up.
sms77.io2

Delete a Contact

ActionIn the docs only

Removes a contact from your sms77.io account, which keeps your list clean when someone no longer wants to hear from you or leaves your customer base.

When to use it
when a customer closes their account in your CRM and should drop off your texting list too.
Watch out
the contact leaves your sms77.io list, so test with a dummy contact before switching the scenario on.
sms77.io3

Get Balance

ActionIn the docs only

Reads the credit left on your sms77.io account and hands it to the next module, so your scenario knows whether it can still afford to send messages.

When to use it
ahead of a large batch of texts, paired with a filter that stops the run or alerts your team in chat when the balance looks low.
sms77.io4

Get Pricing

ActionIn the docs only

Fetches the rates sms77.io applies to your messages, which gives a scenario the cost information it needs before it sends anything to a new region.

When to use it
when your campaigns reach several countries and you want the rates stored in a sheet that finance can read without logging into sms77.io.
sms77.io5

Get SMS Status

ActionIn the docs only

Looks up what happened to a text you already sent, so you can tell a message that reached the phone apart from one that did not.

When to use it
after Send SMS, when your support team wants a record of each message outcome in the customer file.
Watch out
map the message details from the Send SMS bundle, and read the output once with Run once to find it.
sms77.io6

List Contacts

SearchIn the docs only

Returns the contacts stored in sms77.io, one bundle per person, which lets you reuse that list elsewhere or check whether someone is already there.

When to use it
before creating a contact, to avoid a duplicate, or to copy your list into a spreadsheet.
Watch out
as a search module it can return zero, one or many bundles, and every module after it runs once per bundle.
sms77.io7

Lookup CNAM

ActionIn the docs only

Runs a CNAM lookup on a phone number through sms77.io. CNAM is the caller name tied to a number, so this module helps you see who is behind a number before you act on it.

When to use it
when inbound leads arrive with a number but no name and your sales team wants context first.
Watch out
try it on a few numbers you already know with Run once before a filter depends on its answer.
sms77.io8

Lookup Format

ActionIn the docs only

Checks the format of a phone number through sms77.io, which is a simple way to catch a typo before a text or a call fails on it.

When to use it
as the first sms77.io step after a web form, where people type numbers in every possible way.
Watch out
run Run once and read the output bundle to learn which fields you can map next.
sms77.io9

Lookup HLR

ActionIn the docs only

Performs an HLR lookup, the query to the network register that holds a mobile subscriber, so you learn more about a mobile number than its format alone reveals.

When to use it
when you clean an imported list of mobile numbers and want to set aside the doubtful ones before a campaign.
Watch out
each lookup counts as one operation in Make, so avoid running it on the same number twice.
sms77.io10

Lookup MNP

ActionIn the docs only

Runs an MNP lookup, MNP being mobile number portability, which tells you about a number that may have moved from one carrier to another.

When to use it
when routing or reporting depends on the carrier and you do not want to guess it from the prefix.
Watch out
map the result into a field of your own tool, otherwise the answer is lost after the run.
sms77.io11

Make a Voice Call

ActionIn the docs only

Places a phone call through sms77.io, so a message is heard instead of read. It suits cases where a text is easy to miss.

When to use it
for an urgent alert, such as a server down or an appointment about to start, sent to someone who may ignore their messages.
Watch out
pass the number through Validate for Voice first when you are unsure it can take a call.
sms77.io12

Make an API Call

ActionIn the docs only

Calls any endpoint of the sms77.io API with the connection you already set up, which covers every feature the other modules leave out.

When to use it
when the sms77.io documentation describes a feature that none of the fifteen other modules offers.
Watch out
you write the request yourself, so keep the sms77.io API documentation open while you fill in the module.
sms77.io13

Send SMS

ActionIn the docs only

Sends a text message from your sms77.io account to the number you map, with the wording built from data earlier in the scenario. This is the module most scenarios with this app are built around.

When to use it
for an order confirmation, a delivery notice or a code, right after the event happens in another app.
Watch out
test on your own phone with Run once before real customers receive anything.
sms77.io14

Update a Contact

ActionIn the docs only

Changes the details of an existing sms77.io contact, so a new phone number or name recorded in your CRM reaches your texting list as well.

When to use it
when a customer edits their profile and the next reminder has to go to the right number.
Watch out
the module works on a contact that already exists, so find it with List Contacts first if you only hold the phone number.
sms77.io15

Validate for Voice

ActionIn the docs only

Checks a number with sms77.io ahead of a voice call, so your scenario does not try to phone a line that is not ready for it.

When to use it
as the step right before Make a Voice Call, when numbers come from a form you do not control.
Watch out
read its output with Run once to see what it returns before building a filter on it.
sms77.io16

[DEPRECATED] Get Analytics

ActionIn the docs only

Pulls statistics from your sms77.io account. Make labels this module as deprecated, a sign it is on its way out.

When to use it
only if an existing scenario already relies on it and you need to keep it running while you plan a replacement.
Watch out
for a new scenario, check in the sms77.io API documentation whether Make an API Call can fetch what you need.
Need help

Need help automating sms77.io with Make?

A person reads every message.

FAQ

Common questions about sms77.io and Make

01Is the sms77.io Make integration free?
Yes, on the Make side. sms77.io is a standard app, so it works on the Free plan, which allows 2 active scenarios, runs no more often than every 15 minutes, and stops a run after 5 minutes. Paid plans (Core, Pro, Teams, Enterprise) drop the interval to 1 minute and count usage in credits each month. The sms77.io account itself follows its own pricing page, which this guide does not cover. Each text or call you send still needs an active sms77.io account behind the API key.
02What do you need to connect sms77.io to Make?
You need an active sms77.io account and an API key from it. Log in to sms77.io, open the Developer area, click Create API key and copy the key displayed. In Make, add any sms77.io module, click Create a connection, optionally name it, and paste the key. That single connection then serves all 16 modules of the app, so you only go through this once per sms77.io account. If you manage several sms77.io accounts, create one connection for each.
03Can an sms77.io scenario start on its own in real time?
No, not from sms77.io. The app has no trigger module, so nothing in sms77.io can start a scenario by itself. You have two ways around it. Start the scenario with a module from another app, such as a new form entry or a new order, and let sms77.io act afterward. Or put an sms77.io module first, such as Get Balance, and let the Make schedule run it: every 15 minutes by default on a new scenario, down to 1 minute on paid plans.
04What if an sms77.io module you need is missing in Make?
Use Make an API Call. It calls any endpoint of the sms77.io API with the connection you already have, so a feature without its own module is still within reach. If a scenario still relies on the deprecated Get Analytics module, look there for a way to replace it. You will need the sms77.io API documentation to build the request. Also note that the Make documentation for this app is marked as AI-generated and may contain mistakes, so check important details with sms77.io directly before relying on them.
05Should you use Make or n8n with sms77.io?
It depends on the tool your team already works in. In Make, sms77.io offers 16 modules, including Make an API Call for everything else, and a scenario is built visually with no code. n8n often has a node for the same app, so check its catalog if your other automations already run there. Neither choice is better by default for this app. Pick the platform where your existing scenarios live, so every workflow that sends texts or places calls stays in one place.
Same platform

Other docs you might need on this stack.

Browse all integrations