Operator
← All integrations
Figma logo+Miro logo

Connect Figma to Miro

Automate Figma and Miro with AI

Workshops in Miro produce ideas that still need a polished spec in Figma. Your Operator agent on OpenClaw exports sticky themes from a Miro board into a structured Figma page, links each frame back to the source stickies, and updates Miro when a Figma concept moves to approved. Ask for open workshop items not yet specced and it compares both boards.

It reaches both apps directly or through connectors like Composio MCP and Pipedream MCP, which handle the sign in and token refresh, so there is no Zap to build and no API keys to paste.

What your agent can do with Figma and Miro

What your agent does in Figma

  • Add a comment to a file

    Posts a new comment to a Figma file or branch, optionally replying to an existing root comment (replies cannot be nested); `region_height` and `region_width` in `client_meta` must be positive if defining a comment region.

  • Add a reaction to a comment

    Posts a specified emoji reaction to an existing comment in a Figma file or branch, requiring valid file_key and comment_id.

  • Create a webhook

    Creates a Figma webhook to receive POST notifications when specific events occur. Webhooks can monitor events at three scopes: - Team level: monitors all files in a team (requires team admin permissions) - Project level: monitors all fil...

  • Create dev resources

    Creates and attaches multiple uniquely-URLed development resources to specified Figma nodes, up to 10 per node.

  • Create, modify, or delete variables

    Manages variables, collections, modes, and their values in a Figma file via batch create/update/delete operations; use temporary IDs to link new related items in one request and ensure `variableModeValues` match the target variable's `re...

  • Delete a comment

    Deletes a specific comment from a Figma file or branch, provided the authenticated user is the original author of the comment.

All 52 Figma actions →

What your agent does in Miro

  • Attach Tag To Item

    Tool to attach an existing tag to a specific item on a Miro board. Use when you need to associate a tag with an item after confirming the board, item, and tag IDs. Note that card and sticky note items can have up to 8 tags.

  • Create App Card Item

    Tool to add an app card item to a board. Use when you need to push a rich preview card with custom fields into a Miro board. Returns the created card; the card ID is nested under data.id in the response, not at the top level. Burst write...

  • Create Board

    Tool to create a new board. Use when you need to set up a board with a specific name, description, and policies. Example: "Create a new board named Project Plan". If workspace board quota is reached, returns HTTP 400; use MIRO_GET_BOARDS...

  • Create Card Item

    Tool to create a card item on a Miro board. Use when you need to add task cards with titles, descriptions, due dates, and assignees.

  • Create Connector

    Tool to create a connector (edge/arrow) that links two existing board items. Use after creating or locating the two endpoint items (shapes/cards/stickies) to establish visual relationships in flowcharts and diagrams. Both start and end i...

  • Create Document Item

    Tool to create a document item on a Miro board by providing a URL to the document. Use when you need to attach a document (PDF, DOC, etc.) to a board from a publicly accessible URL.

All 73 Miro actions →

How it works

Tell the agent what you want to happen between Figma and Miro, for example to watch one and act in the other, or to keep the two in step. It reads what it needs from Figma, works out what to do, and runs the matching action in Miro without you mapping a single field.

You can have it run once, on a schedule, or whenever something changes. Ask it for a status any time and it reads the latest from both apps back to you in the same chat.

Common questions about Figma and Miro

How do I connect Figma and Miro to Operator?
You authorize Figma and Miro once each from your Operator dashboard. Operator holds both connections and refreshes the access tokens for you, so your agent keeps working across them without you signing in again.
What can my agent do across Figma and Miro?
Tell it the job and it moves between Figma and Miro as one task, choosing which actions to run on each side. There is nothing to map and no trigger to configure; you give instructions the way you would to a person.
Can my agent keep Figma and Miro in sync?
Yes. It can watch Figma and act in Miro, or keep both in step, reading from one and running the matching update in the other. This runs on demand when you ask or on a schedule you set.
Do I need to build a workflow or write code?
No. There is no workflow to build, no fields to map, and no API keys to paste. Operator manages both connections, and you give the agent instructions in plain language.

Figma and Miro integrations

Put your agent on Figma and Miro

Sign in, connect both apps, and hand your agent the work. The same setup reaches every app in the catalog. Your first week is free.

Try for free