Resources · Make integration

Zyllio Make integrationAutomate Zyllio with Make.

Want Zyllio to fill its own tables and ping your users while you work elsewhere? The Zyllio Make integration gives you 9 action modules for rows, tables, notifications and files. This page shows how to link your account and build a first working scenario, step by step.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Zyllio Make integration let you automate?

The Zyllio Make integration links your Zyllio account to Make, so a scenario (the automation you build in Make, a chain of bricks called modules) can add, read, change or remove rows, refresh a table, send notifications and upload files in Zyllio. Something happens in another tool, and Zyllio updates itself without anyone copying data by hand.

Keep a table in step with a form. A new answer lands in your form tool, and Create a Row writes it into Zyllio. Refresh table then reloads the table so the fresh row shows up for the people using it.

Warn the right people when something changes. After Update a Row changes a status, Send Notification to a User pings the person concerned, while Send Notification to a Channel reaches a whole group at once.

Send files where they belong. A document created elsewhere can go straight into Zyllio through Upload file, instead of sitting in an inbox. On the Make Free plan a file can weigh 5 MB at most, so check the limits on Make pricing before you scale.

Zyllio has no trigger in Make: nothing in Zyllio starts a scenario by itself. You start it from another app's trigger or from the schedule on the first module. Make also warns that its own documentation for Zyllio is limited, so expect to test each module with Run once. If a run fails, Make troubleshooting covers the usual causes, and n8n vs Make helps if you are still choosing a tool.

Connect

How do you connect Zyllio to Make?

  1. 01

    Add a Zyllio module

    In your scenario, click the + and search for Zyllio, then pick any of its modules, for example Create a Row. Click Create a connection. A connection is your Zyllio account linked to Make once and reused by every Zyllio module.

  2. 02

    Name it and authorize

    Give the connection a name if you like, which helps when you juggle several accounts. Then authorize Make on the Zyllio page that opens, or paste the key Zyllio gives you, depending on what the window asks for.

  3. 03

    Save the connection

    Click Save. Make now lists what it can read in your account, so the module fields fill with choices instead of blank boxes. Every other Zyllio module you add later picks the same connection from a dropdown.

First scenario

Your first scenario with Zyllio and Make

GoalWhen a new entry arrives in another app, Make writes it as a row in Zyllio and notifies your team channel.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. Since Zyllio has no trigger, this first module comes from the app where your entries arrive.

  2. 02

    Add Create a Row

    Click the + on the right of that first module, search for Zyllio and pick Create a Row. Select your connection, or create it now, and choose the table Make lists for you.

  3. 03

    Map the data

    Fill each field of the row by dragging values from the first module, like a name or an email. Each value travels inside a bundle, one item passed from one module to the next.

  4. 04

    Notify the channel

    Add Send Notification to a Channel after Create a Row and write a short message that reuses a value from the new row, so the team sees what just came in.

  5. 05

    Test with Run once

    Click Run once and trigger one real entry. Open the bubble above each module to read the bundles it received, then check the row and the notification in Zyllio.

  6. 06

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default (Free plan minimum; paid plans go down to 1 minute), then switch the scenario on. Each module run counts as one operation on your plan.

Modules

What Zyllio can do in Make

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

Zyllio1

Create a Row

ActionIn the docs only

Adds a new row to a Zyllio table from data another module hands over, so records appear without anyone typing them in.

When to use it
a lead form, an order or a sign-up happens elsewhere and needs its own line in Zyllio.
Watch out
it writes one row for each bundle it receives, so check with Run once that you get as many rows as entries.
Zyllio2

Delete a Row

ActionIn the docs only

Removes a row from Zyllio for good, which keeps a table clean when the matching record disappears in another tool.

When to use it
a customer cancels, a ticket closes, and the line has no reason to stay.
Watch out
a deletion cannot be undone from Make, so test it with Run once on a dummy row before you switch the scenario on.
Zyllio3

Make an API Call

ActionIn the docs only

Calls any endpoint of the Zyllio API with the connection you already set up, which covers what the eight other modules leave out.

