Resources · Make integration

TelTel Calls and SMS text messaging Make integrationAutomate TelTel Calls and SMS text messaging with Make.

Send texts and place calls from your other tools, without writing code. The TelTel Calls and SMS text messaging Make integration gives you 6 modules: 1 trigger and 5 actions. This guide is for ops and sales teams who already use TelTel, and it walks you from the connection to a working scenario.

Try the TelTel Calls and SMS text messaging integration on MakeSee the 6 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the TelTel Calls and SMS text messaging Make integration do?

The TelTel Calls and SMS text messaging Make integration links your TelTel account to Make, a visual tool where you chain apps together without code. Once linked, Make can spot call events in TelTel, send one text or a batch of texts, start a call and check whether an SMS went through.

A follow-up text after a call. Start with Watch call events, then add Send single SMS text message so the person on the line gets a short written recap. A small sales team can use this to confirm what was agreed on the phone.

A reminder sent to a whole list. When a row lands in your spreadsheet or your CRM tags a group of customers, Send multiple SMS text messages pushes the same notice to everyone in one step. Follow it with Get SMS message status to see which texts were delivered.

A call placed from another app. Create a call lets an event elsewhere, such as a new lead in a form, open a phone call through TelTel, so nobody has to dial by hand.

Be aware of what the official documentation says about itself: the TelTel page on apps.make.com is marked as AI-generated and asks you to check important details with TelTel directly. The module list does not include any search module, and anything outside it goes through Make an API Call. TelTel often exists as an n8n node too; if you are still choosing a platform, read n8n vs Make, and for a wider look at the tool, our Make review. Teams that want help building it can reach our Make agency.

Connect

How do you connect TelTel to Make?

  1. 01

    Copy your API key from TelTel

    Log in to your TelTel account and open the section called API key, API Access or Credentials in the dashboard. Copy the key shown on screen. You need an active TelTel account for this, since Make signs in with that key.

  2. 02

    Add a TelTel module in Make

    In your scenario, add any TelTel Calls and SMS text messaging module and click Create a connection. A connection is your TelTel account linked to Make once, then reused by every TelTel module you add later.

  3. 03

    Name it and paste the key

    The Connection name field is optional, but a clear name helps when you run several accounts. Paste the API key you copied, or follow the on-screen instructions, then save. Make can now read and act on your TelTel account.

First scenario

Your first scenario: a text after each call event

GoalWhen Make spots a new call event in TelTel, it sends a text message to the number of your choice.

  1. 01

    Create the scenario

    Open the Scenarios page in Make and create a new scenario. A scenario is the automation you build: a chain of modules. Click the big + to place the first module.

  2. 02

    Place the trigger

    Search for TelTel Calls and SMS text messaging, pick Watch call events and click Create a connection with your API key. This module starts the scenario whenever it finds new call events.

  3. 03

    Add the text message

    Click the + on the right of the trigger and choose Send single SMS text message. Fill its fields and map data coming from the call event, so each text matches the call that started it.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles each module received, a bundle being one item passed along, here one call event. Check that the text looks right.

  5. 05

    Schedule and switch it on

    Open the clock on the first module. New scenarios check every 15 minutes by default, and the Free plan cannot go below 15 minutes. Pick your interval, then switch the scenario on.

Triggers

What starts a TelTel scenario

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

TelTel Calls and SMS text messaging1Watch call events

Watch call events

triggerIn the docs only

This trigger gives your scenario a starting point tied to what happens on your TelTel phone line: each new call event it finds becomes a bundle for the next modules. The documentation does not list which events it covers, so run a test before relying on it.

How it fires
scheduled, Make checks the app on the scenario's schedule, every 15 minutes by default, so expect a short delay.
When to use it
any time a call should lead to something else, like a follow-up text, a note in your CRM or a message to a colleague.
Watch out
every bundle it passes on is processed by the next modules, and each of those runs counts as an operation, the unit Make tracks on your plan.
Modules

What the TelTel modules do

TelTel Calls and SMS text messaging gives you 5 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

