Resources · Make integration

Texting Base Make integrationAutomate Texting Base with Make.

Can a new lead get a text without anyone typing it? The Texting Base Make integration gives you 7 modules: 6 actions and 1 search to handle contacts and send messages. This guide shows who it suits, how to link your account and how to build your first scenario.

Try the Texting Base integration on MakeSee the 7 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Texting Base Make integration do for you?

The Texting Base Make integration links your Texting Base account to Make, a visual tool where you build a scenario: an automation made of modules, each module being one brick such as an action or a search. Texting Base has no trigger of its own, so its modules act when another app or a schedule starts the scenario.

Welcome every sign-up by text. A form tool or a CRM starts the scenario, Create a Contact saves the person in Texting Base, then Send a Message writes to them in the same run. A small training company can greet each new registrant this way.

Reach a whole audience at once. When a store changes its opening hours, Send a Message to a Group sends one announcement to a group instead of looping over each person.

Keep your list clean. List Contacts pulls your contacts so another app can compare them, and Delete a Contact removes someone who asked to stop receiving texts.

What Make does not give you here: a trigger that starts when something happens in Texting Base, and a full documentation page, since Make states it lacks public information on this app. Make an API Call is the way around a missing module. If you are still weighing tools, read our n8n vs Make comparison, check Make pricing, or learn the editor with Make training.

Connect

How do you connect Texting Base to Make?

  1. 01

    Open the connection window

    Add any Texting Base module to your scenario and click Create a connection. A connection is your Texting Base account linked to Make once, then reused by every Texting Base module you add later.

  2. 02

    Give the connection a name

    This step is optional, but a clear name such as the account or team it belongs to helps when you manage several accounts and need to pick the right one inside a module.

  3. 03

    Authorize Make and save

    Follow what the window asks: either approve Make on the Texting Base page that opens, or paste the key Texting Base gives you. Then click Save and the module is ready to fill.

First scenario

Your first scenario: greet new contacts by text

GoalWhen a new sign-up arrives from another app, Make adds the person to Texting Base and sends them a welcome message.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. Pick the app that receives your sign-ups, such as your form tool, and its trigger.

  2. 02

    Add Create a Contact

    Click the + on the right of that first module, search for Texting Base and choose Create a Contact. Click Create a connection if you have not linked your account yet.

  3. 03

    Map the sign-up data

    Fill the module fields with the data from the first module: Make shows what it received, so you click the values you need instead of typing them. Each item that flows through is called a bundle.

  4. 04

    Add Send a Message

    Add Send a Message after the contact module and write the welcome text. You can map the first name from the earlier modules so every text feels personal.

  5. 05

    Test with Run once

    Click Run once, then submit a test sign-up with your own number. Open each module's bundles to check what it received and whether the message reached your phone.

  6. 06

    Schedule and switch it 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 on your Make plan.

Modules

What each Texting Base module does

Texting Base gives you 7 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Texting Base1

Create a Contact

ActionIn the docs only

You get a new person in your Texting Base contacts without copying details by hand, fed by whatever app started the scenario.

When to use it
a lead fills a form or a client signs, and you want them on your texting list before anything else happens.
Watch out
run it before any message step, so later modules can map the contact it just created.
Texting Base2

Delete a Contact

ActionIn the docs only

This one takes a person out of your Texting Base contacts for good, which keeps your list in line with the people who still want to hear from you.

When to use it
someone unsubscribes in your CRM or asks your team to stop texting them.
Watch out
treat a delete as final and test it on a dummy contact with Run once before switching the scenario on.
Texting Base3

Get a Contact

ActionIn the docs only

Pull the details of one contact you already know, so the next modules can reuse them in a message or another app.

When to use it
an earlier module handed you a single contact and you need the rest of their record before writing to them.
Watch out
it reads one contact; to browse or filter many, reach for List Contacts instead.
Texting Base4

List Contacts

SearchIn the docs only

Your Texting Base contacts come back as separate bundles, ready to compare with a spreadsheet or a CRM.

When to use it
you want to check who is in Texting Base against another source, or clean up duplicates.
Watch out
as a search, it can return zero, one or many bundles, and every module after it runs once per bundle, which adds operations.
Texting Base5

Make an API Call

ActionIn the docs only

Reach any part of the Texting Base API that the six other modules do not cover, using the same connection you already set up.

When to use it
you need an action that has no ready module in this list.
Watch out
you must know the endpoint you are calling, and Make has little public documentation on this app, so check with Texting Base first.
Texting Base6

Send a Message

ActionIn the docs only

One person gets a text from your Texting Base account, written with data mapped from earlier modules, such as the first name of the person who signed up.

When to use it
a single event concerns one contact, like a confirmed booking or a new lead to welcome.
Watch out
placed after a search, it fires once per bundle, so filter the list first to avoid texting people twice.
Texting Base7

Send a Message to a Group

ActionIn the docs only

A whole group receives the same announcement in one step, instead of a scenario sending text after text to each member.

When to use it
news that concerns everyone in a group, such as a closure, a new schedule or a last-minute change.
Watch out
the text goes to all members at once, so run a test on a small group before using the real one.
Need help

Need help automating Texting Base with Make?

A person reads every message.

FAQ

Questions about the Texting Base Make integration

01Is the Texting Base Make integration free?
Yes, on the Make side. Texting Base is a standard app, so its modules are available on the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution at most, files up to 5 MB and 512 MB of data transfer. Paid plans drop the minimum interval to 1 minute and remove the cap on active scenarios. Usage is counted in operations, one per module run on one bundle. Your Texting Base subscription is a separate matter.
02What do you need to connect Texting Base to Make?
A Texting Base account and a Make account. Add any Texting Base module, click Create a connection, name it if you like, then either approve Make on the Texting Base page or paste the key Texting Base gives you, and click Save. Make lists no other prerequisite for this app. Its documentation is limited for lack of public information, so if the window asks for something unfamiliar, look in your Texting Base settings or ask their support.
03Does the Texting Base Make integration have a trigger?
No. All 7 modules are actions or searches, so a Texting Base scenario always starts somewhere else. You can open it with a trigger from another app, like a form or a CRM, and if that trigger is instant, the other app calls Make through a webhook as soon as something happens. You can also start the scenario on a schedule set on the first module, every 15 minutes by default, or as low as 1 minute on a paid plan.
04What if the Texting Base module you need is missing?
Use Make an API Call. It sends a request to any endpoint of the Texting Base API from inside your scenario, with the connection you already created, so you are not limited to the six ready-made modules. The catch is that Make states it cannot provide complete documentation for Texting Base, so you need the endpoint details from Texting Base itself. If that route is too technical, a texting app with a fuller module list may fit better.
05Should you use Make or n8n for Texting Base?
It depends on what you check first. On Make, Texting Base comes as a ready app with 7 modules, including Make an API Call, and it runs on the Free plan. The same app often has an n8n node too; check that Texting Base does before you compare. Then weigh the modules each tool offers for your use case and which editor your team already knows. Neither choice is ranked here.
Same platform

Other docs you might need on this stack.

Browse all integrations