Resources · Make integration

Termii Make integrationAutomate Termii with Make.

Can Make send your Termii messages for you? The Termii Make integration gives you 11 modules: 1 trigger, 8 actions and 2 searches. This guide is for teams that already use Termii and have never built a scenario. It walks you from the API key to a working first scenario.

Try the Termii integration on MakeSee the 11 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Termii Make integration do for you?

The Termii Make integration links your Termii account to Make so that messages, tokens and sender IDs are handled by a scenario, the automation you build in Make, instead of by hand. Each step of a scenario is a module: one trigger, action or search from Termii or from another app.

Welcome a new signup. When a contact lands in your form tool or CRM, Send a Single Message sends them a message from Termii with the name and details mapped from that other app. Nobody has to copy a phone number again.

Confirm a phone number before you trust it. A signup flow can call Send a Token as soon as someone registers, then Verify a Token once they type the code back. Your other tools only learn about the contact after the check.

Keep an eye on your credit. Get Wallet Balance reads what is left on your Termii wallet, so a scenario can pass that figure to the team chat or a spreadsheet before a campaign goes out.

Some limits are worth knowing. Make's documentation for this app carries its own warning: it was generated with AI from Termii's docs and may contain mistakes, so check anything important against Termii. When a Termii feature has no module, Make an API Call reaches the rest of the API with the same connection. To judge Make as a whole, read our Make review; to weigh it against the other big option, see n8n vs Make, and for what you will pay, Make pricing.

Connect

How do you connect Termii to Make?

  1. 01

    Copy your API key from Termii

    Log in to your Termii dashboard and open Settings, then the API token tab. The key displayed there is the only credential Make asks for. You need an active Termii account for it to exist.

  2. 02

    Add a Termii module in Make

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

  3. 03

    Paste the key and save

    Paste the API key you copied, or follow the on-screen instructions, and confirm. Once the connection exists, the Termii modules of this scenario can use it without asking again.

First scenario

Your first scenario with Termii

GoalWhen a new contact reaches another app you use, Make sends them a welcome message through Termii.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big +. This first module is the trigger: pick the app where new contacts show up, such as your form tool or CRM.

  2. 02

    Set up the trigger

    Connect that app and fill its fields. Each new contact it returns becomes a bundle, one item that flows from a module to the next, carrying the name and phone number you will reuse.

  3. 03

    Add Send a Single Message

    Click the + on the right of the trigger, search for Termii and choose Send a Single Message. Create the connection with your API key, then map the phone number and name from the trigger into the message.

  4. 04

    Test with Run once

    Add a test contact in the source app, then click Run once. Make runs the scenario one time and shows the bundles each module received, so you can read what Termii answered before going live.

  5. 05

    Schedule and switch it on

    Click the clock on the first module to set the schedule; a new scenario checks every 15 minutes by default. Then switch the scenario on. Each module run counts as one operation on your Make plan.

Triggers

What starts a Termii scenario

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

Termii1Watch Events and Reports

Watch Events and Reports

triggerIn the docs only

Judging by its name, this trigger brings Termii's events and reports into Make, so a scenario can react to what happens on your account instead of you checking the dashboard. Make lists it without a description, so read its fields in the editor before you build on it.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default, and never less than 15 minutes apart on the Free plan.
When to use it
when a report from Termii should land in a sheet or a team channel without anyone exporting it.
Watch out
test it with Run once first and read the bundles it returns before you map anything from them.
Modules

Everything the Termii modules can do

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

Termii1

Create an In-App Token

ActionIn the docs only

Going by its name, it creates a token in Termii and hands it back to the scenario, so the code can be shown in your own app or email rather than sent by Termii itself. Make gives no description for it, so open its fields to see what it returns.

When to use it
when the code must appear on your own screen instead of in a message.
Watch out
checking the code later is the job of Verify a Token.
Termii2

Get Wallet Balance

ActionIn the docs only

Reads the balance of your Termii wallet and passes it to the next module, which turns a figure you usually look up by hand into data your scenario can act on.

When to use it
just before a batch of sends, to route the scenario to an alert when the balance looks too low.
Watch out
the module only reads the balance; topping up still happens in Termii.
Termii3

Make an API Call

ActionIn the docs only

Lets you call any endpoint of the Termii API from the scenario, using the connection you already created, so you are not stuck when a feature has no ready-made module.

