Resources · Make integration

SMSC Make integrationAutomate SMSC with Make.

Can Make send your SMSC text messages for you? Yes. The SMSC Make integration gives you 18 modules: 13 actions and 5 searches. This guide is for anyone who already uses SMSC and wants to connect the account, build a first scenario and pick the right module.

Try the SMSC integration on MakeSee the 18 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the SMSC Make integration do for you?

The SMSC Make integration lets Make act on your SMSC account for you: send a text, store a contact, manage the sender names your messages go out under, or read back what came in. You build this as a scenario, which is the automation you assemble in Make, one module (one brick) after another, without writing code.

Confirmations that leave on their own. A new booking or order lands in another app, and Send an SMS texts the customer right after. Add Check an SMS Status further down the line if you want the scenario to look at what SMSC says about that message.

A contact book that stays in step with your CRM. Support teams often keep phone numbers in two places. Search Contacts checks whether the person already exists in SMSC, then Create a Contact or Update a Contact writes the right version.

Replies and credit under watch. Search Incoming Messages pulls the texts people sent back, and Get an Account Balance reads your credit so a later module can alert the person who tops it up.

What Make does not do here: SMSC has no trigger in Make, so nothing inside SMSC can start a scenario by itself. You start it from another app or from the schedule of Make. The Make documentation for SMSC is also marked as AI-generated, so check anything important with SMSC. If you are weighing tools, the n8n vs Make comparison lays out both, and the Make training takes you further than this page. When a run fails, start with Make troubleshooting.

Connect

How do you connect your SMSC account to Make?

  1. 01

    Add an SMSC module

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

  2. 02

    Name the connection

    The Connection name field is optional. A clear name still helps when you run more than one SMSC account, for example one per brand or one for testing, because the name is what you pick from when you add the next SMSC module.

  3. 03

    Enter your SMSC credentials

    Paste the login and password or the API key from your SMSC account, or follow the instructions Make shows on screen. You need an active SMSC account first; the login and password sit in the Settings or Profile section of your SMSC dashboard.

First scenario

Your first scenario: welcome a new customer by text

GoalWhen a new customer comes in through another app, Make adds that person to SMSC and sends a welcome text.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. The first module comes from the app where your customers arrive, such as a form tool or your shop.

  2. 02

    Add Create a Contact

    Click the + to the right of that first module, search for SMSC and pick Create a Contact. Choose your connection, then map the name and number received from the first module.

  3. 03

    Add Send an SMS

    Add one more module with the +: Send an SMS. Map the same number, write the welcome text and slip in the first name from the previous bundle (one item passed along).

  4. 04

    Test with Run once

    Click Run once and create a test customer with your own phone number. Open each module to read the bundles it received, and check that the text reached you.

  5. 05

    Schedule and switch on

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

Modules

What each SMSC module does

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

SMSC1

Check a Sender Verification Code

ActionIn the docs only

This module confirms a sender name on your SMSC account by submitting the verification code linked to it. It closes the loop that Generate a Sender Verification Code opens.

When to use it
once the code has reached the person in charge, for instance through a form they filled in, and you want the scenario to finish the check without anyone logging in to SMSC.
SMSC2

Check an SMS Status

ActionIn the docs only

Here you get back what SMSC records about a message you already sent, so the scenario can react to it instead of assuming all went well.

When to use it
after Send an SMS, when a failed appointment reminder should lead to a phone call or an email.
Watch out
the module has to know which text you mean, so place it after the module that sent or found that message.
SMSC3

Create a Contact

ActionIn the docs only

Adds a new person to the contact list of your SMSC account, so later campaigns can reach them without retyping a number.

When to use it
a lead signs up on your site or a customer places a first order.
Watch out
run Search Contacts first if the same person can come back, or you risk storing them twice.
SMSC4

Create a Sender

ActionIn the docs only

You end up with a new sender, the name your recipients see as the origin of a text, created in SMSC straight from the scenario.

When to use it
when an agency opens a new client account and each brand needs its own sender.
Watch out
the two verification code modules in this app suggest a new sender must be confirmed, so plan them into the same scenario.
SMSC5

Delete a Contact

ActionIn the docs only

Removes a person from your SMSC contact list, which keeps your campaigns away from people who asked to leave.

When to use it
a customer unsubscribes in your CRM and the number must disappear from SMSC too.
Watch out
treat the deletion as final and test it with Run once on a dummy contact before switching the scenario on.
SMSC6

Delete a Sender

ActionIn the docs only

With this module a sender name you no longer use leaves your SMSC account, so nobody picks it by mistake in a later campaign.

When to use it
a brand is retired or a client contract ends and their sender should go.
Watch out
if another scenario still sends under that name, expect it to fail, so check your scenarios first.
SMSC7

Delete an SMS

ActionIn the docs only

Clears one message from SMSC, which is handy when a text should not stay in the account records.

When to use it
a message was queued by mistake or holds data your team prefers not to keep.
Watch out
you need the reference of that exact message, usually taken from Search Outgoing Messages or Send an SMS earlier in the scenario.
SMSC8

Generate a Sender Verification Code

ActionIn the docs only

Asks SMSC for a verification code on a sender name, the first half of confirming that the name really belongs to you.

When to use it
right after Create a Sender, so the whole setup of a new brand runs in one scenario.
Watch out
the code only matters once Check a Sender Verification Code submits it, so plan both modules together.
SMSC9

