Resources · Make integration

FireText Make integrationAutomate FireText with Make.

Can Make text your customers the moment something happens elsewhere? With the FireText Make integration, yes: 6 action modules send SMS, manage contacts and cancel scheduled messages. This guide connects your account and walks you through a first scenario, no code involved.

Try the FireText integration on MakeSee the 6 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the FireText Make integration do for you?

The FireText Make integration lets a Make scenario (the automation you build, a chain of steps) send SMS from your FireText account and manage your contact list. Each step is a module, one brick of the scenario. FireText brings 6 of them, all actions, so another app or a schedule starts the flow.

Welcome text for every new lead. A form tool catches a signup, Create a Contact saves the mobile number in FireText, then Send a Message greets the person by SMS. Nobody copies numbers by hand anymore.

A contact list that follows your CRM. When a customer changes plan or details in another tool, Get a Contact looks up the record by mobile number and Update a Contact rewrites it, so your next campaign hits the right people.

Cancel what no longer makes sense. If an order is refunded or a booking cancelled, Remove a Scheduled Message pulls the planned SMS before it goes out, as long as your scenario knows its ID.

What the integration does not do: FireText has no trigger in Make, so an incoming SMS or a reply cannot start a scenario by itself. For any endpoint the listed modules skip, Make an API Call reuses the same connection. New to the editor? The Make training covers the basics, and Make pricing explains how operations are counted. Weighing tools first? Read n8n vs Make.

Connect

How do you connect FireText to Make?

  1. 01

    Copy your API key in FireText

    You need an active FireText account and its API key. In FireText, open Settings, then API, and copy the key shown on screen. Keep that tab open, you paste it in the next step.

  2. 02

    Add a FireText module and create the connection

    In your scenario, add any FireText module and click Create a connection. A connection is your FireText account linked to Make once; every FireText module in your scenarios reuses it.

  3. 03

    Name it and paste the key

    The Connection name field is optional, but a clear name helps if you manage several accounts. Paste the API key, save, and Make is ready to talk to FireText.

First scenario

Your first scenario: welcome every new signup by SMS

GoalWhen a new lead signs up in your form tool, Make saves the number in FireText and sends a welcome SMS.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. Pick the trigger of the app that collects your leads, since FireText has none.

  2. 02

    Add Create a Contact

    Click the + on the right of the first module, search FireText, choose Create a Contact and pick your connection. Map the contact details coming from the form, starting with the mobile number.

  3. 03

    Add Send a Message

    Add Send a Message after it. Write the welcome text and map the same mobile number, so each lead gets the SMS right after being saved.

  4. 04

    Test with Run once

    Click Run once and submit a test entry with your own number. Each module shows the bundles it received, a bundle being one item passed along, 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 runs through by itself.

Modules

What each FireText module does

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

FireText1

Create a Contact

Action

In Make“Creates a new contact.”

Adds a new person to your FireText account, so a number captured in another tool becomes someone you can text right away.

When to use it
a lead fills in a form or a customer places a first order, and you want their mobile number in FireText without retyping it.
Watch out
if the person may already exist, run Get a Contact first and route known numbers to Update a Contact instead.
FireText2

Get a Contact

Action

In Make“Retrieves the stored contact information for a given mobile number in your account.”

Reads what FireText has stored for one mobile number, so the rest of your scenario can decide what to do with that person.

When to use it
before an update or a message, to check that the number is already in your account and see its current details.
Watch out
the lookup starts from a mobile number only, so an earlier step of your scenario has to supply that number.
FireText3

Make an API Call

Action

In Make“Performs an arbitrary API call.”

Calls any endpoint of the FireText API from your scenario, reusing the connection you already created, so you are not stuck when no ready module fits.

When to use it
the other five modules cover sending, contacts and cancellation; reach for this one only for something they leave out.
Watch out
you build the request yourself, so keep FireText's API documentation open next to the editor.
FireText4

Remove a Scheduled Message

Action

In Make“Removes a scheduled message specified by ID.”

Cancels an SMS that was planned for later, so a customer never receives a reminder that no longer applies.

When to use it
a booking is cancelled or an order refunded in another app, and the matching text should not go out.
Watch out
the module needs the ID of that scheduled message, so store it somewhere your scenario can find it; once removed, the message is gone.
FireText5

Send a Message

Action

In Make“Sends an SMS message from your FireText account”

Sends an SMS from your FireText account, the heart of most scenarios on this page: an event somewhere turns into a text on someone's phone.

When to use it
order shipped, appointment confirmed, form received, any moment where a short text beats an email.
Watch out
a click on Run once sends a real SMS, so test with your own number before mapping customer data.
FireText6

Update a Contact

Action

In Make“Updates an existing contact specified by mobile telephone number.”

Changes the details of a contact already in FireText, found by their mobile phone number, so your list stays in line with the tool where customers really live.

When to use it
a customer edits their profile in your CRM or shop and FireText should reflect it.
Watch out
the number identifies the contact, so a customer who switches phones needs Create a Contact for the new one.
Need help

Need help automating FireText with Make?

A person reads every message.

FAQ

FireText Make integration: frequent questions

01Is the FireText Make integration free?
Yes, on the Make side. FireText is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between 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) drop the interval to 1 minute and remove the cap on active scenarios. Usage is counted in operations, one operation being one module run on one bundle. Your FireText subscription is separate and billed by FireText.
02What do you need to connect FireText to Make?
An active FireText account and its API key. In FireText, go to Settings, then API, and copy the key displayed there. In Make, add any FireText module, click Create a connection, optionally give it a name, and paste the key. The connection is then shared by all six FireText modules, so you only do this once per account. If you do not have a FireText account yet, you create it on their side first.
03Can a FireText event trigger a Make scenario in real time?
No. FireText has no trigger module in Make, scheduled or instant, so nothing on the FireText side can start a scenario. You start it another way: with the trigger of another app, such as a form tool, a shop or a CRM, or with Make's own schedule on the first module, which runs every 15 minutes by default. FireText modules then come after that first step and act on the data it brings in.
04What if a FireText module you need is missing?
Use Make an API Call. It is part of the FireText app in Make and lets your scenario reach any endpoint of the FireText API with the same connection, which covers what the five other modules leave out. You write the request yourself, following FireText's API documentation. Also note that the Make documentation for FireText is flagged as AI-generated from the vendor's docs, so confirm important details with FireText directly.
05Should you use Make or n8n for FireText?
It depends on the tool you already run. On Make, FireText comes with 6 ready modules for sending SMS, handling contacts and cancelling scheduled messages, plus Make an API Call for the rest. The same app often has a node in n8n too, so check what it covers before choosing. Pick the platform where your other automations already live, since that keeps every connection and every scenario in one place.
Same platform

Other docs you might need on this stack.

Browse all integrations