Resources · Make integration

Zaia Make integrationAutomate Zaia with Make.

Can Make send messages through Zaia without a single line of code? Yes. The Zaia Make integration gives you 2 action modules, one for Telegram messages and one for direct API calls. This guide links your account and walks you through a first working scenario.

Try the Zaia integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Zaia Make integration do for you?

The Zaia Make integration lets a Make scenario, the automation you build as a chain of bricks called modules, act on your Zaia account. Zaia brings two actions and no trigger, so another app or a schedule starts the flow, then Zaia does the work: it sends a Telegram message or calls its own API.

A Telegram alert the moment something matters. A new order, a signed form or a support ticket shows up in another app; the next module, Send a Telegram message, pushes the news through Zaia. Nobody has to watch a dashboard.

Reach what the menu does not show. Make an API Call talks to any endpoint of the Zaia API with the same connection. When the listed module is not enough, this is where you go before looking for another tool.

Fetch, then notify. Chain both: the API call reads or writes something in Zaia, and the Telegram step reports the result to your team, all inside one scenario.

Know the limit before you start: Make itself warns that its documentation for Zaia is incomplete, because little public information exists about the app. Test every module with real data. If you hesitate between tools, the n8n vs Make comparison sets out the criteria, the Make training covers the editor from scratch, and Make troubleshooting helps when a run fails.

Connect

How do you connect Zaia to Make?

  1. 01

    Add a Zaia module

    In your scenario, add either Zaia module and click Create a connection. A connection is your Zaia account linked to Make once; every Zaia module in every scenario reuses it afterward.

  2. 02

    Name it clearly

    Naming the connection is optional, but a label such as the workspace or the client it serves saves confusion later, especially once you manage several accounts in the same Make organization.

  3. 03

    Authorize and save

    Depending on what Zaia asks, either approve Make on the Zaia page that opens or paste the key Zaia gives you. Then click Save and the module is ready to fill.

First scenario

Your first scenario with Zaia

GoalWhen a new event lands in another app, Make sends a Telegram message through Zaia.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + in the middle of the canvas. That empty circle becomes your first module.

  2. 02

    Pick what starts it

    Zaia has no trigger, so choose the app where the event happens, such as your form tool or CRM, and pick its watch module. Link that account the same way.

  3. 03

    Add the Zaia action

    Click the + on the right of the first module, search Zaia and pick Send a Telegram message. Select your Zaia connection, then map data from the first module into the message.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time and shows each bundle, the item passed from one module to the next, so you can read exactly what Zaia received.

  5. 05

    Schedule and switch on

    Open the clock on the first module; a new scenario checks every 15 minutes by default. Adjust it if your plan allows, then switch the scenario on.

Modules

What each Zaia module does

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

Zaia1

Make an API Call

ActionIn the docs only

Opens the whole Zaia API to your scenario, reusing the connection you already created, so you can reach an endpoint that no ready-made module covers.

When to use it
the Telegram module does not do what you need and Zaia confirms an endpoint of its API that does.
Watch out
Make's own Zaia documentation is limited, so ask Zaia which endpoint to call and test the call with Run once before wiring anything after it.
Zaia2

Send a Telegram message

ActionIn the docs only

Delivers a Telegram message through your Zaia account from inside a scenario, filled with data mapped from the modules before it, so a team or a customer hears about an event without anyone typing.

When to use it
a form, an order or a ticket in another app should turn into a short Telegram notice.
Watch out
every message sent counts as one operation on your Make plan, so filter upstream to avoid noise.
Need help

Need help automating Zaia with Make?

A person reads every message.

FAQ

Questions people ask about Zaia and Make

01Is the Zaia Make integration free?
Yes, on the Make side. Zaia is a standard app, available from the Free plan. That plan allows 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Make counts operations: one module running on one bundle. Paid plans such as Core, Pro, Teams and Enterprise lower the interval to 1 minute and remove the cap on active scenarios. Whatever you pay Zaia is billed apart, by Zaia.
02What do you need to connect Zaia to Make?
A Zaia account and a Make account. Make's documentation lists no specific prerequisite for Zaia. You add a Zaia module, click Create a connection, optionally name it, then either authorize Make on the Zaia page or paste the key Zaia provides, and save. Make notes that its Zaia documentation is limited because little public information exists, so if the authorization screen differs from what you expect, look up the API access settings inside your Zaia account first.
03Can a Zaia scenario start on its own?
Not from Zaia itself, because the app has no trigger module in Make. Two options remain. You can start the scenario with a trigger from another app: a scheduled one, which Make checks at the interval you set, or an instant one, which that app calls through a webhook as soon as something happens. Or you can rely on the schedule of the scenario itself, every 15 minutes by default, and let the Zaia action follow. Either way, the Zaia modules run right after the first module.
04What if the Zaia module you need is missing?
Use Make an API Call. It reaches any endpoint of the Zaia API with the connection you already have, so you are not limited to the Telegram module. You need Zaia to tell you which endpoint to call and what to send, since Make says its own Zaia documentation is incomplete. Test the call with Run once and inspect the returned bundle before adding more steps. If the API does not expose what you need either, another app in your stack may hold that data.
05Should you use Make or n8n for Zaia?
It depends on the tool your team already runs. In Make, Zaia offers 2 action modules and a universal API call, which covers messaging and anything else the Zaia API exposes. Many apps also have an n8n node, so check whether Zaia does before deciding. Compare the editor, the way each tool counts usage and the skills available in your team, then build the same small flow in both and keep the one that your team finds easier to maintain.
Same platform

Other docs you might need on this stack.

Browse all integrations