Resources · Make integration

Telnyx (EU) Make integrationAutomate Telnyx (EU) with Make.

Can Make send your Telnyx messages and manage your AI assistants for you? Yes. The Telnyx (EU) Make integration gives you 12 modules: 7 actions and 5 searches. This guide connects your account, then builds a first scenario that sends a message.

Try the Telnyx (EU) integration on MakeSee the 12 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Telnyx (EU) Make integration do?

The Telnyx (EU) Make integration links your Telnyx account to Make, a tool where you build a scenario: an automation made of modules, each one a single brick that acts or searches. With it, Make sends messages through Telnyx and reads or edits your AI assistants, without a line of code.

Text a customer when something happens elsewhere. A new row in a spreadsheet or a signed quote in your CRM starts the scenario, and Send a message delivers the text from your Telnyx account. Every item that passes from one module to the next is called a bundle.

Keep your AI assistants in sync. Create an AI Assistant and Update an AI Assistant let a scenario set up or adjust an assistant from data kept in another tool, while Get available LLMs and List voices show which options your account offers.

Review what your assistants said. List AI assistant conversations pulls the conversations into Make, so you can copy them to a sheet, such as the one behind the Airtable Make integration.

One limit to know: this app has no trigger, so Telnyx cannot start a scenario by itself. The scenario opens on another app or on a schedule. When a listed module is missing, Make an API call reaches the rest of the Telnyx API with the same connection. To weigh Make against n8n, read n8n vs Make; for plan limits, see Make pricing.

Connect

How do you connect Telnyx (EU) to Make?

  1. 01

    Create an API key in Telnyx

    In the Mission Control Portal, click your name in the upper right corner, open API Keys and click Create API Key. Add a descriptive tag, pick the expiration settings, click Create and copy the key shown in the dialog.

  2. 02

    Open the connection window in Make

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

  3. 03

    Paste the key and save

    Give the connection a clear label in Connection name if you run several accounts, paste the API key you copied, and confirm. Make then shows the connection as ready in the module.

First scenario

Your first scenario with Telnyx (EU)

GoalWhen a new entry arrives in another app, Make sends a text through Telnyx (EU).

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. Since Telnyx (EU) has no trigger, pick the app where the event starts, such as your form tool or CRM.

  2. 02

    Add Send a message

    Click the + on the right of that first module, search for Telnyx (EU) and choose Send a message. Select the connection you created, or click Create a connection if this is your first Telnyx module.

  3. 03

    Map the data

    Fill the module fields and map the values that come from the first module, such as the contact to reach and the text to send. Make shows the data of the previous module so you can click it into place.

  4. 04

    Test with Run once

    Click Run once to execute the scenario one time. Open the bubble above each module to read the bundles it received and check that the message went out as expected.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. From now on each new entry in the first app leads to a message sent by Telnyx.

Modules

What each Telnyx (EU) module does

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

Telnyx (EU)1

Create an AI Assistant

ActionIn the docs only

This action sets up a new AI assistant in your Telnyx account straight from a scenario, so a new assistant can be born from data stored in another tool instead of a manual setup.

When to use it
a new client or project gets its own assistant, and the details already live in your CRM or a sheet.
Watch out
the doc lists no fields for this module, so open it in Make to see what it asks before you map anything.
Telnyx (EU)2

Get a message

ActionIn the docs only

Get a message brings back a single message from Telnyx into the scenario, so the modules after it can reuse what it holds for a report, a sheet or a follow-up.

When to use it
right after Send a message, when you want to store what was sent next to the customer record.
Watch out
it works on one message at a time and counts one operation, which is one run of one module on one bundle.
Telnyx (EU)3

Get an AI Assistant

ActionIn the docs only

Pick this action to read one AI assistant from your Telnyx account and pass its details to the next modules, for example to log its settings or compare them with what another tool expects.

When to use it
before Update an AI Assistant, to check the current state of the assistant you are about to change.
Watch out
it targets one assistant; to go through all of them, start with List AI Assistants.
Telnyx (EU)4

Get available LLMs

ActionIn the docs only

Here you get the list of language models your Telnyx account can offer to its assistants, which helps you choose the right one before you build or change an assistant from Make.

When to use it
in a setup scenario, ahead of Create an AI Assistant, so the model you map is one Telnyx actually provides.
Watch out
the Make doc for this app gives no detail on it, so run it once and read the bundle before you rely on it.
Telnyx (EU)5

List AI Assistants

SearchIn the docs only

A search that returns the AI assistants in your account, one bundle each, so a scenario can walk through them and act on every assistant in turn without you copying names by hand.

When to use it
for an inventory in a sheet, or to feed Update an AI Assistant for several assistants at once.
Watch out
a search can return zero, one or many bundles, and each module placed after it runs once per bundle.
Telnyx (EU)6

