Resources · Make integration

Chiavistello Make integrationAutomate Chiavistello with Make.

Can Make read your Chiavistello data without a single line of code? The Chiavistello Make integration gives you 9 action modules and no trigger. This guide shows how to link your account, which module to pick, and how to test a first scenario safely.

Try the Chiavistello integration on MakeSee the 9 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Chiavistello Make integration let you automate?

The Chiavistello Make integration links your Chiavistello account to Make so its modules can run inside a scenario, the automation you build in Make as a chain of modules. All 9 modules are actions: each one does a job when the scenario reaches it, and nothing in Chiavistello starts a scenario by itself.

A booking check that runs on its own. Put Elenco Prenotazioni first, let the Make schedule start the scenario, and hand what comes back to the next module of your choice.

A status snapshot for the IT team. Informazioni sul Chiavistello, Elenco Switch and Elenco Partizioni are the modules to read when someone needs what the app reports without opening Chiavistello; test them first, since the doc does not say what they return.

A payment follow up. Elenco Richieste di Pagamento pulls the payment requests the app holds, so another tool can file or share them.

Be clear about the limits: the Make doc states it has limited documentation for Chiavistello, and none of the 9 modules comes with an official description. The Italian names are your only guide, so every module deserves a Run once test before you trust it. Before you commit, read our Make review and check the Make pricing page. If you are weighing both tools, the n8n vs Make comparison sets them side by side.

Connect

How do you connect Chiavistello to Make?

  1. 01

    Add a Chiavistello module

    Open a scenario, click the +, search for Chiavistello and pick any of its modules. Then click Create a connection. A connection is your Chiavistello account linked to Make once and reused by every Chiavistello module.

  2. 02

    Name it if you like

    Giving the connection a name is optional. It helps when several people or several Chiavistello accounts share the same Make workspace, because the name is what you will see in every module later.

  3. 03

    Authorize and save

    Approve Make on the Chiavistello page that opens, or paste the key Chiavistello gives you, depending on what the window asks. Click Save. The doc lists no prerequisite for this step.

First scenario

Your first scenario with Chiavistello and Make

GoalWhen the Make schedule starts the scenario, Make reads the Chiavistello booking list and passes the result to the Notifica module.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. Since Chiavistello has no trigger, an action module will open the flow.

  2. 02

    Add Elenco Prenotazioni

    Search for Chiavistello, pick Elenco Prenotazioni and click Create a connection to link your account. Fill the fields Make shows you once the connection exists.

  3. 03

    Chain Notifica

    Click the + on the right of the first module and add Notifica. Map the data coming from Elenco Prenotazioni into its fields, since each item passed along is called a bundle.

  4. 04

    Test with Run once

    Click Run once to execute the scenario one time. Open each module and read the bundles it received: this is how you learn what these undocumented modules really return.

  5. 05

    Schedule and switch on

    Open the clock on the first module, the Scheduling setting, which runs every 15 minutes by default. Keep it or change it, then switch the scenario on.

Modules

What each Chiavistello module does in Make

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

Chiavistello1

Effettua una chiamata API

ActionIn the docs only

Its Italian name translates as make an API call, which points to a request you shape yourself rather than a fixed task. The doc gives no description, so treat that reading as a clue, not a promise.

When to use it
when none of the other eight Chiavistello modules returns what your scenario needs.
Watch out
run it once on its own and inspect the bundle before you map anything from it.
Chiavistello2

Elenco Partizioni

ActionIn the docs only

Here you get the partitions list of your Chiavistello account, going by the name, which means partition list. Nothing in the doc confirms what each partition holds.

When to use it
when a scenario must look at every partition at once, for example to copy them into a sheet.
Watch out
a list can come back as several bundles, and every later module then runs once per bundle, which costs operations.
Chiavistello3

Elenco Partizioni (lettura singola)

ActionIn the docs only

This variant carries the words single read in its name, so it reads as the one partition version of Elenco Partizioni. The doc does not say which field picks the partition.

When to use it
when your scenario already knows which partition it cares about and a full list would be noise.
Watch out
compare it with Elenco Partizioni in a Run once test to see which fields it expects.
Chiavistello4

