Overview
Connect Figma to Taskade so design work and project work share one loop. A new comment or a published library can start an automation, and any automation can read a file, export a frame as an image, or post a comment back.
TL;DR: Figma connects to Taskade automations with a Figma personal access token. Triggers start an automation on a new comment, a file edit, a named version, or a library publish. Actions read files and layers, export images, list folders and versions, and read and post comments. Figma steps need Pro and up.
Before You Start
- What you need: A Figma account and a Taskade workspace. The triggers also need a paid Figma plan (Professional or above), because the free Figma plan cannot send events.
- Plan: Pro and up. On Free and Starter, the Figma steps show a PRO badge and open the upgrade page.
- Time: About 5 minutes
Step 1: Create a Figma Personal Access Token
- In Figma, open the account menu, then Settings, then the Security tab.
- Under Personal access tokens, click Generate new token.
- Pick an expiration. Figma allows at most 90 days, so you connect again after that.
- Give these scopes:
current_user:read,file_content:read,file_comments:read,file_comments:write,file_versions:read,folders:read, andwebhooks:write. A scope that you leave out turns off the steps that need it. - Copy the token. Figma shows it only once.
Step 2: Connect Figma in Taskade
Taskade stores the connection for the whole workspace, so every automation that uses Figma reuses it. Your AI agents and Taskade EVE can use the same connection.
- Open Automations in your workspace, and click Create.
- Add a trigger or a step, and search for Figma.
- Click Connect.
- Paste the token into Personal access token.
- Save the connection. Taskade tests it with Figma before it saves it.
Step 3: Pick a Trigger or an Action
Pick a Figma trigger to start an automation, or add a Figma action after any trigger. See Automation Triggers and Automation Actions for the Taskade steps that you can combine with them.
Each trigger asks what to Watch: one file, every file in a folder, or every file in a team. Paste the Figma link or the ID. To watch a file or a folder, you need Can edit access. To watch a whole team, you must be a team admin.
| Trigger | Starts the automation when |
|---|---|
| New Comment | Someone comments on, or replies in, a watched file. |
| File Updated | Someone edits a watched file. Figma sends the event within 30 minutes after the edits stop, not on every change. |
| New Named Version | Someone saves a named version in the version history of a watched file. |
| Library Published | Someone publishes a watched library file. The event names the components, styles, and variables that changed. |
| Action | What it does |
|---|---|
| Get File | Reads the name, the last edit time, and an outline of the pages and top-level frames of a file. |
| Get File Nodes | Reads the layers that you name by node ID, with their children and the text of each text layer. |
| Export Images | Saves layers as PNG, JPG, SVG, or PDF, and returns a download link for each one. The links expire after 30 days. |
| Get Comments | Lists the comments on a file, newest first, with the author and the layer of each comment. |
| Post Comment | Posts a new comment on a file, or a reply to a comment. A new comment can be pinned to a layer. |
| Get File Versions | Lists the version history of a file, newest first. |
| List Team Folders | Lists the top-level folders of a Figma team. Figma called folders "projects" before August 2026. |
| List Folder Files | Lists the files in a folder, most recently edited first. |
The steps also accept a FigJam board link in place of a design file link.
You are done when a test comment on a watched file starts the automation, and the run shows in the automation history.
Build Your First Figma Automation
Start from one of these patterns, then add your own steps.
| Goal | Trigger | Steps that follow |
|---|---|---|
| Turn feedback into tasks | New Comment on a design file | Ask AI to sort the comment, then Add Task for the designer |
| Share each release | New Named Version | Export Images of the main frame, then Add Task with the image links |
| Track library changes | Library Published | Add Task that lists the changed components for the front-end team |
To describe an automation in plain words instead, ask Taskade EVE in your workspace. For example:
Build an automation that uses Figma. When someone comments on my design file, add a task with the comment text to a project that I pick. Do not add any other steps yet.
The last sentence of the prompt keeps the first draft small, so you can test one step before you add more.
Frequently Asked Questions
Why does my Figma trigger not start?
Figma sends trigger events only on a paid Figma plan, Professional or above. Your token also needs the webhooks:write scope, and you need Can edit access to the file or folder that you watch. Figma allows at most 3 of these triggers on each file, 5 on each folder, and 20 on each team.
Why do some Figma steps stop after a few runs?
Figma limits API calls by your Figma seat. A View or Collab seat gets only 20 calls a month for Get File, Get File Nodes, and Export Images. A Dev or Full seat gets a much higher limit.
Related guides
- Confluence Integration. Keep design notes next to your docs.
- Linear Integration. Send design work to your issue tracker.
- GitHub Integration. Connect design changes to code.
- Automation Actions. The Taskade steps to combine with Figma.
- Automations & Execution. Chain triggers and actions across 100+ integrations.
- Explore integrations and browse automations.