--- title: "Miro Integration" description: "Connect AI agents to Miro boards. Agents spin up boards for projects and workshops, turn incoming ideas and tasks into sticky notes and cards, browse board items for syncing, and manage sharing and member access." url: https://flowrunner.ai/integrations/miro date_modified: 2026-08-01T02:40:32-07:00 --- # Miro [Productivity](https://flowrunner.ai/integrations/category/project-management-productivity) Connect AI agents to Miro boards. Agents spin up boards for projects and workshops, turn incoming ideas and tasks into sticky notes and cards, browse board items for syncing, and manage sharing and member access. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 10 actions · API key · available [Miro website](https://miro.com/) · [Platform Documentation](https://developers.miro.com/) · Capability data verified 2026-07-28 1. A new project kicks off in the project tracker with a team roster attached 2. Create Board spins up the project board from the naming convention, assigned to the right team with edit access configured 3. Create Card drops the project's initial milestones onto the board, positioned as a starting lane 4. Share Board invites the roster by email at editor level, and the client contact at commenter level 5. List Board Members confirms access matches the roster, nobody missing, nobody extra 6. The project lead reviews the external shares before invitations go beyond the org 7. The board's view link posts to the project channel ## What This Integration Enables A Miro board is where teams think together, and the thinking suffers when the board has to be assembled by hand every time. FlowRunner treats boards as workflow outputs: agents create them per project or workshop, seed them with cards and sticky notes from the systems where work originates, share them at the right permission levels, and read items back out so decisions made on the wall reach the systems that execute them. The loop runs both directions, which is what separates a synced board from a screenshot. - Spin up boards per project, kickoff, or workshop, named, teamed, and shared before anyone asks - Turn form submissions, chat ideas, and backlog rows into sticky notes and cards positioned on the board - Read items off a board with List Items to sync workshop outcomes into trackers and sheets - Audit membership with List Board Members and gate external shares and board deletion with a person ### Without FlowRunner **Board setup is kickoff overhead**: The first twenty minutes of every workshop is someone building the board the last workshop already had **Ideas die in the intake tool**: Form submissions and chat suggestions pile up in queues nobody triages visually **Sharing by accumulation**: Boards collect members over months, and no one knows which client contact can still see the roadmap ### With FlowRunner **Boards arrive ready**: Each project or workshop gets a board created, seeded with cards, and shared before the meeting starts **Intake lands on the wall**: New ideas and requests become sticky notes and cards on the triage board the hour they arrive **Access is audited, not assumed**: Member lists export on a schedule, and external shares pass a human check before the invite sends ## Use Case Scenarios ### The retro board that builds itself Friday at noon, an agent creates the retro board from the standing template, then pulls the week's shipped items and incidents from the tracker, dropping each as a card in the right column. Share Board invites the squad at editor level, and the view link posts to [Slack](https://flowrunner.ai/integrations/slack). The retro starts with the week already on the wall, and after it ends, List Items reads the action-item stickies back out and files them in the tracker. ### The idea funnel with a visible wall Product feedback arrives through a [Typeform](https://flowrunner.ai/integrations/typeform) form. Each submission becomes a Create Card call onto the triage board, title from the summary field, description carrying the full response. The product team clusters the cards spatially in their weekly review, and the agent syncs the surviving clusters into the backlog. The intake queue nobody read becomes a wall everyone argues in front of, which is the point. ### The access audit that runs monthly instead of never An agent walks List Boards for the workspace, calls List Board Members on each, and writes the full access map to [Google Sheets](https://flowrunner.ai/integrations/google-sheets): board, member, role, external or internal. Boards with external editors get flagged to the ops channel. The audit that used to happen after an awkward client discovery now happens on the first of the month, and offboarding a contractor means checking one sheet instead of opening forty boards. ## Human-in-Loop Highlight Delete Board removes the board and every item on it, and the API offers no undo. What makes this worse than most deletes is what a Miro board uniquely holds: the spatial arrangement itself is the content. Sticky clusters, arrows, and positioning encode a workshop's reasoning in a way no export reconstructs, so a board deleted by an overeager cleanup workflow is not restorable from a backup of its text. FlowRunner treats it accordingly. A retention agent may nominate boards, inactive for months, zero members outside the creator, but the deletion itself waits: the agent posts the board name, view link, member list, and item count, and a person who can open the link and look confirms. Share Board gets a lighter version of the same gate when the invite goes outside the org, because an external editor on the wrong board is a disclosure, not a permission bug. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via preferred channel Human decides Agent resumes with decision ## Agent Capabilities 10 actions ### Boards 4 - **List Boards** Retrieves boards the authenticated user can access, newest first, with team filtering and limit and offset paging. The enumeration step behind audits and syncs. - **Get Board** Retrieves a single board's full details: name, description, sharing policy, owner, team, view link, and timestamps. The inspection step before adding items or changing access. - **Create Board** Creates a board with a name and optional description, assignable to a team with sharing access set at creation: private, view, comment, or edit. Returns the board ID and view link. - **Delete Board** Permanently deletes a board and every item on it, with no undo through the API. The operation this page's human gate exists for. ### Items 4 - **List Items** Retrieves items on a board, filterable by a single type such as sticky notes, cards, shapes, text, or images, cursor-paginated with content, position, geometry, and style. The read that syncs a wall back into structured systems. - **Get Item** Retrieves one item by ID with its type, content, position, geometry, and style, for any item type. - **Create Sticky Note** Adds a sticky note with text, position in board coordinates relative to center, and optional fill color and alignment. The unit of automated intake onto a triage or workshop board. - **Create Card** Adds a card with a title and optional description at a board position. The representation of choice for tasks and agenda items flowing in from other systems. ### Access 2 - **List Board Members** Retrieves a board's members with their roles: viewer, commenter, editor, coowner, or owner. Paginated; the backbone of access audits and the pre-check before changing access. - **Share Board** Shares a board by email at a chosen role, sending invitation emails. External invitations pass through this page's review gate before they send. ## Frequently Asked Questions ### What can FlowRunner do with Miro? FlowRunner agents can run List Boards, Get Board, and Create Board in Miro, plus 7 more actions. ### Does connecting Miro to FlowRunner require OAuth? No. Miro connects to FlowRunner with an API key, no OAuth flow required. ### Can Miro trigger a FlowRunner workflow automatically? Miro doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Miro?** This integration exposes Miro to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/miro. Site index: https://flowrunner.ai/llms.txt