Resources · Make integration

Miro Make integrationAutomate Miro with Make.

Can Make build and update your Miro boards while you work elsewhere? The Miro Make integration gives you 11 modules: 2 triggers that watch boards and items, 7 actions and 2 searches. This guide is for teams that live in Miro, and it walks you from the connection to a working scenario.

Try the Miro integration on MakeSee the 11 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Miro Make integration do for you?

The Miro Make integration links your Miro account to Make so that boards and the items on them can start or receive an automation. In Make, that automation is called a scenario: a chain of modules, where each module is one brick, like a trigger, an action or a search. You assemble it visually, without writing code.

A board ready for every new client. A new deal lands in your CRM, and Create a Board opens a fresh board for it, then Create a Shape Item drops a first shape on it with the client's name. If you prefer a template, Copy a Board duplicates a board your team already polished.

A log of what changed on a workshop board. Watch Items picks up items created or modified on one specific board, and Make can pass each one to a spreadsheet or a chat tool. Your facilitator reviews the output instead of scrolling the canvas.

An inventory of your boards. List Boards returns every board the connection can see, and Get a Board fetches the details of one. Useful when you want a single place that names each board and what it is for.

Know the edges before you start. The listed modules create, copy, read and update, but none of them deletes a board. For anything the list does not cover, Make an API Call reaches the rest of the Miro API with the same connection. Both Miro triggers are scheduled, so Make checks for changes on the scenario's schedule rather than hearing about them the moment they happen.

New to the tool? The Make training covers the editor from the ground up, and if you are still choosing a platform, n8n vs Make sets the two side by side. For plan details, see Make pricing.

Connect

How do you connect Miro to Make?

  1. 01

    Prepare an app in Miro

    You need a Miro developer team account and an app created in Miro. In your profile settings, open Apps, pick your app under Created apps, add the callback URI below, then copy the Client ID and the Client secret.

  2. 02

    Grab your Team ID

    Still in Miro, go to User and Team Management, click Teams, then click your team name. The Team ID sits in the page URL: copy it from there and keep it next to the two other values.

  3. 03

    Create the connection in Make

    Add any Miro module to your scenario and click Create a connection. A connection is your Miro account linked to Make once, then reused by every Miro module. Give it a name if you like in Connection name, paste the credentials and confirm.

First scenario

Your first scenario: a Miro board for each new client

GoalWhen a new client shows up in another app, Make creates a Miro board for them and places a first shape on it.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. This first module is the app where your new clients appear, such as your CRM or a form tool.

  2. 02

    Set the starting module

    Search that app, pick its module that watches new records and connect the account. Every new client it finds becomes a bundle: one item that flows to the next module.

  3. 03

    Add Create a Board

    Click the + on the right, search Miro and pick Create a Board. Connect Miro as shown above, then fill the fields by mapping the client data coming from the first module.

  4. 04

    Add Create a Shape Item

    Add Create a Shape Item after it. Map the board created one step earlier, so the shape lands on the new board and not on an old one, then map the client details you want to see on it.

  5. 05

    Test with Run once

    Click Run once and create a test client in your source app. Open each module's bubble to read the bundles it received, then check in Miro that the board and its shape appeared.

  6. 06

    Schedule and switch on

    Click the clock on the first module to set the schedule, every 15 minutes by default, and switch the scenario on. From then on, each run can open boards without you touching Miro.

Triggers

What can start a Miro scenario?

2 modules start a scenario when something happens in Miro. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Miro as soon as it happens.

Miro1Watch Boards

Watch Boards

Scheduled trigger

In Make“Triggers when a board is created or modified.”

Watch Boards starts your scenario whenever a board is created or modified in your Miro team, and hands the board to the next module as a bundle. Pick it to react to the boards themselves, not to what sits on them.

How it fires
it is a scheduled trigger, so Make checks Miro on the scenario's schedule, every 15 minutes by default, and picks up the boards changed since the previous check.
When to use it
you want a spreadsheet or a channel to hear about each new workshop board, so nobody has to announce it by hand.
Watch out
modified boards count too, so a board created or copied by another scenario shows up here as well.
Miro2Watch Items

Watch Items

Scheduled trigger

In Make“Triggers when a item is created or modified on the specific board.”

Watch Items follows one specific board and fires when an item on it is created or modified, such as a shape added during a session. You get each item as its own bundle, ready to be sent somewhere more structured than a canvas.

How it fires
scheduled as well: Make checks the board on the scenario's schedule, not at the instant a teammate edits it.
When to use it
during a retrospective or a brainstorm, when each idea added to the board should also land in your task tool or your notes.
Watch out
it watches a single board, so a second board needs a second scenario and not the whole team space.
Modules

What else can Make do in Miro?

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

Miro1

Copy a Board

Action

In Make“Creates new board from existing one.”

Copy a Board takes an existing board and produces a new one from it, so a layout your team already refined can be reused instead of rebuilt from scratch.

When to use it
a kickoff template, a sprint planning canvas or an onboarding map that every new project should start from.
Watch out
the copy is a new board, so a Watch Boards trigger running elsewhere will see it too; keep the two apart to avoid a loop.
Miro2

Create a Board

