Resources · Make integration

Texter Make integrationAutomate Texter with Make.

Want Texter to send a message when something happens in another tool? The Texter Make integration gives you 3 action modules and no trigger. This guide is for ops and marketing people who build their own flows: connect the account, then ship a first working scenario.

Try the Texter integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Texter Make integration do for you?

The Texter Make integration lets a Make scenario send messages through your Texter account without code. A scenario is the automation you build in Make, a chain of modules; a module is one brick of that chain. Texter only brings actions, so the event that starts the flow comes from another app or from Make's own clock.

A message that follows an event elsewhere. A lead fills a form, a booking is confirmed in a calendar tool: that app's trigger starts the scenario and Send a Message Without Header passes the news on through Texter, using the data mapped from the step before.

A message that carries a header. When your Texter setup relies on a header, Send a Message With Header is the variant to pick. The documentation does not describe what that header holds, so check the result on a test run before relying on it.

Anything the two senders do not cover. Make an API Call reaches any endpoint of the Texter API with the same connection, which is the way out when a listed module falls short.

Know the limits before you start. The Make documentation for Texter is marked as limited: no field list, no troubleshooting notes, no official connection steps. Plan a Run once test at each change. The Make review gives a wider picture of the platform, and if you are weighing tools, the n8n vs Make comparison sets the criteria side by side. Teams that would rather hand the build over can talk to our Make agency.

Connect

How do you connect Texter to Make?

  1. 01

    Add a Texter module

    Open your scenario, click the +, search for Texter and pick any of its modules. Make then asks for a connection: your Texter account linked to Make once, and reused by every Texter module afterwards.

  2. 02

    Create the connection

    Click Create a connection. You can give it a name, which helps when several people or several Texter accounts share the same Make organization and you need to tell them apart later.

  3. 03

    Authorize and save

    Follow what Texter asks for: either an authorization page where you approve access for Make, or a key from your Texter account that you paste into the field. Then click Save and the module is ready to fill.

First scenario

Your first scenario with Texter and Make

GoalWhen a new form answer arrives in another app, Make sends a Texter message with the details.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. Texter has no trigger, so this first module belongs to the app where the event happens, such as your form tool.

  2. 02

    Set up the starting app

    Pick that app's trigger, connect its account and fill its fields. Make lists what it can read once the connection exists, so you choose the form from a menu instead of typing an ID.

  3. 03

    Add the Texter action

    Click the + on the right of the first module, search Texter and choose Send a Message Without Header. Select your connection, then map the answer fields from the previous module into the message.

  4. 04

    Test with Run once

    Submit a test answer in the form tool, then click Run once. Make runs the scenario one time and shows the bundles each module received: one bundle is one item, here one form answer.

  5. 05

    Schedule and switch on

    Open the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on. From now on, each new answer ends up as a Texter message.

Modules

What the Texter modules do in Make

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

Texter1

Make an API Call

ActionIn the docs only

This module opens the whole Texter API to your scenario, reusing the connection you already created, so you are not stuck when the two message modules do not match your need.

When to use it
a Texter feature you know from the app has no dedicated module in Make, and you have the matching endpoint from Texter's API reference.
Watch out
you write the request yourself, and each run still counts as an operation, one execution of a module that Make bills on your plan.
Texter2

Send a Message With Header

ActionIn the docs only

Here you get a Texter message sent from the scenario with a header attached, built from data that earlier modules passed along, with no copy and paste on your side.

When to use it
your Texter messages are expected to carry a header, and the version without one would leave the recipient missing that part.
Watch out
the Make documentation does not say what the header contains, so read the first message delivered after Run once before switching the scenario on.
Texter3

Send a Message Without Header

ActionIn the docs only

You end up with a plain Texter message, fired at the exact step of the scenario where you place it, which makes it the simplest way to turn an event from another app into a notification.

When to use it
the message stands on its own and needs no header, as in the first scenario above, fed by a form answer.
Watch out
each bundle reaching this module sends one message, so a trigger returning ten items sends ten; filter upstream if that is too many.
Need help

Need help automating Texter with Make?

A person reads every message.

FAQ

Texter and Make: common questions

01Is the Texter Make integration free?
Yes, Texter is a standard app in Make, so it works from the 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 and Enterprise) bring the interval down to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations per month, and each Texter message sent uses at least one.
02What do you need to connect Texter to Make?
A Texter account and a Make account are enough to start, as the documentation lists no other prerequisite. The connection follows the generic Make flow: add a Texter module, click Create a connection, give it a name if you like, then approve access on the Texter page or paste the key Texter gives you, and click Save. Official connection steps for Texter are missing from the documentation, so if something blocks, look in your Texter account for the access method it provides.
03Can Texter start a Make scenario in real time?
No, Texter has no trigger module in Make, so it cannot start a scenario on its own. The flow has to begin elsewhere. Either you place the trigger of another app first, for example an instant trigger that the app calls through a webhook as soon as something happens, or you let Make start the scenario on its schedule, every 15 minutes by default. The Texter modules then act further down the chain, at the step where you put them.
04What if a Texter module you need is missing in Make?
Use Make an API Call. The module reaches any endpoint of the Texter API with the connection you already set up, so it covers what the two message modules leave out. You will need Texter's API reference to know which endpoint to call, because the Make documentation for Texter is marked as limited and describes no fields. Test each call with Run once and read the bundle that comes back before activating the scenario.
05Make or n8n for Texter?
It depends on the tool your team already runs. In Make, Texter comes with 3 action modules and no trigger, a generic API call module for the rest, and it is available from the Free plan among more than 3000 standard apps. Many apps also have a node in n8n, so check the n8n catalog for Texter before choosing. Compare the modules each side offers for the messages you want to send, rather than picking a platform on reputation.
Same platform

Other docs you might need on this stack.

Browse all integrations