Resources · Make integration

Kaleyra Make integrationAutomate Kaleyra with Make.

Need Kaleyra to send a message when something happens in another tool? The Kaleyra Make integration offers 1 action module, Send a Message. This guide is for ops and support teams: link your API key, then build and switch on a first scenario.

Try the Kaleyra integration on MakeSee the 1 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Kaleyra Make integration do for you?

The Kaleyra Make integration lets a Make scenario, the automation you build in Make as a chain of modules, send a message through your Kaleyra account. Each module is one brick of that chain. Kaleyra brings a single action, so something else starts the flow: another app's module or a schedule you set in Make.

Confirm an order without typing anything. A module from your shop or form tool hands over the customer details, and Send a Message pushes the confirmation out through Kaleyra. The data travels as a bundle, one item passed from module to module.

Warn the team when a ticket escalates. Your helpdesk or CRM module spots the change, Make maps the ticket owner into Send a Message, and the right person hears about it without anyone watching a dashboard.

Send reminders on a timetable you control. With no trigger on the Kaleyra side, a scenario can simply run on its schedule, read a list from another tool and send one message per row. If you want to see how other apps start flows like this, the 123FormBuilder Make integration is a good example.

What Make does not do here: Kaleyra has no trigger, no search and no Make an API Call module in Make, so the page only covers sending. The official doc also flags that its content is AI-generated from Kaleyra's documentation, so check important details with Kaleyra. The same app often has an n8n node as well; the n8n vs Make comparison lays out how the two tools differ, and the Make training walks through scenario basics.

Connect

How do you connect your Kaleyra account to Make?

  1. 01

    Generate an API key in Kaleyra

    In Kaleyra, open Developers, choose API Keys and click Generate API Key. Give the key a name, add IP addresses to whitelist if your setup needs it, click Save, then copy both the API key and the Security Identifier (SID).

  2. 02

    Add the module and start the connection

    In your Make scenario, add the Kaleyra module and click Create a connection. A connection is your Kaleyra account linked to Make once, then reused by every Kaleyra module. The Connection name field is optional but helps later.

  3. 03

    Paste your credentials

    Enter the credentials you copied from Kaleyra, or follow the on-screen instructions Make shows, and confirm. From then on the connection appears in the dropdown whenever you add Send a Message to a scenario.

First scenario

Your first scenario with Kaleyra

GoalWhen a new record arrives in another app, Make sends a message through Kaleyra.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big +. Pick the app that holds the event you care about, such as a new form entry or a new order, and connect it.

  2. 02

    Add Send a Message

    Click the + on the right of that first module, search for Kaleyra and choose Send a Message. Select the connection you created, or click Create a connection if this is your first time.

  3. 03

    Map the data

    Fill the module fields and drag in values from the first module wherever the fields Make shows ask for them. Mapping is how the bundle from one app becomes the content of the next module.

  4. 04

    Test with Run once

    Click Run once to execute the scenario one time. Open the bubbles to read the bundles each module received and confirm the message went out as you expected before going further.

  5. 05

    Schedule and switch on

    Set the schedule on the first module; a new scenario runs every 15 minutes by default. Switch the scenario on. Each module run on a bundle counts as one operation on your Make plan.

Modules

What the Kaleyra module does

Kaleyra gives you 1 module. For each one: what it does for you, when to reach for it, and what to watch out for.

Kaleyra1

Send a Message

Action

In Make“Sends a message.”

You get a message sent from your Kaleyra account with content assembled from earlier modules, so updates reach people without anyone copying and pasting text between tools.

When to use it
at the end of a flow, once another app has supplied the details to send, for example after an order or a ticket change.
Watch out
it is an action, so it never starts a scenario by itself; place a trigger from another app or a schedule in front of it, and test with Run once first.
Need help

Need help automating Kaleyra with Make?

A person reads every message.

FAQ

Questions about the Kaleyra Make integration

01Is the Kaleyra Make integration free?
Yes, on the Make side. Kaleyra is a standard app, available from the Free plan, which gives you 2 active scenarios, a minimum of 15 minutes between scheduled runs, up to 5 minutes of execution, files up to 5 MB and 512 MB of data transfer. Paid plans bring a 1 minute minimum interval, unlimited active scenarios and 40 minutes of execution, with usage counted in credits each month. You still need a Kaleyra account and API key; for Kaleyra's own subscription, see its pricing page.
02What do you need to connect Kaleyra to Make?
You need a Kaleyra account and an API key. In Kaleyra, go to Developers, then API Keys, click Generate API Key, name it, whitelist IP addresses if required, save, and copy both the key and the Security Identifier (SID). In Make, add the Kaleyra module, click Create a connection, optionally name it and enter the credentials. The connection is then reused by every Kaleyra module in your scenarios, so this setup happens once.
03Can Kaleyra start a Make scenario in real time?
No, because Kaleyra has no trigger module in Make. You start the scenario another way: with a trigger from another app, which can be scheduled (Make checks at the interval you set) or instant (the app calls Make through a webhook), or with a plain schedule on the first module, every 15 minutes by default on a new scenario. Send a Message then runs as the next step whenever the scenario executes.
04What if the Kaleyra module you need is missing?
It depends on what you need. The Kaleyra app in Make has one module, Send a Message, and no Make an API Call module, so anything beyond sending is not covered by this app. You can pair Kaleyra with other apps in the same scenario to fetch or store data, or ask the team for help designing a workaround. The official doc also notes its content is AI-generated, so confirm important details directly with Kaleyra.
05Should you use Make or n8n with Kaleyra?
It depends on which tool your team already builds in. Kaleyra often has an n8n node too, so both routes can exist. In Make, you get one action module, Send a Message, placed after a trigger from another app or a schedule, and you test it with Run once in the visual editor. Compare the modules each tool offers for Kaleyra against the messages you plan to send, then pick the one your team will maintain.
Same platform

Other docs you might need on this stack.

Browse all integrations