Operator
← All integrations
Figma logo+Mural logo

Connect Figma to Mural

Automate Figma and Mural with AI

Facilitated sessions in Mural capture decisions that design work in Figma should reflect. Operator.io runs your OpenClaw agent across both so action items from a Mural mural become Figma tasks with owners, and frame status writes back to the mural when review finishes. Tell it to sync the login flow workshop and it lists Mural decisions beside the matching Figma frames.

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 Mural

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 Mural

  • MURAL Authorization Request

    Tool to initiate the OAuth 2.0 authorization process. Use when you need to redirect a user to Mural to obtain an authorization code.

  • Create sticky note

    Create one or more sticky note widgets on a mural. Each sticky note must be a properly structured object with required x and y coordinates. Pass the 'stickies' parameter as a direct array of objects - NOT strings, NOT nested objects. Exa...

  • Get current user

    Tool to retrieve information about the currently authenticated user. Use when you need current user details after authentication.

  • Get files for a mural

    Tool to retrieve a list of file widgets in a mural. Use after confirming the mural ID when listing file attachments.

  • Get Mural Widgets

    Tool to retrieve all widgets within a specified mural. Widgets include sticky notes, text boxes, shapes, images, areas, arrows, icons, files, and comments. Use this after obtaining a valid mural ID from workspace murals or other mural-re...

  • Get room by ID

    Tool to retrieve information about a specific room by its ID. Use when you need details about a particular room that the authenticated user has read access to.

All 22 Mural actions →

How it works

Tell the agent what you want to happen between Figma and Mural, 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 Mural 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 Mural

How do I connect Figma and Mural to Operator?
You authorize Figma and Mural 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 Mural?
Tell it the job and it moves between Figma and Mural 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 Mural in sync?
Yes. It can watch Figma and act in Mural, 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 Mural integrations

Put your agent on Figma and Mural

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