List AI assistant conversations

SearchIn the docs only

Your assistants' conversations come into Make through this search, ready to be copied to a sheet, a database or a helpdesk so your team can read them without opening Telnyx.

When to use it
when support or sales wants to review what an assistant told callers and spot the questions it could not answer.
Watch out
many conversations mean many bundles, so check the operations it will cost on your plan.
Telnyx (EU)7

List messaging profiles

SearchIn the docs only

This search shows the messaging profiles set up in your Telnyx account, so you can see from Make which profiles exist and reuse their details in the modules that come after.

When to use it
while you build or check a messaging scenario and want to confirm which profile your texts should go through.
Watch out
no module on this list edits a profile; for anything beyond reading, look at Make an API call.
Telnyx (EU)8

List phone numbers

SearchIn the docs only

With this search, Make returns the phone numbers held in your Telnyx account, one bundle per number, which is handy for an up to date inventory outside the portal.

When to use it
to copy your numbers into a sheet your finance or ops team already reads, or to pick a sender for Send a message.
Watch out
every later module runs once per number returned, which adds operations fast.
Telnyx (EU)9

List voices

SearchIn the docs only

List voices returns the voices Telnyx offers for its assistants, so you can choose one from real options instead of guessing its name when a scenario builds or edits an assistant.

When to use it
in a setup flow before Create an AI Assistant or Update an AI Assistant, when the voice is part of what you configure.
Watch out
as a search, it can send many bundles to the modules placed after it.
Telnyx (EU)10

Make an API call

ActionIn the docs only

When none of the listed modules covers your need, this one calls any endpoint of the Telnyx API from the scenario, reusing the connection you already created, so you never paste the key again.

When to use it
to reach a Telnyx feature that has no module on this list.
Watch out
you write the request yourself, so keep the Telnyx API documentation open next to Make.
Telnyx (EU)11

Send a message

ActionIn the docs only

The module most people come for: it sends a message from your Telnyx account, with the recipient and the text mapped from earlier modules, so an event in another app turns into a text.

When to use it
to confirm a booking, warn a customer about a delivery or alert your team when a form is filled.
Watch out
placed after a search, it sends one message per bundle, so test with Run once first.
Telnyx (EU)12

Update an AI Assistant

ActionIn the docs only

Use this action to change an existing AI assistant in Telnyx from a scenario, so its settings follow the data you keep elsewhere instead of being edited by hand in the portal.

When to use it
when an offer, a script or a model choice changes and the assistant must reflect it.
Watch out
the change applies to a live assistant, so read it first with Get an AI Assistant and test on one before a batch.
Need help

Need help automating Telnyx (EU) with Make?

A person reads every message.

FAQ

Telnyx (EU) and Make: common questions

01Is the Telnyx (EU) Make integration free?
Yes, on the Make side. Telnyx (EU) is a standard app, so its modules work from the Free plan. That plan allows 2 active scenarios, runs a scheduled scenario at most every 15 minutes, stops an execution after 5 minutes and handles files up to 5 MB with 512 MB of data transfer. Paid plans lower the interval to 1 minute and allow up to 40 minutes per run. Telnyx itself is billed separately under its own pricing, which this page does not cover.
02What does the Telnyx (EU) Make integration require?
An active Telnyx account and an API key. You create the key in the Mission Control Portal: click your name in the upper right corner, open API Keys, click Create API Key, add a tag, choose the expiration settings, click Create and copy the key. In Make, add a Telnyx (EU) module, click Create a connection, optionally name it, and paste the key. The same connection then serves every Telnyx module in your scenarios.
03Does the Telnyx (EU) Make integration have a trigger?
No. None of the 12 modules is a trigger, so Telnyx cannot start a scenario on its own. You start it in one of two ways: with a trigger from another app, such as a new form entry or a CRM update, or with the schedule set on the first module, which is every 15 minutes by default. The Telnyx modules then run as actions or searches later in the flow, each one on the bundles it receives.
04What if a Telnyx (EU) Make module is missing?
Use Make an API call. It reaches any endpoint of the Telnyx API from the scenario with the connection you already have, so a feature without its own module is still within reach. You write the request yourself, so the Telnyx API documentation is your guide. Also keep in mind that the Make doc for this app is AI-generated from Telnyx documentation and may contain mistakes, so check anything important with Telnyx directly.
05Is Make or n8n better for Telnyx (EU)?
It depends on your criteria, not on the app. This page covers Make, where Telnyx (EU) offers 12 modules, no trigger, and Make an API call for anything else. Many apps also have an n8n node, so check whether one exists for Telnyx before you decide. Compare the two tools on the modules your case needs and on where your other automations already run. The n8n vs Make comparison linked in the section above lays out the criteria without picking a winner.
Same platform

Other docs you might need on this stack.

Browse all integrations