Miro Zapier integrationAutomate Miro with Zapier.
The Miro Zapier integration offers 4 actions and no trigger. Miro can only be the receiving end: another app starts the Zap, then Zapier creates, copies or fills a board for you. Here is what each action does, what it costs and where it stops.
Verified Trustpilot reviews · AI, automation & growth agency
What the Miro Zapier integration does for you
It connects your Miro account to Zapier so that an event in another tool (a new deal, a form answer, a signed contract) can create a board, copy a template board or add a card in Miro, without anyone opening the whiteboard. It works in one direction only: into Miro.
Three things people use it for.
A board ready before the kickoff call. Copy Board duplicates a template board, so every new client or project starts from the same workshop canvas instead of a blank one.
Empty boards on demand. Create Board opens a new board when a request lands elsewhere, which keeps naming and creation out of someone's to-do list.
Cards that land on the right board. Create Card adds a card to a board you pick, for instance one card per idea submitted through a form.
What it does not do matters just as much. Miro has no trigger here, so nothing that happens on a board can start a Zap: a new sticky note, a comment or a finished workshop stays invisible to Zapier. There is no search either, so a Zap cannot look up an existing board by name. The fourth action, API Request (Beta), is the only step that goes beyond the three others, and it is a technical one.
If you compare tools, the same app has its own Miro Make integration page on this site.
Zapier vocabulary in one minute
Seven Zapier words come back on this page. Here they are, once, in plain English.
- Zap
- An automation on Zapier: one trigger, then one or more actions that run every time the trigger event happens.
- Trigger
- The event that starts the Zap. Miro has none on Zapier, so with Miro the trigger always comes from another app.
- Action
- What the Zap does once it has started: the step that creates, copies or sends something for you, here inside Miro.
- Task
- The unit Zapier bills: one action your Zap completed successfully. The number on your plan is a count of those.
- Polling vs instant
- A polling trigger is checked by Zapier on a timer. An instant one is pushed by the app itself as soon as the event happens.
- Filter
- A step that lets the Zap continue only when what arrived meets the condition you set, and stops it the rest of the time.
- Connection
- Your Miro account linked to Zapier once, then reused by every Miro step in every Zap you build afterwards.
What a Miro Zap really costs
Miro is not a premium app on Zapier, so the free plan can use it. Since every Miro step is an action, every run costs at least one task.
- Premium appNo, available on the free plan
- Free plan100 tasks a month, two-step Zaps
- Miro triggersNone, the Zap starts in another app
- Failed actionNot counted
The trigger, which here comes from another app, never costs a task, and neither do Zapier's checks for new items. Each Miro action that succeeds counts once: copy a board and add a card in the same run, and that is two tasks. An action that fails is not counted. The free plan gives 100 tasks a month, unlimited Zaps and a check every 15 minutes on polling triggers, but only two-step Zaps: one trigger, one action. A filter or a second Miro action makes the Zap multi-step, and that needs a paid plan.
Connect your Miro account in three steps
- 01
Open a new connection
Go to the Apps page of your Zapier account and click + Add connection. In the dialog that opens, type Miro in the search box and pick it from the results.
- 02
Sign in to Miro
Click Add connection. A new tab opens on Miro's sign-in page. Log in with the account that owns, or can edit, the boards your Zap will copy or write to.
- 03
Grant access
Allow Zapier to access that Miro account. The connection then shows on your Apps page and every Miro step reuses it. For boards you do not own, you need write access there too.
Your first Zap: a template board for every new deal
GoalEach time a deal reaches the stage you choose in your CRM, Miro gets a fresh copy of your discovery workshop board.
- 01
Create the Zap
Start a new Zap. Since Miro has no trigger, pick your CRM as the app that starts it and the event that matches a new deal. Connect that account.
- 02
Test the trigger
Run the trigger test. Zapier brings back the three most recent items from your CRM account, so you can map a real deal in the next steps.
- 03
Add a filter
Add a Filter from the plus icon and set the field, the rule and the value to keep only the deals you care about. This makes the Zap multi-step, so it needs a paid plan.
- 04
Add Copy Board
Add Miro with Copy Board, then choose your discovery template as the Original Board. That field is required, so the template has to exist first.
- 05
Test, then publish
Test the action and open Miro to check the new board. Then click Publish. Deals created before that moment will not get a board.
The 4 Miro actions
Miro gives you 4 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Copy Board
ActionIn Zapier“Copies an existing board”
Duplicates an existing board. You point it at the original board, and Miro gets a copy of it, so the structure you designed once is reused.
Create Board
ActionIn Zapier“Creates a board”
Opens a new, empty board in your Miro account, without needing a template. It is the lightest way to get a workspace ready when something happens elsewhere.
Create Card
ActionIn Zapier“Creates a new card on a board”
Adds a card to a board you choose. It is how information collected in another tool ends up on the whiteboard, where the team actually looks.
API Request (Beta)
ActionIn Zapier“This is an advanced action which makes a raw HTTP request that includes this integration's authentication.”
The escape hatch: a raw request to Miro's service that reuses your Miro connection, for anything the three other actions cannot do.
When a Miro Zap breaks
Zapier links no help article to Miro and lists no Miro-specific limit. What breaks comes from how Zapier works in general.
A Miro Zap depends on the app that starts it. Most surprises are about what the trigger sees, not about Miro itself. If a run fails and you can't tell why, the Zapier troubleshooting guide goes through the usual checks, and the Zapier review puts these limits in context.
Older items never get a board
A Zap only reacts to what happens after you publish it. Deals or answers that existed before get nothing; creating their boards is a separate job.A bulk import holds the Zap back
If the starting app suddenly returns a huge batch, after an import or a migration, Zapier's flood protection can hold those runs back.The same item never runs twice
On a polling trigger, Zapier remembers what it has already seen. The same deal will not start the Zap twice, so it does not get two boards.The filter switches the plan
Adding a filter or a second Miro action turns the Zap multi-step, and a multi-step Zap needs a paid plan, not the free one.
Need help automating Miro with Zapier?
A person reads every message.
