Resources · Zapier integration

Mirro Zapier integrationAutomate Mirro with Zapier.

The Mirro Zapier integration gives you 4 triggers and 0 actions. Feedback, feedback requests, kudos and objective updates in Mirro can start a Zap, and the rest of the work then happens in the other tools you send them to.

See the 4 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Mirro Zapier integration does for you

The Mirro Zapier integration lets what happens in Mirro, your performance management tool, travel to your other apps without anyone copying it. Four events can start an automation: a feedback, a feedback request, a new kudos and an objective update. Mirro only sends; nothing comes back into it through Zapier.

Three results you can build. Recognition people actually see: New Kudos starts the Zap and a message lands in your team chat, so a thank-you does not stay inside one tool. A feedback log you control: Feedback starts the Zap and each feedback given to you becomes a row in your own spreadsheet, ready for your next review. Objectives that do not drift out of view: Objective Update fires when an objective changes, and the Zap passes the update to the channel or inbox where the team already works.

What Zapier does not do for Mirro. There is no action: a Zap cannot create a kudos, write a feedback or update an objective in Mirro. There is no search step either, so nothing can be looked up in Mirro mid-Zap. All four triggers are polling triggers, which means Zapier checks for new items on a timer set by your plan, so an event waits for the next check. And a Zap never picks up what happened before it was switched on.

Comparing options first? Open our Make vs Zapier page before you build.

Vocabulary

Zapier words, in one minute

Seven terms to know before you read on. Each one gets a single line.

Zap
Your automation on Zapier: one trigger, then one or more actions that run every time the trigger event happens.
Trigger
The event in an app that starts the Zap. With Mirro, it is always a feedback, a request, a kudos or an objective update.
Action
What the Zap does once it has started, in another app: the step that sends, writes or creates something for you.
Task
The unit Zapier bills: one action your Zap completes successfully. The allowance on your plan is a count of those.
Polling trigger
A trigger Zapier checks on a timer: it asks the app for new items at a fixed interval and keeps only what is new.
Instant trigger
A trigger the app reports itself, the moment the event happens. None of Mirro's four triggers works this way.
Filter
A step that lets the Zap carry on only when what arrived meets your condition, and stops it otherwise.
Cost

What a Mirro Zap costs

Zapier bills actions, never triggers. Mirro is not a premium app, so it works from the free plan.

  • Mirro trigger0 tasks
  • Successful action elsewhere1 task each
  • Free plan100 tasks a month, two-step Zaps
  • Premium appNo

Since Mirro only has triggers, the Mirro part of a Zap costs nothing: the trigger never uses a task, and neither does Zapier checking for new items, however often it looks. What counts is the action in the other app, one task each time it succeeds. A failed action is not counted. The free plan gives 100 tasks a month and unlimited Zaps, each limited to two steps: one trigger, one action. A second action or a filter makes it a multi-step Zap, which needs a paid plan. The grid below sets how often Zapier checks Mirro's four polling triggers.

Connect

Connect Mirro to Zapier in 3 steps

  1. 01

    Start the connection

    On Zapier, open the Apps page of your account and click + Add connection. Search for Mirro in the dialog and pick it. You need a Mirro account first.

  2. 02

    Sign in to Mirro

    Click Add connection and sign in to Mirro in the tab that opens. You also need read or write access on anything you do not own yourself and want the Zap to touch.

  3. 03

    Grant access

    Allow Zapier to reach the account. The connection is then reused by every Mirro trigger you set up, in this Zap and the next ones, so you only do this once.

First Zap

Your first Mirro Zap: share kudos with the team

GoalEvery new kudos in Mirro is posted in your team chat, with a filter that keeps only the ones you choose.

  1. 01

    Pick the trigger

    Create a Zap, pick Mirro as the app that starts it and New Kudos as the event. Then choose the Mirro connection you made earlier.

  2. 02

    Test it

    Run the test. Zapier brings back the three most recent kudos of the account, so you work on a real one. Read what came back before going further.

  3. 03

    Add the filter

    Add a Filter from the plus icon and set its three boxes: the field to look at, the rule, the value. A filter makes the Zap multi-step, so it needs a paid plan.

  4. 04

    Add the message

    Add your chat tool and its message action. Build the text from the kudos fields the trigger test showed. On the free plan, drop the filter and keep these two steps.

  5. 05

    Publish

    Test the message once, then publish the Zap to switch it on. New kudos reach the chat after Zapier's next check, at your plan's interval.

Triggers

The 4 Mirro triggers

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

1

Feedback

Polling trigger

In Zapier“Triggers when someone offers you a feedback.”

Starts the Zap when someone gives you a feedback in Mirro. It is the event to use when what people tell you should not stay buried in one tool, and you want a copy somewhere you already look every day, or a record you keep for yourself.

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
you keep your own spreadsheet of the feedback you receive, to reread before your next review, and you want each new one added as a row.
Watch out
check at test which fields come through before you decide what to copy, and feedback given before you publish is never picked up.
2

Feedback Request

Polling trigger

