Resources · Make integration

Infobip Make integrationAutomate Infobip with Make.

Need your other tools to send text messages through Infobip on their own? The Infobip Make integration gives you 3 modules: 1 trigger and 2 actions. This guide is for ops and marketing teams, and it walks you from the connection to a first working SMS scenario.

Try the Infobip integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Infobip Make integration do for you?

The Infobip Make integration links your Infobip account to Make, a no-code tool where you build a scenario: an automation made of modules, each module being one brick such as a trigger or an action. Once linked, other apps can make Infobip send text messages, and Make can react to the SMS your account sends.

Customers hear from you at the right moment. Put a trigger from your store, form tool or CRM at the start, then add Send an SMS. Every new order, booking or signup becomes a text message, written with the data that arrived from the first app.

Every sent message leaves a trace. Watch SMS picks up the SMS your Infobip account sends, so a scenario can copy each one into a spreadsheet or a CRM. Support staff then see what a customer received without opening Infobip.

The rest of the Infobip API stays within reach. When the two ready-made modules are not enough, Make an API Call reaches any endpoint of the Infobip API with the connection you already set up.

Keep the limits in mind. The Infobip catalog in Make is small, the only trigger is scheduled rather than instant, and Make itself labels this app's documentation as AI-generated from Infobip's own docs, so check anything critical with Infobip. Infobip often has an n8n node too; our n8n vs Make page lays out the criteria. To learn the editor step by step, see Make training, and for plan details read Make pricing.

Connect

How do you connect Infobip to Make?

  1. 01

    Collect your API key and subdomain

    In your Infobip dashboard, open the API keys section and copy the key shown in the list. Then note your subdomain, which appears at the top of the page or in the Base URL section. Keep both handy for the next step.

  2. 02

    Add an Infobip module

    Log in to Make, open your scenario and add any Infobip module, for example Send an SMS. Click Create a connection. You can type a label in Connection name, which helps later if several teams use different Infobip accounts.

  3. 03

    Enter your credentials

    Paste the credentials you copied from Infobip, or follow the instructions Make shows on screen. Infobip accepts an API key, basic auth, an IBSSO token or OAuth 2.0. Once saved, this connection is reused by every Infobip module in your scenarios.

First scenario

Build your first scenario: text a customer after an order

GoalWhen a new order comes in from your shop, Make sends the customer an SMS through Infobip.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + in the middle of the canvas. This first slot takes the trigger from your shop app, the event that starts everything.

  2. 02

    Set up the shop trigger

    Search for your shop app, pick its trigger for new orders and link your account. Make then lists what it can read, so you choose the store instead of typing it.

  3. 03

    Add Send an SMS

    Click the + on the right of the trigger, search for Infobip and pick Send an SMS. Choose your Infobip connection, then map the phone number and order details from the first module into the message.

  4. 04

    Test with Run once

    Place a test order to your own number and click Run once. Open the bubble above each module to read the bundle it received, meaning the single order or message that passed through.

  5. 05

    Schedule and switch on

    Click the clock on the first module to set Scheduling; a new scenario runs every 15 minutes by default. Then switch the scenario on so each new order gets its text.

Triggers

What starts an Infobip scenario

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

Infobip1Watch SMS

Watch SMS

Scheduled trigger

In Make“Triggers when a new SMS is sent.”

Watch SMS hands your scenario each new SMS your Infobip account sends, so you can archive it, log it next to a customer record or alert a colleague. Each message arrives as its own bundle for the next module.

How it fires
scheduled, Make checks Infobip on the scenario's schedule, every 15 minutes by default, and at 15 minutes at best on the Free plan.
When to use it
your support team wants a history of every text sent to a client inside a sheet or CRM.
Watch out
it reacts to sent messages; pairing it with Send an SMS in the same scenario would make each text trigger another one.
Modules

What the Infobip modules do

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

Infobip1

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call opens the whole Infobip API from your scenario, using the connection you already have, so anything the Infobip API offers without a dedicated module stays reachable.

When to use it
you need an Infobip feature beyond sending and watching SMS, and the two ready-made modules do not cover it.
Watch out
you write the request yourself, so keep the Infobip API documentation open and test with Run once first.
Infobip2

Send an SMS

Action

In Make“Sends an SMS message.”

Send an SMS turns data from any earlier module into a text message delivered through your Infobip account: an order confirmation, a booking reminder, a delivery update.

When to use it
an event in another app, such as a paid invoice or a new appointment, should reach the customer's phone without anyone typing.
Watch out
each bundle sends one message, so a sheet of many rows means as many texts; test on your own number before switching on.
Need help

Need help automating Infobip with Make?

A person reads every message.

FAQ

Infobip and Make: common questions

01Is the Infobip Make integration free?
Yes, on the Make side. Infobip is a standard app, so it works from the Free plan, which allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, runs of up to 5 minutes and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and remove the cap on active scenarios. Usage is counted in operations, one run of one module on one bundle. Your Infobip account is a separate matter: the messages themselves follow the subscription you hold with Infobip, so check their pricing page.
02What does the Infobip Make integration need to connect?
You need an active Infobip account and one of the authentication methods Infobip supports: an API key, basic auth, an IBSSO token or OAuth 2.0. With an API key, copy it from the API keys section of your dashboard and note your subdomain from the top of the page or the Base URL section. In Make, add any Infobip module, click Create a connection, optionally name it, then paste your credentials or follow the prompts. The connection is saved once and every Infobip module can use it.
03Does the Infobip trigger in Make fire instantly?
No. Watch SMS is a scheduled trigger, marked with a clock badge in the editor. Make asks Infobip for new sent messages each time the scenario runs, which is every 15 minutes by default. On the Free plan 15 minutes is also the shortest gap, while paid plans go down to 1 minute. Infobip has no instant trigger in Make, so if you need a faster reaction, start the scenario from the app where the event happens and use Send an SMS as the action.
04What if an Infobip module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Infobip API with the same connection as the other modules, so you are not limited to sending and watching SMS. You describe the request yourself, which takes a look at the Infobip API documentation. Also note that Make flags its Infobip documentation as AI-generated from the vendor's docs and possibly wrong in places, so confirm important details with Infobip directly. If a scenario fails, run it once and read the bundle of each module to see where it stopped.
05Make or n8n for Infobip: which one fits?
It depends on how you like to build. Make gives you 3 Infobip modules: Watch SMS, Send an SMS and Make an API Call, which covers any other endpoint with the same connection. Infobip often has an n8n node as well, so the choice rarely comes down to the app itself. Look at which tool your team already uses, how you want to count usage, and which editor feels clearer to you. Our comparison page on the two tools, linked higher up, goes through those criteria one by one without naming a winner.
Same platform

Other docs you might need on this stack.

Browse all integrations