Operator
← All integrations
Figma logo+GitHub logo

Connect Figma to GitHub

Automate Figma and GitHub with AI

Design handoff breaks when specs live in Figma and implementation lives in GitHub with nothing linking them. Operator.io runs your OpenClaw agent across both so a frame comment can open a GitHub issue with the right labels, merged pull requests update the linked Figma file status, and anyone can ask which PR covers a component before review. Tell it to prep a release and it lists open issues beside the Figma pages still marked in progress.

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 GitHub

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 GitHub

  • Abort Repository Migration

    Tool to abort a repository migration that is queued or in progress. Use when you need to cancel an ongoing migration operation.

  • Accept a repository invitation

    Accepts a PENDING repository invitation that has been issued to the authenticated user.

  • Add app access restrictions

    Adds GitHub Apps to the list of apps allowed to push to a protected branch. The branch must already have protection rules with restrictions enabled. This endpoint only works for organization repositories, not personal repositories. Apps...

  • Add a repository collaborator

    Adds a GitHub user as a repository collaborator, or updates their permission if already a collaborator; `permission` applies to organization-owned repositories (personal ones default to 'push' and ignore this field), and an invitation ma...

  • Add assignees to an issue

    Adds assignees to a GitHub issue. This action only adds users - it does not remove existing assignees. Changes are silently ignored if the authenticated user lacks push access to the repository.

  • Add email for auth user

    Adds one or more email addresses (which will be initially unverified) to the authenticated user's GitHub account; use this to associate new emails, noting an email verified for another account will error, while an existing email for the...

All 846 GitHub actions →

How it works

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

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

Put your agent on Figma and GitHub

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