Resources · Make integration

Mobivate SMS Make integrationAutomate Mobivate SMS with Make.

Need a text message to leave on its own when something happens in another tool? The Mobivate SMS Make integration gives you 2 action modules, both built to send. This page shows how to link your account, then walks you through a first scenario that texts a contact.

Try the Mobivate SMS integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Mobivate SMS Make integration do?

The Mobivate SMS Make integration lets a Make scenario (the automation you build, a chain of bricks called modules) send text messages through your Mobivate SMS account. The app has no trigger, so the start signal always comes from another app or from a schedule set in Make.

An order confirmation that goes out by itself. A shop platform starts the scenario when an order is placed, and Send SMS texts the buyer a short confirmation with the order details mapped in.

A heads-up for the field team. A form or a support tool flags an urgent request, and Send SMS alerts the technician on duty, so nobody has to watch an inbox.

A call Mobivate exposes but Make does not list. When you need something beyond sending, Make an API Call reaches the Mobivate API with the same connection. It takes more setup, since you write the request yourself.

Be aware of one limit: Make itself says its documentation for Mobivate SMS is incomplete, because little public information exists about the app. Test every scenario with a real number before you rely on it. For help reading errors, see Make troubleshooting. The same app may also exist as an n8n node; the n8n vs Make comparison helps you pick, and the Make training covers scenario basics.

Connect

How do you connect Mobivate SMS to Make?

  1. 01

    Add a Mobivate SMS module

    In your scenario, click the +, search for Mobivate SMS and pick Send SMS. Then click Create a connection. A connection is your Mobivate account linked to Make once and reused by every module of the app.

  2. 02

    Name the connection

    This step is optional, but a clear name such as the sender account or the team using it saves confusion later, when several people or several Mobivate accounts share the same Make organization.

  3. 03

    Authorize and save

    Follow what the window asks: either approve Make on the Mobivate page, or paste the key Mobivate gives you. Then click Save. The connection now appears in the module and in every Mobivate SMS module you add afterward.

First scenario

Build your first scenario with Mobivate SMS

GoalWhen a new entry arrives in another app, Make texts that person through Mobivate SMS.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the +. The first module is the app that starts everything: your form tool, your shop or your CRM.

  2. 02

    Set the starting module

    Pick the trigger of that other app and connect it. Mobivate SMS has no trigger of its own, so this module decides when a text goes out, one bundle (one item, like one form entry) at a time.

  3. 03

    Add Send SMS

    Click the + on the right of the first module, search for Mobivate SMS and pick Send SMS. Choose your connection, then map the phone number and the message text from the previous module.

  4. 04

    Test with Run once

    Put your own number in the data, click Run once and read the bundle each module received. Check that the text reached your phone before you point the scenario at real contacts.

  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 on one bundle counts as one operation, the unit Make counts on your plan.

Modules

What the Mobivate SMS modules do

Mobivate SMS gives you 2 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Mobivate SMS1

Make an API Call

ActionIn the docs only

This module opens the whole Mobivate API to your scenario, reusing the connection you already made, so you are not stuck with what the listed modules cover.

When to use it
pick it only when Send SMS cannot do the job, for example to reach a Mobivate endpoint that no module in Make lists.
Watch out
you write the request yourself and Make's documentation for this app is thin, so check with Mobivate what the request expects and test it with Run once.
Mobivate SMS2

Send SMS

ActionIn the docs only

This is the module that gets a text message out to a phone number the moment your scenario reaches it, with the content built from data earlier modules passed along.

When to use it
right after the module that brings the recipient, such as a new order, a booked slot or a flagged ticket, so each bundle produces one message.
Watch out
a search upstream that returns several bundles sends one text per bundle, so filter before this module to avoid duplicates.
Need help

Need help automating Mobivate SMS with Make?

A person reads every message.

FAQ

Mobivate SMS and Make: common questions

01Is the Mobivate SMS Make integration free?
Yes, on the Make side. Mobivate SMS is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum interval of 15 minutes between scheduled runs, 5 minutes of execution 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 40 minutes of execution. Sending texts through Mobivate itself depends on your Mobivate account, which Make does not cover.
02What do you need to connect Mobivate SMS to Make?
A Mobivate SMS account and a Make account. Make's documentation lists no specific prerequisite for this app and gives no dedicated connection steps, so the generic flow applies: add a module, click Create a connection, optionally name it, then approve Make on the Mobivate page or paste the key Mobivate provides, and save. Keep that key at hand before you start, because the documentation for this app is limited. Once saved, every Mobivate SMS module in your scenarios reuses it.
03Can a Mobivate SMS scenario start in real time?
Not from Mobivate SMS, because the app has no trigger module in Make. The scenario has to start elsewhere. You can open it with an instant trigger from another app, which calls Make through a webhook as soon as something happens there, or with a scheduled trigger that Make checks on the scenario's schedule, every 15 minutes by default. Send SMS then runs each time that first module hands it a bundle.
04What if the Mobivate SMS module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the Mobivate API with the same connection, so an operation that Send SMS does not cover can still run in the scenario. You write the request yourself, which asks for more care than a ready-made module. Make also states that its documentation for Mobivate SMS is incomplete, so test each call with Run once and read the returned bundle before you switch the scenario on.
05Should you use Make or n8n for Mobivate SMS?
It depends on the tool your team already works in. In Make, Mobivate SMS gives you 2 action modules, Send SMS and Make an API Call, and no trigger, so another app always starts the flow. The same app may also have an n8n node. Compare what each tool offers for your case, the modules you need and how your other apps connect, rather than following a ranking; neither choice changes what Mobivate itself can send.
Same platform

Other docs you might need on this stack.

Browse all integrations