Action

In Make“Creates a new board.”

Create a Board opens a blank board in Miro from inside the scenario, and returns it so the following modules can fill it or pass its details on.

When to use it
pick it over Copy a Board when you want a clean canvas rather than a template, for example a board per support incident.
Watch out
each run creates a board, so test with Run once before you switch the schedule on, or your team space fills up fast.
Miro3

Create a Shape Item

Action

In Make“Creates an item.”

Create a Shape Item puts a shape on a board you choose, which is how a scenario writes visible content into Miro rather than just managing boards.

When to use it
a form answer, a new lead or a ticket title should appear on a planning board as soon as the scenario runs.
Watch out
map the board carefully; if the board comes from an earlier module, point to that output and not to a fixed board picked while testing.
Miro4

Get a Board

Action

In Make“Retrieves information about a specific board.”

Get a Board fetches the details of one board you already know, so later modules can reuse what Miro stores about it without searching through the whole team.

When to use it
right after Watch Boards, when the trigger tells you which board changed and you need its full information before posting a summary.
Watch out
it needs one precise board; if you only have a vague idea of which one, start with List Boards instead.
Miro5

Get an Item

Action

In Make“Retrieves information for a specific item on a board.”

Get an Item reads a single item on a board and returns its information, which helps when another module only gave you a reference and you need the rest.

When to use it
after Watch Items, to pull the full information of the item that just changed before copying it into your task list.
Watch out
the item lives on a specific board, so both the board and the item have to be mapped from the same earlier bundle.
Miro6

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call lets the scenario reach any endpoint of the Miro API while reusing the connection you already created, so you are not stuck when a listed module is missing.

When to use it
the task you need, such as removing a board, is not among the 11 modules on this page.
Watch out
you write the request yourself, so keep the Miro API documentation open and test the call with Run once before relying on it.
Miro7

Update a Board

Action

In Make“Updates an existing board.”

Update a Board changes an existing board, so its details stay in step with the project it belongs to without anyone opening Miro to edit them.

When to use it
a deal changes stage in your CRM, or a project gets renamed, and the matching board should follow.
Watch out
pair it carefully with Watch Boards; an update is a modification, which that trigger will pick up on its next check.
Miro8

List Boards

Search

In Make“Retrieves a list of all boards.”

List Boards returns every board the connection can reach, one bundle per board, which gives you a full picture of your Miro space in a single step.

When to use it
an audit sheet of all boards, or the first step before picking the right board to update or copy.
Watch out
like any search, it can return zero, one or many bundles, and each following module runs once per bundle, which counts operations on your plan.
Miro9

List Items

Search

In Make“Retrieves a list of items for specific board.”

List Items goes through one board and returns the items placed on it, so the content of a workshop can leave the canvas and be sorted elsewhere.

When to use it
at the end of a brainstorm, to export every note from the board into a sheet in one go instead of copying them one by one.
Watch out
a busy board sends many bundles, and every module after it runs for each one; point the scenario at a smaller board if you only need part of them.
Need help

Need help automating Miro with Make?

A person reads every message.

FAQ

Miro and Make: frequent questions

01Is the Miro Make integration free?
Yes, Miro is a standard app in Make, so you can use it from the Free plan. That plan has limits: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution per run at most, files up to 5 MB and 512 MB of data transfer. Every module run on one bundle counts as one operation on your plan. Paid plans, from Core to Enterprise, lower the minimum interval to 1 minute and remove the cap on active scenarios. The Miro subscription itself is a separate matter handled on Miro's side.
02What do you need to connect Miro to Make?
You need a Miro developer team account and an app created in Miro. From that app, you copy a Client ID and a Client secret, after adding the callback URI that Make expects. You also copy your Team ID from the URL of your team page, under User and Team Management. In Make, you add a Miro module, click Create a connection, optionally name it, then enter those credentials. The connection is then reused by every Miro module in your scenarios.
03Does the Miro trigger fire instantly in Make?
No. Watch Boards and Watch Items are both scheduled triggers, shown with a clock badge in the editor. Make checks Miro on the scenario's schedule, which is every 15 minutes by default for a new scenario. On the Free plan, 15 minutes is also the shortest interval allowed between two scheduled runs; paid plans can go down to 1 minute. If a change must be handled faster, a paid plan with a shorter schedule is the lever Make gives you.
04What if the Miro module you need is missing in Make?
Use Make an API Call. It is part of the 11 Miro modules and lets a scenario call any endpoint of the Miro API with the connection you already have. That covers what the listed modules leave out, for instance deleting a board, since the built-in modules create, copy, read and update but do not delete. You write the request yourself, so read the Miro API documentation and check the result with Run once before switching the scenario on.
05Should you use Make or n8n for Miro?
It depends on what you need and how you like to work. This page covers the Make side only: 11 Miro modules, including 2 scheduled triggers, 7 actions and 2 searches, plus Make an API Call for anything else, all built in a visual editor. Whether n8n offers the same Miro coverage is not covered here, so check its node before deciding. Compare on the modules your flow truly needs, not on a general impression, and test your first scenario on the tool you pick.
Same platform

Other docs you might need on this stack.

Browse all integrations