Resources · Make integration

Textbelt Make integrationAutomate Textbelt with Make.

Need a text message to go out the moment something happens in another tool? The Textbelt Make integration gives you 3 action modules: send an SMS, look up whether it was delivered, and check your remaining quota. This page walks you through the connection and a first working scenario.

Try the Textbelt integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Textbelt Make integration do for you?

The Textbelt Make integration links your Textbelt account to Make so that a scenario, the automation you build in Make, can send SMS for you. Each scenario is a chain of modules, one brick per step, and Textbelt supplies three of them, all actions: nothing to code, you fill in the module and Make does the sending.

An SMS alert when a lead comes in. A sales team wants a text on the phone as soon as a web form is submitted. The form tool starts the scenario, and Send a Text Message turns the entry into a short SMS. If you collect leads with a form builder, the 123FormBuilder Make integration covers that first half.

Proof that the text actually arrived. Sending is one thing, reaching the phone is another. Place Look Up Text Delivery Status after the send module and your scenario can record the result, or warn someone when a message did not get through.

No surprise when credit runs low. Check Your Quota tells you how much sending capacity is left on your Textbelt account, so a scenario can pause or alert you before messages start failing.

Keep the limits in mind. Textbelt has no trigger in Make, so it never starts a scenario on its own: another app or the scenario schedule does. There is also no Make an API Call module for this app, so you work with these three modules only. The same app often has an n8n node too; the n8n vs Make comparison lays out how the two tools differ, and the Make training helps if you are new to the editor.

Connect

How do you connect Textbelt to Make?

  1. 01

    Generate your Textbelt API key

    Log in to Textbelt, open the API key generation page and click Generate API Key. Copy the key that appears on screen. You need an active Textbelt account with an API key before Make can send anything for you.

  2. 02

    Add a Textbelt module and create the connection

    In your Make scenario, add any Textbelt module and click Create a connection. A connection is your Textbelt account linked to Make once, then reused by every Textbelt module. The Connection name field is optional but helps later.

  3. 03

    Paste the key and save

    Paste the API key you copied from Textbelt, or follow the instructions Make shows on screen, and confirm. The connection now appears in the module, and every other Textbelt module in your scenarios can pick it from the list.

First scenario

Your first scenario with Textbelt and Make

GoalWhen a new entry lands in another app, Make sends a Textbelt SMS and then checks whether it was delivered.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. Since Textbelt has no trigger, start with the app that holds your event, such as your form tool.

  2. 02

    Add Send a Text Message

    Click the + on the right of the first module, search for Textbelt and pick Send a Text Message. Select your connection, then map the phone number and message text from the data the first module received.

  3. 03

    Chain the delivery check

    Add Look Up Text Delivery Status right after the send module, and map what it needs from the send result. Your scenario now knows whether each SMS reached its recipient.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time and shows the bundles each module received, one bundle being one item passed along. Use your own phone number for this first try.

  5. 05

    Schedule and switch it on

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

Modules

What the Textbelt modules do

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

Textbelt1

Check Your Quota

Action

In Make“Checks your quota.”

Tells you how much sending capacity remains on your Textbelt account, so your scenario can react before a text fails for lack of credit.

When to use it
place it before a batch of messages, then add a filter that stops the run or alerts an admin when the quota comes back too low.
Watch out
checking the quota does not send anything, yet it still uses one operation of your Make plan each time it runs.
Textbelt2

Look Up Text Delivery Status

Action

In Make“Looks up text delivery status.”

Gives you the delivery status of an SMS you already sent, which turns a hopeful send into a confirmed one you can log or act on.

When to use it
right after Send a Text Message, when an appointment reminder or a security code really has to arrive and a failure should reach a person.
Watch out
it only reports on a message that exists, so map its input from the send module rather than typing a value by hand.
Textbelt3

Send a Text Message

Action

In Make“Sends a text message.”

Sends an SMS through your Textbelt account, with the number and wording built from whatever the earlier modules of the scenario collected.

When to use it
whenever an event in another app deserves a text, for example a new order, a booked call or a support ticket marked urgent.
Watch out
run your first tests on your own phone, because every run of the scenario sends a real message and draws on your Textbelt quota.
Need help

Need help automating Textbelt with Make?

A person reads every message.

FAQ

Textbelt and Make: common questions

01Is the Textbelt Make integration free?
Yes, on the Make side. Textbelt is a standard app, available from the Make Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two 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 count usage in credits per month. Sending the texts themselves depends on your Textbelt account and its subscription, which is priced by Textbelt, not by Make.
02What do you need to connect Textbelt to Make?
An active Textbelt account and an API key. Log in to Textbelt, open the API key generation page, click Generate API Key and copy the key. In Make, add a Textbelt module, click Create a connection, give it a name if you like and paste the key. Textbelt points you to its own pricing page for the subscription side. Once saved, the connection is shared by all three Textbelt modules, so you only do this once per account.
03Can a Textbelt scenario run in real time?
Not from Textbelt itself, because the app has no trigger module in Make. All three modules are actions, so something else has to start the scenario. Either put the trigger of another app first, such as a form or a store that reports new entries, or let the scenario run on its schedule, every 15 minutes by default and no less than 15 minutes on the Free plan. If the first app offers an instant trigger, the whole flow starts as soon as its event happens.
04What if the Textbelt module you need is missing in Make?
It depends on what you need. The Make app covers three actions: sending a text, looking up delivery status and checking your quota. There is no Make an API Call module for Textbelt, so you cannot reach other parts of its API from this app. When a use case goes beyond those three modules, look at another SMS or messaging app in Make, or ask the team for help designing the scenario. Make also marks its Textbelt documentation as AI-generated, so check important details with Textbelt.
05Should you use Make or n8n for Textbelt?
It depends on the tool your team already builds with. Textbelt often exists as an n8n node too, so the choice rarely comes down to this one app. On Make, Textbelt brings three action modules, runs from the Free plan and needs only an API key to connect. Start from the rest of your stack: if your other apps and scenarios already live in Make, adding a text step there is the simplest path. The comparison page linked above covers the broader differences between the two tools.
Same platform

Other docs you might need on this stack.

Browse all integrations