Resources · Make integration

TextIt Make integrationAutomate TextIt with Make.

Your chatbot contacts can stay in sync with the rest of your stack. The TextIt Make integration gives you 13 modules: one instant trigger, 10 actions and 2 searches. This page shows you how to link your account, build a first scenario and pick the right module.

Try the TextIt integration on MakeSee the 13 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the TextIt Make integration automate?

The TextIt Make integration links your TextIt workspace to Make, a no-code tool where you chain apps together. You build a scenario (the automation itself), made of modules (its bricks), and TextIt contacts, labels and flows become things other apps can read and change.

Enroll new leads in a flow. A lead lands in a form or a CRM, Create a Contact adds that person to TextIt, and Start Contacts Down a Flow sends them straight into your welcome conversation on WhatsApp or SMS.

Log what your chatbot hears. The Universal Trigger wakes the scenario when the event you picked happens in TextIt, and the next module writes it to a spreadsheet or pings your team chat.

Keep your audience tidy. List Contacts pulls your audience, Update a Contact corrects each record and Create a Label gives you a clean segment for the next campaign.

Make does not add features TextIt lacks: every module works through your API token, and anything the listed modules skip goes through Make an API Call. TextIt also has an n8n node; our n8n vs Make page lays out the criteria. New to the editor? The Make training starts from zero, and the Make pricing guide explains plans and operations.

Connect

How do you connect TextIt to Make?

  1. 01

    Copy your TextIt API token

    In TextIt, click the gear icon at the bottom left to open workspace settings, then open API Token. If no token exists yet, create one with the button, and copy the token shown on screen.

  2. 02

    Open the connection window in Make

    Add any TextIt module to your scenario and click Create a connection. A connection is your TextIt account linked to Make once, then reused by every TextIt module. The Connection name field is optional.

  3. 03

    Paste the token and save

    Paste the API token you copied, or follow the on-screen instructions, and confirm. Make can now read and change contacts and labels in that workspace. You need an active TextIt account for this to work.

First scenario

Your first scenario: welcome every new lead in TextIt

GoalWhen a new lead reaches another app, Make adds the person to TextIt and starts them down your welcome flow.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big + to add the first module. That first module is the app where your leads arrive, a form tool or a CRM.

  2. 02

    Add Create a Contact

    Click the + on the right of the first module, search TextIt and pick Create a Contact. Link your account, then map the lead's details from the previous module into the contact.

  3. 03

    Send the contact into a flow

    Add Start Contacts Down a Flow next. Once the connection exists, Make lists what it can read from your workspace, so you pick the welcome flow and map the new contact.

  4. 04

    Test with Run once

    Click Run once and submit a test lead in the source app. Each module shows the bundles it received, a bundle being one item passing through, here one contact.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module, every 15 minutes by default, and turn the scenario on. From then on, each new lead gets the welcome conversation without anyone copying data.

Triggers

What starts a TextIt scenario?

1 module starts a scenario when something happens in TextIt. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by TextIt as soon as it happens.

TextIt1Universal Trigger

Universal Trigger

Instant trigger

In Make“Triggers when the selected event occurs.”

Universal Trigger gives you a single entry point for TextIt: you choose the event, and the scenario starts the moment that event happens in your workspace. It is the only trigger this app has, so every automation that reacts to TextIt begins here.

How it fires
instant, TextIt calls Make through a webhook as soon as the event happens, with no polling interval.
When to use it
when a chatbot conversation should push its result to a sheet, a CRM or a team alert without delay.
Watch out
click Create a webhook before Create a connection, and test with Run once while triggering the event yourself.
Modules

What can Make do in TextIt?

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

TextIt1

Create a Contact

Action

In Make“Creates a contact.”

Adds a new person to your TextIt audience, so someone who signed up elsewhere can receive your WhatsApp or SMS messages. It is usually the first TextIt step after a form or a CRM.

When to use it
a lead fills in a signup form and should be reachable by your chatbot.
Watch out
if the person may already exist, run List Contacts first and switch to Update a Contact instead.
TextIt2

Create a Label

Action

In Make“Creates a label.”

Creates a new label in TextIt, which gives you a named group to sort contacts into for targeting. The label is built from data in your scenario rather than typed by hand.

When to use it
a new event or product launch needs its own audience segment in TextIt.
Watch out
check List Labels first, or you may end up with two labels meaning the same thing.
TextIt3

Delete a Contact

Action

In Make“Removes a contact.”

Removes a contact from TextIt, which keeps people who left your service out of every future campaign. Use it as the last step of a cleanup, after the record has been checked.

When to use it
a customer closes their account in your main system and asks to be removed.
Watch out
treat a deletion as final, so test it on one sample contact with Run once.
TextIt4

Delete a Label

Action

In Make“Removes a label.”

Removes a label you no longer need, so the list of segments your team picks from stays short and readable. It works on one label at a time.

When to use it
a campaign has ended and its segment should disappear from the workspace.
Watch out
pair it with Get a Label or List Labels so the scenario deletes the right one and nothing else.
TextIt5

