Resources · Zapier integration

Maestro Zapier integrationAutomate Maestro with Zapier.

The Maestro Zapier integration gives you 3 triggers, 2 actions and 0 searches. Zapier can notice when an item reaches a status, when a field changes or when a given item moves, then create or update items in a process for you.

See the 5 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Maestro Zapier integration does for you

The integration links Maestro, a tool that orchestrates business processes without code, to Zapier, the service that chains your apps so updates travel on their own. On Zapier, Maestro works on items inside a process: three ways to notice that one has changed, and two ways to create or update one.

Three results come back again and again. The first is a status alert. New or Updated Item in a Specified Status watches one status of one process, and a message goes out whenever an item lands there, so the person who takes over knows straight away.

The second is a change log. Updated Field notices item updates that touch a given field, and a spreadsheet row keeps the trace. The third is intake: a form or another tool feeds Create Item, and the item appears in the status you chose, ready for the process to run.

Now what Zapier does not do here. There is no search step, so a Zap cannot look an item up by name before updating it: Update Item needs the item ID handed over by an earlier step. Nothing deletes an item either. And every operation asks for a Process Id, so you need to know which process you are working in. Weighing platforms first? See our n8n vs Zapier and Make vs Zapier comparisons.

Vocabulary

Zapier words, in one minute

Seven terms are enough to read the rest of this page. Each one is used exactly as defined here.

Zap
The automation you build on Zapier: one starting event, then one or more steps that run every single time that event happens.
Trigger
The event in an app that opens the Zap. Once the Zap is switched on, Zapier waits for that event and nothing else.
Action
The step that works once the Zap has started: it writes, sends or moves something in an app on your behalf.
Task
The unit Zapier bills: one action your Zap completes successfully. The allowance on your plan is a count of those.
Polling vs instant
A polling trigger is checked by Zapier on a timer; an instant trigger is reported by the app itself the moment it happens.
Filter
A step that lets the Zap go on only when what arrived meets a condition you set, and stops it there otherwise.
Multi-step Zap
Any Zap beyond one trigger and one action. A second action or a filter makes one, and it then needs a paid plan.
Cost

What a Maestro Zap really costs

Zapier bills the work done, not the watching. All three Maestro triggers can check as often as your plan allows without costing a thing.

  • TriggerNever billed
  • Each successful action1 task
  • Free plan100 tasks a month, two-step Zaps
  • Premium appNo
  • Maestro triggers3, all polling

The trigger never costs a task, and Zapier looking for new data is free too. Each action that succeeds counts once; one that fails is not billed. Maestro is not a premium app, so it runs on the free plan: 100 tasks a month, but only two-step Zaps. A filter or a second action makes the Zap multi-step, which needs a paid plan. All three triggers poll, so the grid below sets how quickly a change in Maestro reaches your Zap.

Connect

Connect Maestro to Zapier in three steps

  1. 01

    Open your connections

    In your Zapier account, go to the Apps page and click + Add connection. A connection is your Maestro account linked once, then reused by every step that calls Maestro.

  2. 02

    Pick Maestro

    Type Maestro in the search box of the dialog, select it, then click Add connection. You need a Maestro account already in place before this step, since Zapier links to it.

  3. 03

    Sign in and allow access

    A new tab opens. Sign in to Maestro there and grant Zapier access to the account. Back in Zapier, the connection shows in your list, ready for triggers and actions.

First Zap

Your first Zap: a message when an item reaches a status

GoalEach item that is created or updated in the status you pick goes through a filter, and the ones that pass send a message to your team chat.

  1. 01

    Start from Maestro

    Create a Zap, choose Maestro and pick New or Updated Item in a Specified Status. Fill in the Process Id and the Status ID: both are required.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent items from the connected account, so you map the next steps on a real one.

  3. 03

    Add the filter

    Click the plus icon and add a Filter. Fill its three boxes: the field to look at, the rule, and the value to compare with. Use a text rule for text.

  4. 04

    Send the message

    Add your team chat with its send message action, then write the message with what the trigger brought back, so the reader knows which item moved.

  5. 05

    Test, then publish

    Test each step and read what came back before moving on. Then click Publish to switch the Zap on. With a filter it has three steps, so it needs a paid plan.

Triggers

The Maestro triggers

3 events start a Zap when something happens in Maestro. Zapier checks for them at the interval your plan allows.

1

New or Updated Item in a Specified Status

Polling trigger

In Zapier“Triggers when a new item is created or an existing item is updated in a specified status.”

Pick a process and one of its statuses, and this trigger catches every item created in that status, plus every existing item updated while it sits there. One status becomes a signal you can act on.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
when one status means a handover, and whoever owns the next stage should hear about it without watching Maestro.
Watch out
it needs both a Process Id and a Status ID, so one Zap only watches one status of one process.
2

Updated Field

Polling trigger

In Zapier“Triggers when an item update contains the target field.”

