Zistemo Make integrationAutomate Zistemo with Make.

You end up with an absence recorded in Zistemo without typing it twice, because the details come from the step before, such as a form answer or an approved request in another tool. The leave is then visible where you plan work.

A new Zistemo task appears the moment another app decides there is work to do, so requests stop living in inboxes. Map the title and the other fields from the previous module and the task is ready for your team.

Hours land in Zistemo without anyone opening a timesheet, since Make writes the entry from data it already has, for example a calendar event or a finished task. That keeps billing and reporting fed with the same numbers.

Your Zistemo item list grows on its own when a product or service is added somewhere else, which spares you the double entry and the typos that come with it. The item is built from the fields you map in the module.

A cancelled absence disappears from Zistemo automatically, so your planning never shows someone away who is actually working. The module needs to know which leave to remove, usually from Search Leaves or Get a Leave placed earlier.

Wrong or duplicated hours leave Zistemo without a manual cleanup, which keeps invoices and reports honest. Feed it the entry to remove, typically found by Search Time Entries a step before.

You receive the full record of one absence when you already know which one it is, so later modules can reuse its dates or its owner. It returns a single leave, not a list.

This pulls every detail of one known task into the scenario, which is handy when a trigger only gave you part of the picture. The result is a single bundle ready to be mapped.

One item from your Zistemo catalog comes back with its details, ready to be copied into a quote, a shop listing or a message. Use it when you already hold the item reference from an earlier module.

You get your Zistemo items back as a series of bundles, one per item, which lets Make copy, compare or clean the catalog in one pass. As a search module, it can return zero, one or many results.

This gives you the tasks already in Zistemo as separate bundles, so you can report on them, archive a batch or check for a duplicate. It is a search, meaning the result may be empty, a single task or many.

When none of the listed modules does what you need, this one lets you call any endpoint of the Zistemo API from your scenario, using the same connection you already set up. You keep one account link and gain access to the rest of the API.

A task that was parked comes back into play without anyone searching the archive, which is useful when a client reopens a topic. The module switches the status of one task you point it to.

Finished tasks leave your active list while staying on record, so the team sees only what is still open. You point it to one task and Make changes its status for you.

Tasks created by mistake or cancelled at the source get flagged as deleted automatically, which keeps the board clean without a manual sweep. It works on one task at a time.

An item you had set aside becomes available again in Zistemo without a trip through the settings, which matters when an offer returns to your range. The module changes the status of the item you pass to it.

Old items move out of the way while their history stays in Zistemo, so nobody picks a discontinued service by accident. You give it one item, and its status changes.

Items that should never have existed, such as a test entry or a duplicate, are flagged as deleted without opening Zistemo. The module acts on a single item reference.

Absences recorded in Zistemo come back as bundles, which lets Make check who is away before assigning work or sending a summary. As a search, it may find nothing, one leave or several.

You collect the hours already logged in Zistemo as separate bundles, ready for a report, a check or a correction. The result can be empty, a single entry or a long series.

The clock starts in Zistemo as soon as work begins elsewhere, so no minutes are lost because someone forgot to press play. Make launches the timer from the data of the previous step.

This closes a running timer in Zistemo when the work ends in another tool, which turns the elapsed time into tracked hours without a manual click. It pairs naturally with Start a Timer.

When someone moves their holiday, the leave in Zistemo follows without anyone editing it by hand. The module changes an existing absence that you identify with a reference from an earlier step.

A Zistemo task picks up changes made somewhere else, such as a new deadline agreed with a client or a new owner, so the team always reads the latest version. You map the new values from the previous module.

You fix hours in Zistemo from another tool, so a corrected meeting or a changed project code does not require a second manual edit. The module needs the reference of the entry to change.

Changes to a product or service made in your main tool reach the matching Zistemo item, so names and details stay the same everywhere. It edits one existing item.