In Zapier“Triggers when a feedback request is submitted.”

Fires when a feedback request is submitted in Mirro. Where the Feedback trigger is about answers, this one is about the ask itself, so a Zap can act on it while there is still time to answer.

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
a request should turn into a to-do in the task tool you actually work from, so it does not sit unread in Mirro while you are elsewhere.
Watch out
the request reaches the Zap at the next check, not the moment it is submitted; check at test what it carries before you map anything.
3

New Kudos

Polling trigger

In Zapier“Triggers when a new Kudos is received.”

Each new kudos received in Mirro starts the Zap. Recognition tends to work best when other people see it too, and this is the trigger that takes it out of Mirro and into a channel the whole team reads.

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
posting kudos in your team chat, or adding them to a shared document of wins that the team rereads together.
Watch out
Zapier keeps track of what it has already seen on this trigger, so the same kudos does not start the Zap twice.
4

Objective Update

Polling trigger

In Zapier“Triggers when an objective is updated. Sends a message to contributors and owner.”

An objective updated in Mirro is what sets this one off. Objectives move slowly and get forgotten easily, so carrying each update to where people already talk keeps them in view without anyone opening Mirro.

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
you want every change on your objectives copied to a channel or an email, to follow progress from there.
Watch out
check at test what an update brings back, so the message you build does not miss the part that changed.
When it breaks

When a Mirro Zap breaks

Zapier attaches no help article to Mirro and no limit specific to the app is documented. The surprises below are the ones every polling-based Zap can run into.

Four cases to know before you publish. For the day a run fails anyway, keep our Zapier troubleshooting page at hand.

  • Old feedback never arrives

    A Zap only reacts to what happens after it is switched on. Feedback, kudos and objective updates already in Mirro are not picked up; moving them is a separate job.

  • Items show up later than expected

    All four Mirro triggers are polling triggers. A new item waits for Zapier's next check, every 15 minutes on the free plan, faster on paid plans.

  • The same item does not repeat

    Zapier keeps track of what it has already seen on a polling trigger, so the same item does not start the Zap twice.

  • A big batch is held back

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

Need help automating Mirro with Zapier?

A person reads every message.

FAQ

Mirro Zapier integration: common questions

01Is the Mirro Zapier integration free?
Yes. Mirro is not a premium app, so its triggers work on Zapier's free plan. That plan gives 100 tasks a month and unlimited Zaps, each built from two steps: one trigger and one action. A Zap that posts each new kudos in your team chat fits in that. Add a filter to keep only some kudos, or a second action, and it becomes a multi-step Zap, which needs a paid plan. Since Mirro has no actions, the action in your Zap always belongs to another app.
02How many tasks does a Mirro Zap use?
Only the actions count, one task each time an action succeeds. The Mirro trigger costs nothing, and Zapier checking Mirro for new items costs nothing either, however often it looks. So a Zap that turns each feedback into a spreadsheet row costs one task per feedback. If the same Zap also sends an email, that is two tasks per feedback. An action that fails is not counted against your plan.
03Does Mirro trigger Zaps in real time?
No. All four Mirro triggers are polling triggers: Zapier goes to Mirro at regular intervals and picks up what is new. How often depends on the plan: every 15 minutes on Free, every 2 minutes on Professional, every minute on Team and Enterprise. So a kudos given in Mirro reaches your chat after the next check. On a paid plan, how often the trigger checks can be changed, and a check can also be run by hand from the editor.
04What does it take to connect Mirro to Zapier?
A Mirro account, plus read or write access on anything you do not own yourself and want the Zap to touch. On Zapier, open the Apps page, click + Add connection, search for Mirro and pick it, click Add connection, sign in on the tab that opens and grant access. Before testing a trigger, make sure the account already has at least one matching item, since the test brings back the three most recent ones.
05Can a Zap give kudos or write feedback in Mirro?
No. The Mirro integration on Zapier has four triggers and no action, so a Zap can read what happens in Mirro but cannot write anything back. Kudos, feedback and objective changes are made in Mirro itself. What a Zap can do is carry those events elsewhere: to your chat, your inbox, a spreadsheet or a task tool. If your idea needs Mirro on the receiving end, Zapier cannot do that part today.
06What if a Mirro operation is missing from Zapier?
Open Mirro's app page on Zapier: it shows the current list of what the integration offers, four triggers today. If the event you want is not there, the integration does not provide it. Look at whether one of the four gets close enough: Objective Update, for example, covers changes on objectives. Otherwise, that part of the process stays manual in Mirro, and the Zap handles what the four triggers can catch.
07Zapier, Make or n8n for Mirro?
Use criteria, not a ranking. First, coverage: on Zapier, Mirro offers four triggers and no action; check whether the other tool lists Mirro at all. Second, delay: Mirro's triggers are polling triggers, so on Zapier the interval of your plan sets how fast events arrive, 15 minutes on the free plan. Third, billing: Zapier counts one task per successful action, and with Mirro every action is in another app. Fourth, the tool your team already maintains.
Same platform

Other docs you might need on this stack.

Browse all integrations