Resources · Make integration

TurkeySMS Make integrationAutomate TurkeySMS with Make.

Need a text message to go out the moment something happens in another tool? The TurkeySMS Make integration gives you 4 action modules, from a single SMS to a one-time code. This page shows how to link your account and build a first working scenario.

Try the TurkeySMS integration on MakeSee the 4 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the TurkeySMS Make integration do for you?

The TurkeySMS Make integration lets a Make scenario (the automation you build in Make, a chain of bricks called modules) send text messages through your TurkeySMS account. It has 4 modules, all actions: they do something when the scenario reaches them, but none of them starts a scenario on its own.

Order confirmations by text. Another app, such as your shop or your form tool, starts the scenario. Send single SMS then writes to the customer with details pulled from that first step.

Login or sign-up codes. When a user needs to prove they own a phone number, Send OTP handles the one-time password message, so your app does not have to build its own SMS logic.

A balance check before a big send. Put Check account balance ahead of your SMS modules and read the result in the test run, so you know where your TurkeySMS account stands before messages start leaving.

What this integration does not do: it cannot watch TurkeySMS for events, because there is no trigger module. For anything the 4 modules skip, Make an API call reaches the rest of the TurkeySMS API with the same connection. Note that Make labels its TurkeySMS documentation as AI-generated, so check important details with TurkeySMS directly.

New to the tool? The Make review explains how it thinks, and Make pricing covers the plans. Weighing another platform instead? Read n8n vs Make.

Connect

How do you connect TurkeySMS to Make?

  1. 01

    Prepare your TurkeySMS account

    Make needs an active TurkeySMS account with a valid API key and an approved Sender ID. Log in to TurkeySMS, open the dashboard and copy the API key shown there.

  2. 02

    Add a TurkeySMS module

    In your scenario, add any TurkeySMS module and click Create a connection. A connection is your TurkeySMS account linked to Make once, then reused by every TurkeySMS module.

  3. 03

    Paste the key and save

    Give the connection a clear label in Connection name if you like; it is optional. Paste the API key you copied, or follow the instructions on screen, then save.

First scenario

Build your first scenario with TurkeySMS

GoalWhen a new order arrives in your shop app, Make texts the customer through TurkeySMS.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the +. TurkeySMS has no trigger, so the first module comes from the app where orders land.

  2. 02

    Add Send single SMS

    Click the + to the right of that first module, search for TurkeySMS and pick Send single SMS. Choose your connection, or click Create a connection if you have none yet.

  3. 03

    Map the order data

    Fill the module fields with data from the first module: the customer phone number and a short message. Each order travels as a bundle, one item passed from module to module.

  4. 04

    Test with Run once

    Click Run once and create a test order. Read the bundles each module received, then check that the text reached your own phone.

  5. 05

    Schedule and switch on

    Set the schedule on the first module (every 15 minutes by default, and 15 minutes is also the shortest on the Free plan), then switch the scenario on.

Modules

What each TurkeySMS module does

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

TurkeySMS1

Check account balance

ActionIn the docs only

As its name says, this module checks the balance of your TurkeySMS account. You would then find that balance in the bundle it returns, ready for the next modules and your test run.

When to use it
place it at the start of a scenario that sends messages, so the balance shows up next to every run you inspect.
Watch out
it counts as one operation each time it runs, even though it sends nothing.
TurkeySMS2

Make an API call

ActionIn the docs only

Here you call any endpoint of the TurkeySMS API directly, using the connection you already created, without a second login.

When to use it
TurkeySMS offers something in its API that the three other modules do not cover, and you want it inside the same scenario.
Watch out
you write the request yourself, so keep the TurkeySMS API documentation open while you set it up.
TurkeySMS3

Send OTP

ActionIn the docs only

Send OTP delivers a one-time password by text, the kind of short code a person types to confirm a login or a phone number.

When to use it
a sign-up form or a login in another app needs a verification code, and you would rather not code the SMS part yourself.
Watch out
an approved Sender ID is required on your TurkeySMS account before any code can leave.
TurkeySMS4

Send single SMS

ActionIn the docs only

With this module, one text message goes to one phone number, filled with whatever the earlier modules of your scenario collected.

When to use it
an order is confirmed, an appointment is booked or a ticket changes status, and the customer should hear about it by text.
Watch out
one message per bundle means ten new orders in a run produce ten texts and ten operations.
Need help

Need help automating TurkeySMS with Make?

A person reads every message.

FAQ

TurkeySMS and Make: common questions

01Is the TurkeySMS Make integration free?
Yes, on the Make side. TurkeySMS is a standard app, available from the Free plan. That plan allows 2 active scenarios, a scheduled run every 15 minutes at the shortest, 5 minutes of execution per run and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute and remove the cap on active scenarios. Your TurkeySMS subscription is separate: check the TurkeySMS pricing page for it.
02What do you need to connect TurkeySMS to Make?
You need an active TurkeySMS account with a valid API key and an approved Sender ID. The key sits on your TurkeySMS dashboard once you log in. In Make, add any TurkeySMS module, click Create a connection, optionally name it, then paste the key. That single connection then serves all 4 TurkeySMS modules, so you set it up only once per account. Both the key and the approved Sender ID are prerequisites, so check the two before you look for a problem on the Make side.
03Can a TurkeySMS scenario start in real time?
Not from TurkeySMS itself, because the app has no trigger module. The scenario has to start somewhere else: an instant trigger in another app, which that app fires through a webhook as soon as something happens, or a schedule set on the first module. A new scenario checks every 15 minutes by default. TurkeySMS modules then run as actions further down the chain. Each module that runs on a bundle counts as one operation on your plan, so a busy trigger app means more operations.
04What if a TurkeySMS module you need is missing in Make?
Use Make an API call. It reaches any endpoint of the TurkeySMS API with the same connection, so a feature the other three modules skip can still be part of your scenario. Keep in mind that Make marks its TurkeySMS documentation as AI-generated and suggests contacting TurkeySMS about anything important, so confirm the endpoint details with TurkeySMS before you rely on them. The request runs on the connection you already have, so no second login is needed in Make.
05Should you pick Make or n8n for TurkeySMS?
It depends on the tool your team already uses. On Make, TurkeySMS has 4 ready modules, a single connection and a spot on the Free plan, which is enough to send texts from other apps without code. Many apps also exist as an n8n node, so check whether TurkeySMS has one before you compare. Judge both on the modules you actually need rather than on the brand. If your other tools already live in Make, keeping TurkeySMS there saves you from maintaining two separate setups.
Same platform

Other docs you might need on this stack.

Browse all integrations