When to use it
when none of the other ten Termii modules covers the request you need.
Watch out
you write the request yourself, so keep Termii's API reference open while you fill the URL and body.
Termii4

Register a Sender ID

ActionIn the docs only

Submits a new sender ID to Termii from the scenario, which saves you a trip to the dashboard each time a brand or a client needs its own name on outgoing messages.

When to use it
when a new client account is created in your CRM and needs its own sender name.
Watch out
check the result with Search Sender ID before a campaign uses the new name.
Termii5

Search Sender ID

SearchIn the docs only

Looks up sender IDs on your Termii account and returns what it finds as bundles, so the scenario can check a name before it uses it. Like every search module, it can return none, one or several results.

When to use it
after a registration, to confirm the sender name exists before a campaign.
Watch out
plan a route for the case where the search finds nothing.
Termii6

Search a Phone Number

SearchIn the docs only

As its name says, it looks up a phone number through Termii and returns the result as bundles, which helps you decide whether a number deserves a message at all. A search can come back with zero, one or more results.

When to use it
when a new lead arrives with a number you have never contacted.
Watch out
add a filter after it, or the next module runs even on an empty result.
Termii7

Send a Message using Number API

ActionIn the docs only

Sends a message through what Termii calls its Number API, a sending route that Make lists apart from the single message.

When to use it
when your Termii setup relies on that Number API; the name suggests sending from a phone number, which Termii's docs will confirm.
Watch out
Make gives no description of the difference with Send a Single Message, so check Termii's docs before choosing one over the other.
Termii8

Send a Single Message

ActionIn the docs only

Sends one message to one recipient with text and details mapped from earlier modules, which is the quickest way to answer an event in another app with a personal note.

When to use it
a booking confirmed, an order shipped, a form submitted: one person, one message.
Watch out
each bundle means one send, so a trigger that returns many contacts sends many messages.
Termii9

Send a Token

ActionIn the docs only

Asks Termii to send a token to a person, so a phone number can be confirmed without any code on your side. The scenario keeps what Termii returns for the check that follows.

When to use it
right after a signup or a login attempt that needs a second step.
Watch out
keep what this module returns; Verify a Token needs it when the person types the code back.
Termii10

Verify a Token

ActionIn the docs only

Checks the code a person typed against the token Termii issued, and tells the scenario whether it matches, so only confirmed contacts move on.

When to use it
when your form or app receives the code the user entered after Send a Token.
Watch out
put a router or a filter after it, so a failed check leads somewhere other than your CRM.
Need help

Need help automating Termii with Make?

A person reads every message.

FAQ

Termii and Make: common questions

01Is the Termii Make integration free?
Yes, on the Make side. Termii is a standard app, so its modules are available on the Free plan along with the rest of the 3,000+ standard apps. The Free plan keeps 2 active scenarios, at least 15 minutes between scheduled runs, 5 minutes per run and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and remove the cap on active scenarios. Your Termii account and its own pricing are separate: sending still uses your Termii subscription.
02What do you need to connect Termii to Make?
An active Termii account and its API key. You find the key in the Termii dashboard under Settings, in the API token tab, and copy it. In Make, add any Termii module, click Create a connection, give it a name if you want to, and paste the key. That connection is then reused by every Termii module in your scenarios, so you do this once per account rather than once per module.
03Does the Termii trigger in Make fire in real time?
No. Watch Events and Reports is a scheduled trigger: Make checks Termii on the scenario's schedule rather than being called the moment something happens. A new scenario checks every 15 minutes by default. On the Free plan that is also the shortest gap allowed; paid plans can go down to 1 minute. If you need a faster reaction to events coming from another app, start the scenario from that app's trigger and use the Termii modules as actions.
04What if a Termii module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Termii API with the connection you already set up, so a feature without its own module is still within reach. You write the request yourself, which means reading Termii's API reference. Also keep in mind that Make flags its Termii documentation as AI-generated and possibly wrong in places, so confirm module behavior against Termii before you depend on it in production.
05Make or n8n for Termii?
It depends on where your other automations already run. Make offers 11 Termii modules, including one scheduled trigger and Make an API Call for anything they do not cover. Many apps also have an n8n node, so check whether one exists for Termii and compare the actions it offers with the list on this page. Picking the tool your team already uses usually means fewer accounts, connections and habits to manage.
Same platform

Other docs you might need on this stack.

Browse all integrations