Operator
← All integrations
Figma logo+Jira logo

Connect Figma to Jira

Automate Figma and Jira with AI

Jira tickets and Figma frames drift when nobody keeps the link current. Operator.io connects both through OpenClaw so a comment on a frame can open a Jira story with repro steps, issue status changes update the Figma review label, and sprint planning can pull open design work from the file. Ask for everything blocking a release epic and it merges Jira blockers with frames still in changes requested.

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 Jira

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 Jira

  • Add Attachment

    Uploads and attaches a file to a Jira issue.

  • Add Comment

    Adds a comment using Atlassian Document Format (ADF) for rich text to an existing Jira issue.

  • Add Users to Project Role

    Adds users and optionally groups to a project role.

  • Add User to Group

    Adds a user to a Jira group.

  • Add Watcher to Issue

    Adds a user to an issue's watcher list by account ID. Requires the authenticated user to have permission to view the issue and manage watchers; insufficient permissions may result in silent failure or an error response.

  • Add Worklog

    Tool to add a worklog entry to a Jira issue. Use when logging time spent on an issue.

All 94 Jira actions →

How it works

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

How do I connect Figma and Jira to Operator?
You authorize Figma and Jira 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 Jira?
You describe the outcome in plain language and your agent works between the two, reading from one and acting in the other. It picks the right Figma and Jira actions on its own, so you do not map fields or pick triggers.
Can my agent keep Figma and Jira in sync?
Yes. It can watch Figma and act in Jira, 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 Jira integrations

Put your agent on Figma and Jira

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