Resources · Make integration

SMSFactor Make integrationAutomate SMSFactor with Make.

Need a text message to go out the moment something happens in another tool? The SMSFactor Make integration gives you 2 action modules, one to send an SMS and one to call the API directly. This page shows how to link your account and build a first working flow.

Try the SMSFactor integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the SMSFactor Make integration do for you?

The SMSFactor Make integration lets a Make scenario (the automation you build, a chain of modules) send text messages through your SMSFactor account. Something happens in another app, and Make fires off the SMS for you. No code, no copy and paste between tabs.

Appointment reminders that send themselves. A booking tool records a new slot, and Send an SMS texts the client the date and address. Pages like the Acuity Scheduling Make integration cover the booking side of that flow.

Alerts for the team on the road. A new row lands in a shared base, and a technician gets a short text with the job details. The Airtable Make integration explains how to watch that base.

Anything the listed module does not cover. Make an API Call reaches any endpoint of the SMSFactor API with the same connection, so you are never stuck with only one module.

Know the limits before you start. SMSFactor has no trigger module in Make, so a scenario cannot start on an incoming SMS from this app: it starts from another app or from a schedule. Each send also needs SMS credits on your SMSFactor account. Weighing your options? The n8n vs Make comparison sets out the criteria side by side.

Connect

How do you connect SMSFactor to Make?

  1. 01

    Get your API token ready

    Log in to SMSFactor and copy your API token. Make needs an active SMSFactor account, that token and enough SMS credits, so check your balance while you are there.

  2. 02

    Open the connection window

    In your Make scenario, add any SMSFactor module and click Create a connection. The Connection name field is optional: a clear name helps when you manage several accounts.

  3. 03

    Paste the credentials and save

    Enter the credentials copied from SMSFactor, or follow the on-screen instructions, then save. The connection (your SMSFactor account linked to Make) is then reused by both modules.

First scenario

Your first scenario with SMSFactor

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

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module: the form or booking app that produces the phone number.

  2. 02

    Add Send an SMS

    Click the + on the right of that first module, search for SMSFactor and pick Send an SMS. Click Create a connection if your account is not linked yet.

  3. 03

    Map the number and the text

    Fill the module fields by mapping data from the first module: the phone number it received and a message that can include the person's name. Each item passed along is called a bundle.

  4. 04

    Test with Run once

    Click Run once and submit a test entry with your own number. Read the bundles each module received, and check that the SMS reached your phone.

  5. 05

    Schedule and switch on

    Set the schedule on the first module (every 15 minutes by default) and switch the scenario on. Each module run counts as one operation on your Make plan.

Modules

What the SMSFactor modules do

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

SMSFactor1

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

This module opens up the whole SMSFactor API from your scenario, reusing the connection you already created. You pick the endpoint and send the request yourself.

When to use it
the action you have in mind is not covered by Send an SMS, and the SMSFactor API documentation describes an endpoint for it.
Watch out
you write the request by hand, so read the SMSFactor docs for the exact endpoint and parameters before running it.
SMSFactor2

Send an SMS

Action

In Make“Sends a single message to one destination.”

Your recipient gets one text message on their phone, sent from your SMSFactor account the moment the scenario reaches this step. One module run means one message to one number.

When to use it
a booking is confirmed, an order ships or a ticket changes status, and the person should hear about it by text.
Watch out
the docs require sufficient SMS credits, so keep an eye on your SMSFactor balance before a big batch of sends.
Need help

Need help automating SMSFactor with Make?

A person reads every message.

FAQ

SMSFactor and Make: frequently asked questions

01Is the SMSFactor Make integration free?
Yes, on the Make side. SMSFactor is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs and up to 5 minutes per execution. Paid plans lower the interval to 1 minute and remove the cap on active scenarios. The texts themselves are a different matter: every SMS uses credits on your SMSFactor account, which you buy from SMSFactor, not from Make.
02What do you need to connect SMSFactor to Make?
Three things: an active SMSFactor account, an API token copied from that account, and enough SMS credits to cover the messages you plan to send. In Make, add an SMSFactor module, click Create a connection, give it a name if you like, then paste the credentials. The same connection then serves both modules, Send an SMS and Make an API Call, so you only set it up once. Pick a connection name you will recognize later.
03How does an SMSFactor scenario start without a trigger?
It starts from somewhere else. SMSFactor has no trigger module in Make, so the first module of your scenario belongs to another app, such as a form, a CRM or a spreadsheet, and SMSFactor comes after it. You can also start the scenario on a schedule: a new scenario checks every 15 minutes by default, and you change that clock on the first module. The SMS goes out when the scenario runs, not the second the event happens.
04What if the SMSFactor module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the SMSFactor API with the connection you already have, so an action that Send an SMS does not handle can still run inside the same scenario. You write the request yourself, following the SMSFactor API documentation. Note that the Make documentation for this app is AI-generated from the SMSFactor docs, so check important details with SMSFactor directly. The Make troubleshooting pages also help when a call fails.
05Should you use Make or n8n for SMSFactor?
It depends on the tool your team already runs. On Make, SMSFactor gives you Send an SMS for the common case and Make an API Call for the rest, available from the Free plan, with a visual editor and a Run once button to test each step. If you already build workflows in n8n, check whether an SMSFactor node covers what you need there before switching. Compare the criteria that matter to you rather than picking by name.
Same platform

Other docs you might need on this stack.

Browse all integrations