Resources · Make integration

smsAdvert.ro Make integrationAutomate smsAdvert.ro with Make.

Can an event in another tool send a text through smsAdvert.ro on its own? The smsAdvert.ro Make integration gives you 5 action modules, Send SMS among them. This page is for people new to Make: link your account, build a first scenario, then pick the right module.

Try the smsAdvert.ro integration on MakeSee the 5 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the smsAdvert.ro Make integration do?

The smsAdvert.ro Make integration lets a Make scenario, the automation you build as a chain of modules, send text messages and read account details from smsAdvert.ro. Each module is one brick of that chain. Here all 5 are actions, so the scenario starts from another app or from a schedule.

Text a customer when something happens elsewhere. A new booking, a paid order or a form entry in another app starts the scenario, and Send SMS passes the message to smsAdvert.ro. No copy and paste between tools.

Keep an eye on the account before a big send. Get Account Units, Get Device Status and Get SMS API Queue read information from your smsAdvert.ro account, going by their names. A scenario can read them first and only send when the answer suits you.

Reach what the list does not cover. Make an API Call calls any endpoint of the smsAdvert.ro API with the same connection.

Be aware of one limit: Make says its documentation for this app is incomplete, because little public information about smsAdvert.ro exists. The fields each module asks for only show up once you open it in the editor. If a run fails, the Make troubleshooting guide helps, and Make pricing explains how operations are counted. Wondering about the other big tool? The n8n vs Make comparison lays out the criteria.

Connect

How do you connect smsAdvert.ro to Make?

  1. 01

    Open a smsAdvert.ro module

    In your scenario, click the +, type smsAdvert.ro and pick any of its modules, Send SMS for example. The module panel opens with a Create a connection button. A connection is your smsAdvert.ro account linked to Make once.

  2. 02

    Name the connection

    Giving the connection a name is optional, but it pays off when you run more than one smsAdvert.ro account. Something like the account or client name keeps you from sending from the wrong one later.

  3. 03

    Authorize and save

    Depending on what smsAdvert.ro asks, either approve Make on the smsAdvert.ro page or paste the key the app gives you, then click Save. Every other smsAdvert.ro module in your scenarios reuses this connection.

First scenario

Your first scenario with smsAdvert.ro

GoalWhen a new entry lands in another app, Make sends a text through smsAdvert.ro.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. Since smsAdvert.ro has no trigger, the first module comes from the app where the event happens, a form tool or your CRM.

  2. 02

    Set up the starting module

    Pick that app, create its connection, fill its fields. Make lists what it can read once the connection exists, so you choose from a list instead of typing names.

  3. 03

    Add Send SMS

    Click the + on the right of the first module, search smsAdvert.ro and choose Send SMS. Map the phone number and message text from the data the first module passes along.

  4. 04

    Test with Run once

    Click Run once, then create one test entry with your own number. Each module shows the bundles it received, a bundle being one item passed along, so you can check what went out.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module. A new scenario checks every 15 minutes by default, and 15 minutes is also the shortest interval on the Free plan. Then switch the scenario on.

Modules

The 5 smsAdvert.ro modules in Make

smsAdvert.ro gives you 5 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

smsAdvert.ro1

Get Account Units

ActionIn the docs only

Going by its name, this action reads the units on your smsAdvert.ro account, and you would get the answer as data your next modules can use. Make gives no official description, so open it once to see exactly what it returns.

When to use it
place it before Send SMS when you want the scenario to check the account before a larger batch of texts goes out.
Watch out
every run of this module counts as one operation on your Make plan, even when nothing is sent.
smsAdvert.ro2

Get Device Status

ActionIn the docs only

You learn the state of the device smsAdvert.ro links to your account, going by the module name, without logging in to smsAdvert.ro. The result lands in the scenario as a bundle you can filter on or pass to a notification.

When to use it
ahead of an important send, when a failed delivery would cost you more than the extra check.
Watch out
Make publishes no detail on what this status contains, so run it once and read the bundle before building logic on it.
smsAdvert.ro3

Get SMS API Queue

ActionIn the docs only

Going by its name, it reads the smsAdvert.ro SMS API queue. That tells you whether messages you sent earlier are still waiting their turn, which matters most on a busy day.

When to use it
after a batch of Send SMS, when you would rather see the queue than assume every text already left.
Watch out
the output may hold several items, and whether it does is not documented, so check the bundles in a Run once test first.
smsAdvert.ro4

Make an API Call

ActionIn the docs only

Your way into any endpoint of the smsAdvert.ro API, using the connection you already set up. Whatever the four other modules leave out, this call can still reach, as long as the smsAdvert.ro API offers it.

When to use it
when you need an action that none of the named modules covers.
Watch out
you write the request yourself, so keep the smsAdvert.ro API documentation open next to Make; Make's own page does not describe the endpoints.
smsAdvert.ro5

Send SMS

ActionIn the docs only

The module most people come for: it sends a text message through your smsAdvert.ro account, with the number and the wording taken from earlier modules or typed in. One run, one message on its way.

When to use it
right after the module that holds the event, such as a new order or a confirmed appointment in another app.
Watch out
test with your own number during Run once, because the text really goes out.
Need help

Need help automating smsAdvert.ro with Make?

A person reads every message.

FAQ

Questions about smsAdvert.ro and Make

01Is the smsAdvert.ro Make integration free?
Yes, on the Make side. smsAdvert.ro is a standard app, so it works on the Free plan. That plan allows 2 active scenarios, a 15 minute minimum between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) lower the interval to 1 minute and allow 40 minutes of execution. What smsAdvert.ro itself charges for sending texts is a separate matter, not covered here.
02What do you need to connect smsAdvert.ro to Make?
A smsAdvert.ro account and a Make account. Make does not list any extra prerequisite for this app. You add a smsAdvert.ro module, click Create a connection, optionally name it, then either authorize Make on the smsAdvert.ro page or paste the key the app provides, and click Save. Make's documentation for smsAdvert.ro is marked as limited, so if the window asks for a value you cannot find, look in your smsAdvert.ro account settings.
03Does the smsAdvert.ro Make integration react in real time?
No, not by itself, since smsAdvert.ro has no trigger module in Make. The scenario has to start somewhere else. Either another app's trigger starts it, for example a new form entry, and the smsAdvert.ro modules follow. Or you put the scenario on a schedule from the clock on the first module, every 15 minutes by default. If the starting app offers an instant trigger through a webhook, the text follows the event right away.
04What if a smsAdvert.ro module is missing in Make?
Use Make an API Call. This module calls any endpoint of the smsAdvert.ro API through the same connection, so an action missing from the other four can still be reached. You need the smsAdvert.ro API documentation to build the request, because Make states that its own documentation for this app is limited by the lack of public information. If the API cannot do it either, another app in Make may cover the need.
05Should you use Make or n8n with smsAdvert.ro?
It depends on the tool your team already works in. On Make, smsAdvert.ro comes with 5 action modules and no trigger, including Make an API Call for anything they do not cover, and it runs on the Free plan. The same app often has a node in n8n as well. Compare the modules each tool offers for your exact use, then look at where your other automations already live and which of the two tools your team already knows.
Same platform

Other docs you might need on this stack.

Browse all integrations