Get a Contact

Action

In Make“Gets a contact.”

Fetches one contact you already know, which gives the next modules its full record to work with. Think of it as opening a single contact card inside the scenario.

When to use it
the trigger only hands you a reference and you need the person's details before writing them elsewhere.
Watch out
it reads one contact; when you need to search across your audience, List Contacts is the module to pick.
TextIt6

Get a Label

Action

In Make“Gets a label.”

Reads one label so the scenario can confirm it exists and reuse its details in later modules. It is a quick check before you rename, delete or assign a segment.

When to use it
before Update a Label or Delete a Label, to be sure you are touching the intended segment.
Watch out
it returns a single label; to browse all of them, use List Labels.
TextIt7

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Calls any endpoint of the TextIt API with the connection you already set up, which covers whatever the other modules leave out. You write the request yourself, so it suits someone who has the TextIt API documentation open.

When to use it
you need a TextIt object or setting that none of the 12 other modules reaches.
Watch out
test each request with Run once and read the response bundle before switching the scenario on.
TextIt8

Start Contacts Down a Flow

Action

In Make“Starts contacts down a flow.”

Pushes contacts into one of your TextIt flows, the scripted conversations your chatbot runs, so a message goes out without anyone launching it by hand. This is the module that turns data from other apps into an actual conversation.

When to use it
a new customer should receive your onboarding sequence the moment their order is confirmed.
Watch out
run it on a test contact first, because real contacts will get real messages.
TextIt9

Update a Contact

Action

In Make“Modifies a contact.”

Changes an existing contact, so TextIt reflects what your CRM or shop already knows about that person. It saves you from deleting and recreating someone just to fix one detail.

When to use it
a customer changes plan or city in your main system and your chatbot should know.
Watch out
the scenario needs to identify the contact first, usually with List Contacts or the trigger's data.
TextIt10

Update a Label

Action

In Make“Modifies a label.”

Renames or edits an existing label, which lets a segment follow your campaigns without being recreated. It keeps the segment in place instead of starting a new one.

When to use it
a segment called "Beta testers" becomes your "Early customers" group after launch.
Watch out
anyone on your team filtering by the old name will not find it anymore, so tell them before the scenario runs.
TextIt11

List Contacts

Search

In Make“Gets all contacts.”

Returns contacts from your TextIt workspace as separate bundles, which means the modules after it run once for each person found. It is the module for bulk work and duplicate checks.

When to use it
you want to compare your TextIt audience with a CRM list before creating anyone.
Watch out
every returned contact costs an operation in each following module, so filter early when you can.
TextIt12

List Labels

Search

In Make“Gets all labels.”

Brings back all your labels, one bundle each, so the scenario can see which segments already exist before acting. Handy as a guard in front of label creation.

When to use it
a scenario should create a segment only when no label with that name is found.
Watch out
a search can return zero, one or several bundles, so plan what the scenario does when nothing comes back.
Need help

Need help automating TextIt with Make?

A person reads every message.

FAQ

TextIt and Make: common questions

01Is the TextIt Make integration free?
Yes, on the Make side. TextIt is a standard app, so its modules are 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. Each module run on a bundle counts as an operation against your monthly credits. Paid plans such as Core, Pro, Teams and Enterprise lower the interval to 1 minute. On the TextIt side, you need an active account.
02What do you need to connect TextIt to Make?
You need an active TextIt account and an API token. To get the token, click the gear icon at the bottom left of TextIt to open workspace settings, open API Token, create one if none exists and copy it. In Make, add a TextIt module, click Create a connection, give it an optional name and paste the token. For the Universal Trigger, which is instant, click Create a webhook before creating the connection. One connection then serves all 13 TextIt modules.
03Does the TextIt trigger in Make work in real time?
Yes. The Universal Trigger is an instant trigger: TextIt calls Make through a webhook as soon as the event you selected happens, so there is no polling interval to wait for. That is the lightning badge on the module in the editor. It is the only trigger in the TextIt app. If you would rather run a batch job, start the scenario with Make's own schedule, every 15 minutes by default, and put List Contacts or List Labels right after it.
04What if a TextIt module is missing in Make?
Use Make an API Call. It reaches any endpoint of the TextIt API with the connection you already created, so nothing needs a second setup. It is the right answer when the 12 action and search modules do not cover the object you need. The official Make documentation for TextIt notes that its content is AI-generated from TextIt's own docs and may contain mistakes, so check TextIt's documentation for anything important and contact TextIt directly for vendor questions.
05Should you use Make or n8n for TextIt?
It depends on the tool your team already works in. TextIt has an n8n node as well as this Make app, so both can move contacts and flows around. On Make, you get 13 ready modules including an instant Universal Trigger and Make an API Call for the rest, all in a visual editor with Run once testing. The better choice comes from your existing scenarios, your plan and who maintains them. Our comparison page linked above sets out the criteria side by side.
Same platform

Other docs you might need on this stack.

Browse all integrations