When to use it
you need an action the module list does not offer, and the Zyllio API does.
Watch out
this is the one module where you write the request yourself, and Make's documentation on Zyllio is limited, so get the API details from Zyllio first.
Zyllio4

Read a Row

ActionIn the docs only

Fetches one existing row so the next modules can use its values, for example to reuse an email or check a status before acting.

When to use it
a scenario must look at what Zyllio already holds before it writes or notifies anything.
Watch out
it reads one row, not a search; you need to know which row you want before this module runs.
Zyllio5

Refresh table

ActionIn the docs only

Going by its name, it asks Zyllio to reload a table, so the changes your scenario just made are what people see next.

When to use it
place it at the end of a scenario that has written several rows in a row, rather than after each write.
Watch out
each refresh is one more operation on your plan, so one call per run is usually enough.
Zyllio6

Send Notification to a Channel

ActionIn the docs only

Sends one message to a whole Zyllio channel, so a group hears about an event at the same moment.

When to use it
a new order, a new booking or a stock alert concerns the whole team rather than one person.
Watch out
if the scenario processes many bundles in one run, the channel gets one message per bundle; group them first when that becomes noise.
Zyllio7

Send Notification to a User

ActionIn the docs only

Reaches one specific person in Zyllio with a message built from your scenario data, like their own order number.

When to use it
a change concerns a single user, such as an approved request or a status that just moved.
Watch out
the scenario must know who that user is, so bring the identifier along from an earlier module, often Read a Row.
Zyllio8

Update a Row

ActionIn the docs only

Changes the values of a row that already exists, keeping one line per record instead of piling up duplicates.

When to use it
a payment is confirmed or a delivery ships, and the existing line in Zyllio should reflect it.
Watch out
pick the row carefully; mapping the wrong reference silently overwrites another record.
Zyllio9

Upload file

ActionIn the docs only

Sends a file from an earlier module into Zyllio, so documents land in the app rather than in someone's downloads.

When to use it
a contract, a photo or a PDF produced in another tool belongs next to its record in Zyllio.
Watch out
the Make Free plan caps files at 5 MB and total transfer at 512 MB, so test with a light file first.
Need help

Need help automating Zyllio with Make?

A person reads every message.

FAQ

Questions about the Zyllio Make integration

01Is the Zyllio Make integration free?
Yes, Zyllio is a standard app in Make, so it works on the Free plan. That plan has limits: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of run time at most, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) remove the cap on active scenarios, allow runs every minute and count usage in credits per month. Zyllio's own subscription is a separate matter this page does not cover.
02What is needed to connect Zyllio to Make?
A Zyllio account and a Make account. Make's documentation lists no special prerequisite and gives no official connection steps for Zyllio, so the generic path applies: add a Zyllio module, click Create a connection, optionally name it, authorize Make on the Zyllio page or paste the key Zyllio gives you, then click Save. Make itself says its documentation for this app is limited, so test the connection with Run once right after saving.
03Does Zyllio have a real-time trigger in Make?
No, Zyllio has no trigger at all in Make, neither scheduled nor instant. All 9 of its modules are actions. To start a scenario, use the trigger of another app as the first module, or run the scenario on a schedule set on that first module, every 15 minutes by default. The Zyllio modules then act on each bundle that comes through, such as writing a row or sending a notification.
04What if a Zyllio module is missing in Make?
Use Make an API Call. Zyllio has this module in Make, and it can reach any endpoint of the Zyllio API with the connection you already created, which covers actions the other 8 modules do not offer. Keep in mind that Make describes its Zyllio documentation as limited, so the details of that API come from Zyllio, not from Make. Test each request with Run once before switching the scenario on.
05Should Zyllio be automated with Make or n8n?
It depends on the tool your team already uses. Many apps have both a Make integration and an n8n node, but this page only confirms the Make side for Zyllio: 9 action modules, including Make an API Call. Check whether n8n offers a Zyllio node before comparing. If both exist, look at which modules each one gives you for your actual case, then decide on that basis rather than on the brand.