Here the Zap starts when an item update contains the field you target. Other edits to the same item leave it quiet, which keeps the noise down when items change all day.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
when only one piece of information matters downstream and you want a record each time it changes.
Watch out
it asks for a Process Id, so a field with the same name in another process is not covered by this Zap.
3

Updated Item

Polling trigger

In Zapier“Triggers when a specified item is updated.”

This one follows a single item you name. Each time that item is updated, Zapier picks up the change from its history and starts the Zap, whatever was edited.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
for one item that deserves close follow-up, where every update should reach the people involved.
Watch out
it needs a Process Id and an Item ID, so it never covers a whole process, only that one item.
Actions

The Maestro actions

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

1

Create Item

Action

In Zapier“Creates a new item in specific status.”

Adds a new item to a process, placed in the status you set, so work coming from elsewhere enters the flow at the right stage.

When to use it
when requests arrive through another app and each one should become a Maestro item without retyping.
Watch out
the Process Id is required, and pointing it at the process your trigger watches can set the Zap off again.
2

Update Item

Action

In Zapier“Updates a specified item.”

Changes an item that already exists, so a step elsewhere can keep Maestro in line with what really happened.

When to use it
when the outcome of another tool should be written back onto the matching item.
Watch out
it needs the Process Id and the Item ID, and with no search step the ID must come from an earlier step.
When it breaks

When a Maestro Zap breaks

Zapier attaches no help article to Maestro, so the failures worth knowing come from how Zaps behave in general, and from the way Maestro ties every step to a process.

Four situations explain most surprises. None is unique to Maestro, but each one shows up in a process Zap in its own way. See our Zapier troubleshooting page.

  • Items already in the status are ignored

    A Zap only reacts to what happens after it is switched on. Items that were already in place are not picked up; moving that backlog is a separate job.

  • Update Item sets the Zap off again

    If Update Item writes into the process that Updated Item or Updated Field watches, each write starts the Zap again, over and over, and the task count drains fast.

  • A bulk import is held back

    When a trigger suddenly returns a huge batch, after a bulk import or a migration, Zapier's flood protection can hold those items back.

  • The same change does not run twice

    On a polling trigger, Zapier remembers what it has already seen, so one item update does not start the Zap a second time.
Need help

Need help automating Maestro with Zapier?

A person reads every message.

FAQ

Maestro Zapier integration: your questions

01Is the Maestro Zapier integration free?
Yes, for simple Zaps. Maestro is not a premium app on Zapier, so it works on the free plan, which gives 100 tasks a month and Zaps of two steps: one trigger and one action. An item reaching a status and a single message to your team fits inside that. Add a filter, a second action or a search from another app and the Zap becomes multi-step, which needs a paid plan. You also need your own Maestro account.
02How many tasks does a Maestro Zap use?
One task per action that completes successfully. The three Maestro triggers never cost anything, however often Zapier checks them. In a Zap where an item in a given status goes through a filter and then a team message, only the message is an action: a passing run uses one task, and a run the filter stops uses none. A Create Item or Update Item that fails is not counted. A few apps and actions take more than one task, so check what you add.
03Do Maestro triggers work in real time?
No. All three Maestro triggers work by polling: Zapier goes to Maestro at a fixed interval and keeps only what it has not seen before. That interval depends on your plan: 15 minutes on Free, 2 on Professional, 1 on Team and Enterprise. On paid plans you can also run a check by hand from the editor. The type is set by the app and cannot be changed from the editor.
04What does it take to connect Maestro to Zapier?
A Maestro account that already exists and a Zapier account. On the Apps page, click + Add connection, search for Maestro, confirm with Add connection, then sign in to Maestro in the tab that opens and grant Zapier access. The connection is then reused by every trigger and action. Since every operation works inside a process, the account also needs read or write access on any process you do not own yourself.
05Why does Update Item ask for an Item ID?
Because it changes one precise item, and Maestro on Zapier offers no search step to find it by name. The Item ID has to come from an earlier step, typically a Maestro trigger that already carries the item, alongside the Process Id. If the Zap starts from another app that knows nothing about Maestro IDs, Update Item has nothing to map. In that case, Create Item is often the step that fits, since it only asks for the process.
06What if the Maestro operation you need is not on Zapier?
On Zapier, Maestro offers three triggers and two actions, and no search. Deleting an item or finding one by name, for instance, is not on the list, and the list cannot be extended from the editor: it is what the app publishes. The practical options are to rebuild the scenario around the operations that exist, to hand the missing part to another app the Zap already uses, or to compare with another automation platform.
07Zapier, Make or n8n for Maestro?
Decide on criteria, not on a ranking. First, coverage: on Zapier, Maestro has three polling triggers and two actions, so check what each platform exposes before you commit. Second, cost logic: Zapier bills one task per successful action, and any Zap with a filter or a second action needs a paid plan. Third, timing: on Zapier, how fast a change arrives depends on the polling interval of your plan. Weigh those three against your volume and your team.
Same platform

Other docs you might need on this stack.

Browse all integrations