TelTel Calls and SMS text messaging1

Create a call

ActionIn the docs only

Starts a phone call through your TelTel account from inside a scenario, so an event in another tool turns straight into a call instead of a task on someone's list.

When to use it
a hot lead fills your website form and you want the phone to ring while interest is still high.
Watch out
the documentation gives no detail on its fields, so test with your own number first.
TelTel Calls and SMS text messaging2

Get SMS message status

ActionIn the docs only

Tells you what became of a text you already sent, so your scenario can react to failed messages instead of assuming every SMS arrived safely.

When to use it
place it after a send module when delivery matters, for instance before marking a customer as notified in your CRM.
Watch out
the documentation says nothing about its fields, so run a test on a text you sent to yourself.
TelTel Calls and SMS text messaging3

Make an API Call

ActionIn the docs only

Opens the rest of the TelTel API to your scenario, reusing the same connection, so you are not limited to the five ready-made actions listed on this page.

When to use it
you need something TelTel offers that no module covers, and you know which endpoint to call.
Watch out
you write the request yourself, so keep the TelTel API reference open while you build it.
TelTel Calls and SMS text messaging4

Send multiple SMS text messages

ActionIn the docs only

Sends texts to several recipients in a single module, which keeps a group notice in one step of your scenario rather than one send per person.

When to use it
a shop closes early, a delivery slot moves, or a session changes room and a whole list needs to know.
Watch out
check the list before running it; a text that has gone out cannot be taken back.
TelTel Calls and SMS text messaging5

Send single SMS text message

ActionIn the docs only

Sends one text to one number, the simplest way to put a short message on a customer's phone the moment something happens in another app.

When to use it
a booking is confirmed, an order ships or a call just ended and one person needs a quick written note.
Watch out
when the trigger returns many bundles, this module runs once per bundle, so one text each.
Need help

Need help automating TelTel Calls and SMS text messaging with Make?

A person reads every message.

FAQ

Questions about TelTel and Make

01Is the TelTel Calls and SMS text messaging Make integration free?
Yes, on the Make side. TelTel is a standard app, available from the Free plan, which allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, up to 5 minutes per run, files up to 5 MB and 512 MB of data transfer. Paid plans go down to 1 minute between runs, allow unlimited active scenarios and 40 minutes per run, and count usage in credits each month. The TelTel side is separate: you need an active TelTel account, and its pricing page tells you what your subscription covers.
02What do you need to connect TelTel Calls and SMS text messaging to Make?
An active TelTel account and its API key. You find the key in your TelTel dashboard, under a section named API key, API Access or Credentials, and copy it. In Make, add any TelTel module, click Create a connection, optionally give it a name, then paste the key or follow the on-screen instructions. That single connection is reused by every TelTel module in your scenarios, so you only do this once per account.
03Does the TelTel Calls and SMS text messaging trigger work in real time?
No. Watch call events is a scheduled trigger: Make checks TelTel on the scenario's schedule instead of being called by TelTel the moment a call happens. A new scenario checks every 15 minutes by default. On the Free plan you cannot go below 15 minutes, while paid plans allow checks as often as every minute. For call follow-ups this short delay is usually fine, but it is worth knowing before you promise customers an immediate text.
04What if a TelTel module is missing in Make?
Use Make an API Call. It lets your scenario call any endpoint of the TelTel API with the connection you already set up, which covers what the five listed actions and the single trigger leave out. You will need to read the TelTel API reference to build the request. Keep in mind that the TelTel documentation on Make is flagged as AI-generated, so confirm important details with TelTel before you depend on them.
05Should you use Make or n8n for TelTel Calls and SMS text messaging?
It depends on which platform your team already works in. On Make, TelTel comes with 6 ready modules, a visual editor and a connection that takes a single API key. TelTel often has an n8n node as well, so the choice rarely comes down to the app itself. Look at where your other automations live, who will maintain them, and which tool your team finds easier to read. Stay with one platform when you can, so every workflow sits in the same place.
Same platform

Other docs you might need on this stack.

Browse all integrations