Automate Sinch Build With Make: 3 Modules, SMS and WhatsApp

What you can automate

What can the Sinch Build Make integration do for you?

The Sinch Build Make integration lets a Make scenario (the automation you build, a chain of modules) send messages through your Sinch account. Another app supplies the event, such as a new order or a booked slot, and Sinch Build delivers the SMS or WhatsApp message to the right number, with no code to write.

Order updates by text. A store adds a row to a sheet or receives an order in its shop app; the next module, Send SMS message, texts the buyer that the parcel has left. Each run handles one bundle, meaning one item passed from module to module, here one order.

Appointment reminders on WhatsApp. A clinic or a salon books a slot in its calendar tool, and Send WhatsApp template message sends the template's wording to the client, filled with the date and name from the booking.

Everything the two modules skip. The directory mentions voice calls and verification checks, yet no dedicated module covers them. Make an API call can reach them with the same connection, as long as the Sinch API exposes them: check the Sinch documentation first.

Know the limits before you plan: Sinch Build has no trigger in Make, so it never starts a scenario by itself, and the official module docs are flagged as AI-generated, to be checked against Sinch. If you are still choosing a tool, the n8n vs Make comparison lays out the criteria, Make pricing explains the plans, and Make training takes you further than a first scenario.

Connect

How do you connect Sinch Build to Make?

01
Collect your Sinch keys
In the Sinch Dashboard, open Settings, then Access keys, and copy the API key and the Client secret. Then go to Project management in the same Settings section and copy the Project ID. Keep the three values at hand.
02
Open the connection window
Log in to Make, add a Sinch Build module to your scenario and click Create a connection. A connection is your Sinch account linked to Make once, then reused by every Sinch Build module you add later.
03
Paste and save
Give it a label in Connection name if you run several Sinch projects, which is optional. Paste the credentials you copied, or follow the on-screen instructions, and save. The module fields become available once Make accepts the keys.

First scenario

Your first scenario with Sinch Build

GoalWhen a new order lands in your shop app, Make texts the buyer through Sinch Build.

01
Create the scenario
On the Scenarios page, create a new scenario and click the +. Pick the app where the event happens, such as your shop or form tool, and choose its trigger for new orders.
02
Add Send SMS message
Click the + on the right of that first module, search for Sinch Build and pick Send SMS message. Choose your connection, or click Create a connection if you have not made one yet.
03
Map the order data
Fill the recipient with the phone number coming from the order, then write the message and drop in the buyer's name or the order reference from the previous module. Make shows those values as clickable items.
04
Test with Run once
Place a test order on your own phone number, then click Run once. Open the bundles each module received to check the number and the text, and confirm the SMS actually reached you.
05
Schedule and switch on
Set the schedule on the first module, every 15 minutes by default for a new scenario, and switch the scenario on. Each module run on one order counts as one operation on your Make plan.

Modules

What the Sinch Build modules do

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

Sinch Build1

Make an API call

Action

In Make“Performs and arbitrary authorized API call.”

This module reaches any endpoint of the Sinch Build API, reusing the connection you already created, so you are not stuck with SMS and WhatsApp templates only.

When to use it

you want something the directory mentions, such as a voice call or a verification check, and none of the other two modules offers it.

Watch out

you build the request yourself from the Sinch documentation, and the module docs are AI-generated, so confirm each endpoint with Sinch before going live.

Sinch Build2

Send SMS message

Action

In Make“Sends an SMS message to a recipient using the Sinch Conversation API.”

Your scenario sends a text to one recipient through the Sinch Conversation API, with names or references pulled from earlier modules so every message reads personal.

When to use it

a shipping notice, a payment reminder or an on-call alert that must reach a phone rather than an inbox.

Watch out

it only works once an SMS channel is configured in your Sinch account, and each text sent is one operation, so a test loop can burn through your plan fast.

Sinch Build3

Send WhatsApp template message

Action

In Make“Sends a WhatsApp template message to a recipient using the Sinch Conversation API.”

Here Make sends a WhatsApp message built from a template, not free text, which keeps the wording consistent across every customer you reach.

When to use it

a booking confirmation or a delivery update for customers who read WhatsApp more readily than SMS.

Watch out

the module expects a template rather than a message typed on the fly, so prepare the template in Sinch first and run a single test with Run once on your own number.

Need help

Need help automating Sinch Build with Make?

A person reads every message.

FAQ

Sinch Build and Make: common questions

01Is the Sinch Build Make integration free?

Yes, on the Make side. Sinch Build is a standard app, available from the Free plan, which allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run and files up to 5 MB. Paid plans (Core, Pro, Teams, Enterprise) lower the interval to 1 minute and count usage in credits per month. Your Sinch subscription is separate: check the Sinch Build pricing page for what messages cost on their side.

02What do you need to connect Sinch Build to Make?

You need an active Sinch account with an SMS channel already configured, plus three values from the Sinch Dashboard. Under Settings, then Access keys, copy the API key and the Client secret; under Project management, copy the Project ID. In Make, add a Sinch Build module, click Create a connection, optionally name it, and paste the credentials. The same connection then serves all three modules, including Make an API call.

03Does Sinch Build have a trigger to start a Make scenario?

No. All 3 modules are actions, so Sinch Build never starts a scenario on its own. The scenario begins with another app: a scheduled trigger that Make checks on the scenario's schedule, every 15 minutes by default, or an instant trigger that the other app fires through a webhook as soon as its event happens. Sinch Build then comes second, sending the SMS or WhatsApp message for each bundle it receives.

04What if the Sinch Build module you need is missing in Make?

Use Make an API call. It can call any endpoint of the Sinch Build API with the connection you already have, which should cover the voice calls and verification checks the directory mentions, if the Sinch API offers them. You write the request from the Sinch documentation yourself. Keep in mind that Make flags the Sinch Build module docs as AI-generated, so check important details with Sinch before relying on them.

05Should you use Make or n8n for Sinch Build?

It depends on the tool your team already runs. In Make, Sinch Build offers 3 action modules, a connection built from an API key, a Client secret and a Project ID, and a guided editor with Run once for testing. Many apps also exist as n8n nodes, but check whether Sinch Build has one before comparing. Base the choice on the modules each tool actually lists for your case, not on general claims about either platform.

Collect your Sinch keys

Open the connection window

Paste and save

Create the scenario

Add Send SMS message

Map the order data

Test with Run once

Schedule and switch on

Need help automating Sinch Build with Make?