Resources · Make integration

SMSVio Make integrationAutomate SMSVio with Make.

Want a customer to get a text when something happens in another tool? The SMSVio Make integration gives you 3 action modules: send an SMS, read a message's details, delete a message. This guide connects your account and walks you through a first scenario.

Try the SMSVio integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the SMSVio Make integration do for you?

The SMSVio Make integration lets a Make scenario (the automation you build, a chain of steps) send, look up and delete text messages in your SMSVio account. Each step is a module, one brick of the scenario. SMSVio brings 3 of them, all actions: something else has to start the scenario.

A confirmation text after a booking. A form or a calendar app starts the scenario, and Send an SMS texts the customer. Each item that flows from one module to the next is called a bundle: here, one booking produces one bundle and one message.

A check on a message you already sent. Read Message Details pulls the information SMSVio keeps about a message, so a later module can store it in a sheet or a CRM.

A cleanup when a message is no longer needed. Delete a Message removes it from SMSVio. Use it with care: nothing in Make's documentation says a delete can be undone.

Know the limits before you start. SMSVio has no trigger in Make, so it cannot start a scenario by itself, and it has no Make an API Call module for requests outside these three. Make's own documentation for SMSVio is also marked as limited: expect to check field meanings in your SMSVio account. To judge the platform first, read our Make review, and see Make pricing for what each plan allows. If you also weigh n8n, the n8n vs Make comparison lays out the criteria.

Connect

How do you connect SMSVio to Make?

  1. 01

    Add an SMSVio module

    In a scenario, click the +, search for SMSVio and pick any of its modules. Then click Create a connection. A connection is your SMSVio account linked to Make once, and every SMSVio module reuses it.

  2. 02

    Name and authorize it

    Give the connection a name if you like, for example the account or the team it belongs to. Then follow what the window asks: either approve access on SMSVio's page, or paste the key SMSVio gives you.

  3. 03

    Save and check

    Click Save. Make now shows the module's fields. If it returns an error instead, open the connection again and check the account you authorized or the key you pasted.

First scenario

Your first scenario: text a customer when a form comes in

GoalWhen a new form entry arrives in another app, Make sends an SMS to that person through SMSVio.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. It will not be SMSVio, since SMSVio has no trigger.

  2. 02

    Pick the starting app

    Choose the trigger of the app where your forms or bookings live, and connect that account. This module decides when the scenario runs and what data it hands over.

  3. 03

    Add Send an SMS

    Click the + on the right of the first module, search SMSVio and pick Send an SMS. Create the connection, then map the recipient's number and your message from the previous module, using the field names Make shows.

  4. 04

    Test with Run once

    Click Run once and submit a test entry with your own number. Make shows the bundles each module received. An operation is one module running on one bundle, and your plan counts them.

  5. 05

    Schedule and switch on

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

Modules

What each SMSVio module does

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

SMSVio1

Delete a Message

ActionIn the docs only

This one removes a message from your SMSVio account, one message per run. It keeps the account tidy once a message has served its purpose.

When to use it
at the end of a scenario that has already copied what it needed from the message, for example into a spreadsheet.
Watch out
Treat a delete as final: the documentation mentions no way back. Test it with Run once on a message you do not need.
SMSVio2

Read Message Details

ActionIn the docs only

Here you get the information SMSVio stores about one message, returned as a single bundle that the next modules can use. It is a lookup: nothing changes in your account.

When to use it
you want to record what happened to a message in a CRM or a sheet, or feed it into a filter.
Watch out
the documentation does not list what it returns, so run it once and read the bundle before mapping anything.
SMSVio3

Send an SMS

ActionIn the docs only

With this module your customer receives a text from your SMSVio account, triggered by whatever event starts the scenario. It is the module most scenarios with SMSVio are built around.

When to use it
a booking is confirmed, an order ships or a lead fills a form, and the person should hear about it by text.
Watch out
each bundle sends one message, so a module upstream that returns many items sends many texts. Try it on your own number before real customers get it.
Need help

Need help automating SMSVio with Make?

A person reads every message.

FAQ

SMSVio and Make: common questions

01Is the SMSVio Make integration free?
Yes, on the Make side. SMSVio is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes per run, files up to 5 MB and 512 MB of data transfer. Paid plans bring the interval down to 1 minute, remove the cap on active scenarios and allow runs of up to 40 minutes. Make counts usage in operations, one per module per bundle. Your SMSVio account is a separate matter, and this page does not cover SMSVio's own pricing.
02What do you need to connect SMSVio to Make?
An SMSVio account and a Make account. The documentation lists no other prerequisite. In the scenario, add an SMSVio module, click Create a connection, name it if you want, then approve access on SMSVio's page or paste the key SMSVio provides, depending on what the window asks. Click Save. The connection is then reused by all three SMSVio modules, so you only set it up once per account. Since Make's SMSVio documentation is marked as limited, keep your SMSVio account open in another tab while you fill fields.
03Can SMSVio start a Make scenario on its own?
No. SMSVio has no trigger module in Make, only three actions, so it cannot tell Make that something happened. The scenario has to start elsewhere. The usual option is the trigger of another app, such as a form tool, a store or a calendar, followed by Send an SMS. The other option is a scenario that simply runs on its schedule, every 15 minutes by default, and then calls SMSVio. Either way, the SMSVio modules only run when an earlier step hands them a bundle to work on.
04What if an SMSVio module you need is missing in Make?
It depends on what you need. SMSVio offers three modules in Make: Send an SMS, Read Message Details and Delete a Message. There is no Make an API Call module for this app, so you cannot reach other SMSVio features from Make with a custom request. If your case goes further, look at another SMS or messaging app in Make that covers it, or ask the Hack'celeration team to look at your scenario. Make's own SMSVio documentation is also limited, which is worth knowing before you plan a large build.
05Should you use Make or n8n with SMSVio?
It depends on the tool your team already works in and on what you want to automate. This page covers Make, where SMSVio brings three actions and no trigger, so another app or a schedule starts each scenario. Many apps also have an n8n node, and whether SMSVio has one is worth checking in n8n itself before you decide. Compare what each side offers for SMSVio specifically, then pick the one where your other apps already live. Our n8n vs Make comparison lists the general criteria side by side.
Same platform

Other docs you might need on this stack.

Browse all integrations