Elenco Prenotazioni

ActionIn the docs only

Bookings are what this module lists, as its Italian name says. It makes a natural first module for a scheduled scenario, since Chiavistello has no trigger to start one.

When to use it
when a team outside Chiavistello needs to see or file the bookings.
Watch out
the doc says nothing about filters or sorting, so check in Run once how many bundles come back and in what shape.
Chiavistello5

Elenco Richieste di Pagamento

ActionIn the docs only

Payment requests are the subject here: the name means list of payment requests. Use it to bring that list into Make so a finance tool or a message can take over.

When to use it
when accounting wants the pending requests without logging into Chiavistello.
Watch out
payment data is sensitive, so choose carefully which later module receives it and who can open the scenario history.
Chiavistello6

Elenco Switch

ActionIn the docs only

With this action you read the switches known to Chiavistello, judging by the name, which reads switch list. The doc does not explain what a switch covers in the app.

When to use it
when an IT or facilities team wants an overview of every switch in one place, outside the app.
Watch out
each switch will likely arrive as its own bundle; add a Make aggregator if you want one summary instead.
Chiavistello7

Elenco Switch (lettura singola)

ActionIn the docs only

Pick this one to read a single switch instead of the full list, as the words single read in its name suggest. It keeps the output small when you only follow one switch.

When to use it
when a scenario reacts to one known switch and must not process the others.
Watch out
the doc lists no fields, so the way you point it at the right switch has to be found in the module itself.
Chiavistello8

Informazioni sul Chiavistello

ActionIn the docs only

Information about the Chiavistello itself is what the name promises. It fits the start of a scenario that first needs to confirm which Chiavistello account it is talking to.

When to use it
when you want a quick check that the connection works before the heavier list modules run.
Watch out
the doc does not detail what it returns, so read the bundle in Run once before mapping it.
Chiavistello9

Notifica

ActionIn the docs only

Notifica is Italian for notification, the only module whose name suggests it sends something rather than reads. That makes it the likely last step of a Chiavistello scenario.

When to use it
when the data read by an earlier module must end up as an alert on the Chiavistello side.
Watch out
every run of this module counts as an operation, so test it with Run once before the schedule starts it for real.
Need help

Need help automating Chiavistello with Make?

A person reads every message.

FAQ

Chiavistello and Make: common questions

01Is the Chiavistello Make integration free?
Yes. Chiavistello is a standard app, so it works from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute, allow unlimited active scenarios and 40 minutes of execution. Usage is counted in credits, one operation per module run on one bundle.
02What do you need to connect Chiavistello to Make?
A Chiavistello account and a Make account. Add any Chiavistello module, click Create a connection, give it a name if you want, then authorize Make on the Chiavistello page or paste the key the app provides, and click Save. The Make doc lists no extra prerequisite. The same connection then serves all 9 Chiavistello modules, so you only do this once per account. Since the doc gives no official steps, follow what the authorization window shows you.
03Does Chiavistello have a trigger in Make?
No. All 9 modules are actions, so Chiavistello cannot start a scenario on its own. You start it another way: set the schedule on the first module, every 15 minutes by default, or open the flow with a trigger from another app. A Chiavistello action such as Elenco Prenotazioni then runs at each start. On the Free plan the schedule cannot go below 15 minutes; paid plans go down to 1 minute.
04What if a Chiavistello module is missing in Make?
It depends on what you need. Chiavistello has no Make an API Call module, and the Make doc says its documentation for this app is limited. First test the 9 existing modules with Run once to see what they return. If none fits, look at whether another app in your stack can supply the data, or ask the Hack'celeration team to look at your case. Keep in mind that every module run on one bundle is an operation, so a test on a small scenario costs little.
05Make or n8n for Chiavistello?
It depends on the tool your team already runs. On Make, Chiavistello offers 9 action modules and no trigger, so every scenario starts from a schedule or from another app. Before you decide, check whether n8n has a node for it: the same app often exists in both. Our n8n vs Make comparison lays out the differences without ranking the two tools. Both paths start the same way: list what you want Chiavistello to do, then check which tool covers it.
Same platform

Other docs you might need on this stack.

Browse all integrations