Get an Account Balance

ActionIn the docs only

Reads how much credit is left on your SMSC account, so a scenario can warn you before your messages stop going out.

When to use it
ahead of a large send, or as the first module of a small watch scenario that emails the person who pays the bills.
Watch out
the module only reads the figure; deciding when it is too low is up to the modules you add after it.
SMSC10

List Senders

SearchIn the docs only

Gives you every sender name set up on your SMSC account, one bundle per sender, ready to be checked or copied elsewhere.

When to use it
to audit which brands can send texts, or to feed a sheet that your marketing team keeps up to date.
Watch out
each sender becomes its own bundle, so the next module runs once per sender.
SMSC11

List Statistics

SearchIn the docs only

Pulls the sending statistics SMSC keeps for your account, so the numbers can land in a report without a manual export.

When to use it
to fill a dashboard or a spreadsheet that the team reviews after each campaign.
Watch out
like any search, it can return zero, one or many bundles; add an aggregator if you want a single row.
SMSC12

Make an API Call

ActionIn the docs only

Lets you call any endpoint of the SMSC API from your scenario, with the connection you already set up, when no other SMSC module covers the job.

When to use it
a feature you see in SMSC has no dedicated module in Make.
Watch out
you describe the request yourself, so keep the SMSC API documentation open next to the editor.
SMSC13

Search Contacts

SearchIn the docs only

Finds people already stored in your SMSC contact list, so the scenario can decide between creating, updating or skipping.

When to use it
before Create a Contact, to keep duplicates out when the same customer orders again.
Watch out
like any search, it can return zero, one or several bundles, and zero simply means the person is new.
SMSC14

Search Incoming Messages

SearchIn the docs only

Collects the texts people sent back to you through SMSC, so replies can reach your helpdesk or your CRM instead of staying in the SMSC dashboard.

When to use it
you ask customers to answer YES to confirm, and someone needs to see those answers.
Watch out
since SMSC has no trigger, this search runs on the scenario schedule, never the moment a reply arrives.
SMSC15

Search Outgoing Messages

SearchIn the docs only

Brings back the messages your account has sent, which gives you a trail you can store or check against your own records.

When to use it
a customer says they never got the code, and support wants to see what actually left.
Watch out
several messages come out as several bundles, and every following module counts an operation for each.
SMSC16

Send an SMS

ActionIn the docs only

This is the module that puts a text on someone's phone: your scenario writes the message and SMSC delivers it.

When to use it
order confirmations, delivery notices, appointment reminders, any moment where a short text beats an email.
Watch out
test with Run once on your own number first, because every real run spends SMSC credit.
SMSC17

Update a Contact

ActionIn the docs only

Changes the details of a contact that already exists in SMSC, so the next text goes to the right number under the right name.

When to use it
a customer edits their phone number in your shop or your CRM.
Watch out
the module needs to know which contact to change; get it from Search Contacts in the step before.
SMSC18

Update a Sender

ActionIn the docs only

Edits a sender name that is already on your account, which saves you from deleting it and building a new one.

When to use it
a brand changes its spelling and the sender should follow.
Watch out
run List Senders first to pick the right one so the change lands on the sender you meant.
Need help

Need help automating SMSC with Make?

A person reads every message.

FAQ

SMSC and Make: common questions

01Is the SMSC Make integration free?
Yes, on the Make side. SMSC is a standard app, so it works on the Free plan. That plan allows 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes per run, files up to 5 MB and 512 MB of data transfer. Paid plans lower the interval to 1 minute and remove the cap on active scenarios. Make counts usage in operations, one per module run. Sending texts still requires an active SMSC account, and SMSC bills that separately under its own pricing.
02What do you need to connect SMSC to Make?
An active SMSC account and its credentials. Make accepts the login and password, or an API key, from SMSC. You find the login and password in the Settings or Profile section of the SMSC dashboard once you are logged in. In Make, add any SMSC module, click Create a connection, give it a name if you like, then paste the credentials. The connection is created once and every SMSC module in your scenarios reuses it, so you do not repeat the setup each time.
03Can SMSC start a Make scenario in real time?
No. SMSC has no trigger module in Make, neither scheduled nor instant. A scenario that uses SMSC starts from something else: the trigger of another app, such as a new order or a form reply, or the schedule of Make itself, every 15 minutes by default. For replies, put Search Incoming Messages right after a scheduled start. The scenario then collects new texts at each run, which means a short delay rather than an immediate reaction.
04What if an SMSC module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the SMSC API with the connection you already have, so a feature without its own module is still within reach. You write the request yourself, which asks for a look at the SMSC API documentation. Keep in mind that the Make documentation for SMSC says it was generated with AI and may contain mistakes, so check any detail that matters with SMSC before you build a scenario on it.
05Should you use Make or n8n for SMSC?
It depends on the tool your team already runs. Make gives SMSC 18 modules, 13 actions and 5 searches, plus Make an API Call for the rest, and the whole setup happens in a visual editor. Many apps also have a node in n8n, so check whether SMSC is covered there before choosing. The deciding factor is rarely SMSC alone: pick the platform where your other apps and your existing scenarios already live, and compare the two on that basis.
Same platform

Other docs you might need on this stack.

Browse all integrations