Resources · Make integration

Sinch Engage Make integrationAutomate Sinch Engage with Make.

Need a text message to go out when something happens in another tool? The Sinch Engage Make integration gives you 3 action modules, including Send an SMS. This guide is for ops and support teams: link your account, then build a first working scenario.

Try the Sinch Engage integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Sinch Engage Make integration do for you?

The Sinch Engage Make integration links your Sinch Engage account to Make, a no-code tool where you build a scenario: an automation made of modules, each module being one brick such as an action. Sinch Engage brings 3 action modules, so another app starts the flow and Sinch Engage does the messaging part.

Text a customer when their order ships. A new row in your order tool starts the scenario, and Send an SMS pushes the update to the buyer's phone. Every item that moves between modules is called a bundle: here, one order.

Look at incoming replies. Inbound Message sits in the list as an action module. The official documentation gives it no description, so run it once on a test scenario to see what it returns before relying on it.

Reach what the list leaves out. Make an API Call calls any endpoint of the Sinch Engage API with the connection you already set up. It is the fallback when neither of the other two modules covers your case.

One limit to keep in mind: Sinch Engage has no trigger in Make, so the scenario always starts from a schedule or from another app. If you are weighing tools, read n8n vs Make. For the basics of the editor, the Make training walks through a full build, and Make troubleshooting helps when a run fails.

Connect

How do you connect Sinch Engage to Make?

  1. 01

    Create an API key in Sinch Engage

    In Sinch Engage, open Settings > API Settings and scroll to Basic Authentication. Click Create new key, give it a name you will recognize, then click Create Key.

  2. 02

    Open the connection window in Make

    Add any Sinch Engage module to your scenario and click Create a connection. A connection is your Sinch Engage account linked to Make once, then reused by every module of the app. The Connection name field is optional.

  3. 03

    Paste your credentials and save

    Enter the API key and the API token that Sinch Engage displayed in its modal, then save. If Make shows its own on-screen instructions instead, follow them to finish the link.

First scenario

Your first scenario with Sinch Engage

GoalWhen a new record appears in another app, Make sends an SMS through Sinch Engage.

  1. 01

    Create a blank scenario

    From the Scenarios page, create a new scenario and click the + in the middle of the editor to add the first module.

  2. 02

    Pick the app that starts the flow

    Sinch Engage has no trigger, so the first module comes from another app: your form tool, CRM or spreadsheet. Pick its module and connect that account.

  3. 03

    Add Send an SMS

    Click the + on the right of the first module, search for Sinch Engage and choose Send an SMS. Select the connection you created earlier.

  4. 04

    Map the data

    Fill the module fields by mapping values from the first module, so the message carries the right details. No retyping: you pick them from what the first module returned.

  5. 05

    Test with Run once

    Click Run once to execute the scenario one time. Then read the bundles each module received and check the message that left.

  6. 06

    Schedule and switch it on

    Set the schedule on the first module (every 15 minutes by default), then turn the scenario on. Each module run on one bundle counts as one operation on your plan.

Modules

What each Sinch Engage module does

Sinch Engage gives you 3 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Sinch Engage1

Inbound Message

ActionIn the docs only

Judging by its name, this one deals with messages your contacts send back. Make lists it as an action, and the official documentation says nothing about what it returns or which fields it asks for.

When to use it
when you want to explore how replies from your contacts could feed a scenario, on a test build first.
Watch out
it is an action, not a trigger, so it cannot start a scenario on its own; check its output with Run once before you map anything.
Sinch Engage2

Make an API Call

ActionIn the docs only

Here you reach any endpoint of the Sinch Engage API from your scenario, while reusing the connection you already created, so there are no extra credentials to paste.

When to use it
when neither Send an SMS nor Inbound Message covers the task, for example a Sinch Engage feature the list leaves out.
Watch out
you need to read the Sinch Engage API documentation to know the endpoint and the body to send.
Sinch Engage3

Send an SMS

ActionIn the docs only

Your customer gets a text message from your Sinch Engage account, built from data another app passed along: an order, a booking or a support ticket.

When to use it
right after the module that detects the event, as the last step of the flow, when a text is the fastest way to reach the person.
Watch out
each bundle that reaches this module sends one message, so test with Run once on a single record before activating.
Need help

Need help automating Sinch Engage with Make?

A person reads every message.

FAQ

Sinch Engage and Make: common questions

01Is the Sinch Engage Make integration free?
Yes, on the Make side. Sinch Engage is a standard app, so it works from the Free plan onward. The Free 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 and Enterprise) bring the interval down to 1 minute and remove the cap on active scenarios. You still need a Sinch Engage account of your own; its subscription is handled on the Sinch Engage side.
02What do you need to connect Sinch Engage to Make?
An active Sinch Engage account and a pair of API credentials. In Sinch Engage, go to Settings, then API Settings, scroll to Basic Authentication and click Create new key. Name it, click Create Key and copy both the API key and the API token from the modal. Back in Make, add a Sinch Engage module, click Create a connection and paste the two values. The connection name is optional, and every Sinch Engage module in your scenarios then reuses that same connection.
03Can a Sinch Engage scenario in Make react in real time?
Not from Sinch Engage itself: the app has no trigger module in Make, only 3 actions. The scenario therefore starts in one of two ways. Either another app's trigger opens the flow, and if that trigger is instant, the app calls Make through a webhook as soon as something happens. Or you run the scenario on a schedule set on its first module, every 15 minutes by default. Sinch Engage then acts inside the flow, for example with Send an SMS.
04What if a Sinch Engage module is missing in Make?
Use Make an API Call. This module can call any endpoint of the Sinch Engage API with the connection you already set up, so it covers what Send an SMS and Inbound Message do not. You will need the Sinch Engage API documentation to pick the right endpoint. Also note that the Make documentation for this app is marked as AI-generated from the vendor docs and may contain mistakes, so check important details with Sinch Engage directly.
05Should you use Make or n8n for Sinch Engage?
It depends on what you already run. In Make, Sinch Engage offers 3 modules, works on the Free plan, and Make an API Call reaches the rest of the API with the same connection. n8n often has a node for the same app, but check that one exists for Sinch Engage and what it covers before choosing. Compare the two on the modules you actually need and on the tool your team already uses, rather than on the brand name.
Same platform

Other docs you might need on this stack.

Browse all integrations