Connect Clickup to Figma
Automate Clickup and Figma with AI
Design requests in ClickUp should open on the Figma file the brief references. On Operator.io, an OpenClaw agent connects both so a task status change can comment on the linked frame, new Figma replies update the ClickUp description, and anyone can ask for the mock tied to a task ID. When review finishes, tell it to mark the ClickUp item done and it adds a closing note on the Figma thread.
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 Clickup and Figma
What your agent does in Clickup
Add dependency
Adds a 'waiting on' or 'blocking' dependency to a task, requiring either `depends_on` (task becomes waiting on) or `dependency_of` (task becomes blocking), but not both; `team_id` is required if `custom_task_ids` is true.
Add guest to folder
Adds a guest to a folder with specified permissions; requires a ClickUp Enterprise Plan.
Add guest to list
Shares a ClickUp List with an existing guest user, granting them specified permissions; requires the Workspace to be on the ClickUp Enterprise Plan.
Add guest to task
Assigns a guest to a task with specified permissions; requires ClickUp Enterprise Plan, and `team_id` if `custom_task_ids` is true.
Add tags from time entries
Associates a list of specified tags with one or more time entries within a given Team (Workspace).
Add tag to task
Adds an existing tag to a specified task; team_id is required if custom_task_ids is true.
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.
How it works
Tell the agent what you want to happen between Clickup and Figma, for example to watch one and act in the other, or to keep the two in step. It reads what it needs from Clickup, works out what to do, and runs the matching action in Figma 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 Clickup and Figma
- How do I connect Clickup and Figma to Operator?
- You authorize Clickup and Figma 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 Clickup and Figma?
- Tell it the job and it moves between Clickup and Figma 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 Clickup and Figma in sync?
- Yes. It can watch Clickup and act in Figma, 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.
Clickup and Figma integrations
Put your agent on Clickup and Figma
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