Resources · Zapier integration

Figma Zapier integrationAutomate Figma with Zapier.

The Figma Zapier integration gives you 7 triggers, 9 actions and 3 searches. Two of the triggers react instantly, the other five wait for Zapier's next check. Here is what each one does, what it costs and where it breaks, before you open the editor.

See the 19 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Figma Zapier integration actually does

Zapier sits between Figma and the rest of your tools. It notices something in a Figma file (a new comment, a new version, a new file in a project) and then does something with it, in Figma or elsewhere. Figma is the collaborative design tool your team uses for interfaces, prototypes and graphics; Zapier is the glue that moves what happens there.

Three outcomes cover most real uses. A feedback loop that never goes quiet: New Comment picks up every remark left on a file, and React to Comment lets the Zap acknowledge it with an emoji so the author knows it was seen. A version log: New File Version fires each time a new version of a file is created, and Search File Version pulls its full details so a later step can file them away. A design handoff that keeps up: Create Image renders chosen frames of a file as images, and Create Dev Resource attaches a named link to a precise node of the file for developers.

What it does not do is just as useful to know. Zapier cannot draw, move or restyle anything on your canvas: every action works on comments, images, variables, dev resources or file details, never on the design itself. Several operations also carry a restriction in brackets in their name: Paid Accounts Only, Requires Dev Seat or Enterprise Only. They most likely refer to your Figma plan or seat; Zapier says nothing more, so check your Figma account before building on one.

If you are weighing tools, the same app is covered on our Figma n8n integration page and our Figma Make integration page, written the same way.

Vocabulary

Zapier words you will meet on this page

Seven terms, each in plain words. Once explained here, the rest of the page uses them as is.

Zap
The automation you build: one trigger, then one or more actions that run every time that trigger event happens.
Trigger
The event in Figma that starts the Zap, like a new comment. Once the Zap is on, Zapier waits for it.
Action
What the Zap does after it starts: the step that writes, posts or creates something for you, in Figma or another app.
Task
What Zapier bills you for: one action that your Zap completes successfully. Your plan counts these and nothing else.
Polling vs instant
A polling trigger is checked on a timer, Zapier asks for new items. An instant trigger is reported by the app the moment it happens.
Filter
A step that only lets the Zap continue when what arrived matches a condition you set, and stops it quietly otherwise.
Search step
A step that looks up something that already exists in an app, so the steps after it can reuse what it found.
Cost

What a Figma Zap really costs you

The trigger is free. Watching Figma for new comments or versions costs nothing either, however often Zapier checks. Only an action that goes through is counted as a task.

  • Trigger and checksNo task
  • Each successful actionOne task
  • Free plan100 tasks a month, two-step Zaps
  • Premium appNo, available on Free

In a Zap with several actions, each successful one counts on its own: three actions, three tasks per run. A failed action is not counted. The free plan gives you 100 tasks a month and two-step Zaps only, one trigger and one action. Add a filter or a search step and the Zap becomes multi-step, which means a paid plan. Figma is not a premium app, so it works from the free plan. For a wider look at the tool itself, see our Zapier review.

Connect

Connect your Figma account to Zapier

  1. 01

    Open your connections

    In Zapier, go to the Apps page and click + Add connection. A dialog opens: type Figma and pick it from the list. You need a Figma account, plus access to any file or project you do not own and want the Zap to touch.

  2. 02

    Sign in to Figma

    Click Add connection. A new tab opens on Figma's own login screen. Sign in with the account whose files the Zap should read or write, not a colleague's, because every step will act as that account.

  3. 03

    Grant access

    Figma asks you to let Zapier into the account. Accept, and the tab closes. The connection now sits on your Apps page and every Figma step in every Zap reuses it, so you only do this once.

First Zap

Build your first Figma Zap

GoalEach time a comment flagged urgent lands on a file, the Zap reacts to it so the author sees it was picked up.

  1. 01

    Create the Zap

    Start a new Zap, then pick Figma and New Comment as the trigger. Choose your Figma connection and paste the File Key of the file you want to watch.

  2. 02

    Test the trigger

    Test the trigger. Zapier brings back the three most recent comments on that file. Pick one with real text, so you can map its fields in the next steps.

  3. 03

    Add the filter

    From the plus icon, add a Filter. Pick the comment text field, the rule that checks it contains a word, and type urgent. This step makes the Zap multi-step, so it needs a paid plan.

  4. 04

    Add the reaction

    Add the action React to Comment. Map the File Key and the comment ID from the trigger, then type an emoji shortcode such as :heart: in the Emoji field.

  5. 05

    Test and publish

    Run the action test once and check the reaction showed up in Figma. Then click Publish: the Zap is on and reacts to new urgent comments from now on.

Triggers

Figma triggers: what can start your Zap

7 events start a Zap when something happens in Figma, and 2 of them are instant: the app calls Zapier straight away, whatever your plan.

1

File Updated (Paid Accounts Only)

Instant trigger

In Zapier“Triggers when a file is updated (within 30 minutes of editing inactivity in a file).”

Starts the Zap when a file changes, but only once people have paused their editing on it. You watch a team, a project or a single file, and you can list several file IDs separated by commas.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
you want a review request or a notification sent once a designer has finished a work session, not on every click.
Watch out
"right away" starts after that editing pause (see the breaks section below), and its name flags it as Paid Accounts Only.
2

New Comment

Polling trigger

In Zapier“Triggers when a new comment is created in a Figma file.”

Picks up each new comment left on one Figma file and hands it to the next steps, so they can route it to the right person or channel. You point it at the file with its File Key.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
the instant version, marked Paid Accounts Only, is not open to you, and you still want design feedback collected somewhere your team reads every day.
Watch out
if the Zap itself posts comments on that same file, it will catch its own words and loop.
3

New Comment (Paid Accounts Only)

Instant trigger

In Zapier“Triggers when a new comment is created in a Figma file.”

The fast twin of the previous trigger: same event, a new comment, but Figma pushes it to Zapier itself. It can watch a whole team or project, not just one file, through its context setting.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
feedback needs a fast answer, and the timer of a polling trigger on the free Zapier plan is too slow.
Watch out
Context only accepts team, project or file, and Context ID must be the ID of that same team, project or file.
4

New Dev Resource (Requires Dev Seat)

Polling trigger

In Zapier“Triggers when a new dev resource is added to the Figma file.”

Fires when someone attaches a dev resource to a file, that is a named link attached to a precise node of the file for developers.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
your engineering lead wants a log of every link added during handoff, kept in a spreadsheet or a project tool outside Figma.
Watch out
its name says Requires Dev Seat, most likely a Figma seat; check yours before you count on it.
5

New Project File

Polling trigger

In Zapier“Triggers when a new file is added to a project.”

Triggers when a new file appears inside a project you choose, which makes it the natural starting point for kick-off routines on fresh design work.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
each new file in a client project should create a card in your task tool, so nobody forgets to brief the developer.
Watch out
the project list only loads if your connected account carries a personal access token, and you need the team ID from the team page address.
6

New File Version

Polling trigger

In Zapier“Triggers when a new file version is created.”

Catches each new version saved in the history of a file. You can follow several files at once by typing their File Keys separated by commas.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
product managers want a changelog of new versions kept outside Figma, without opening the file.
Watch out
its ID field is exactly what Search File Version expects, so map it rather than typing it by hand.
7

New Variable (Enterprise Only)

Polling trigger

In Zapier“Triggers when a new variable is found in a file (local or published).”

Spots a variable that shows up in a file, whether it was created locally or published from a library. Variables are the stored values (colours, spacing, text) a design system reuses everywhere.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
a design system team wants each new token announced to developers so the code side can follow.
Watch out
its name says Enterprise Only, most likely the Figma plan; check yours before building on it.
Actions

Figma actions: what your Zap can do

Figma gives you 9 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Create Comment

Action

In Zapier“Creates a new comment in a Figma file.”

Posts a new comment on a Figma file with the message you write or map from an earlier step. Designers see it in the usual comment panel.

When to use it
a ticket changes status in your project tool and the designer should read the news right where they work.
Watch out
never pair it with a comment trigger on the same file, or it feeds itself.
2

Create Dev Resource (Requires Dev Seat)

Action

In Zapier“Creates a new dev resource in a Figma file.”

Pins a named link to a precise layer of a file, where developers look for them. It needs a URL, a name and the node ID.

When to use it
a new ticket for a screen should appear as a link right on that screen for the developer.
Watch out
like its trigger twin, its name says Requires Dev Seat.
3

Create Image

Action

In Zapier“Creates a new image from a Figma file.”

Renders chosen parts of a file as images, from a list of node IDs (a node is any frame or layer). Later steps can send or store those images.

When to use it
each new version should drop a fresh preview of the key screens into the client channel.
Watch out
the list of node IDs is mandatory, so have them ready before building.
4

Create Variable (Enterprise Only)

Action

In Zapier“Creates a new variable in a Figma file.”

Adds a variable to a file, inside the collection you name by its ID, with a type that says what kind of value it holds. You can also hide it from publishing.

When to use it
tokens defined in a spreadsheet by the brand team should land in the design file without retyping.
Watch out
its name says Enterprise Only, and it needs the ID of an existing variable collection.
5

Delete Comment

Action

In Zapier“Deletes a comment in a Figma file.”

Erases a comment from a file, given its ID. Useful for tidying up threads that a Zap posted earlier and that are no longer relevant.

When to use it
an automatic reminder comment should vanish as soon as the matching review is approved elsewhere.
Watch out
it needs the comment ID, so test it on a throwaway file before pointing it at real threads.
6

Delete Comment Reaction

Action

In Zapier“Deletes your own comment reaction in a Figma file.”

Removes a reaction from a comment, but only one that your connected account placed itself. It needs the comment ID and the same shortcode.

When to use it
a temporary "in progress" emoji should disappear once the task linked to the comment is done.
Watch out
reactions left by colleagues stay untouched, whatever you map.
7

React to Comment

Action

In Zapier“Reacts to a comment in a Figma file.”

Adds an emoji reaction to an existing comment, a light way to show that something was picked up without adding noise to the thread.

When to use it
a bug comment has been copied to your tracker and you want a visible sign of it in Figma.
Watch out
the emoji goes in as a shortcode between colons, like :heart:, not as the picture itself.
8

Update Variable (Enterprise Only)

Action

In Zapier“Updates an existing variable in a Figma file.”

Changes an existing variable in a file, found by its variable ID, including whether it stays hidden from publishing.

When to use it
a brand colour changes in your source of truth and the design file should follow without a manual edit.
Watch out
the variable ID is mandatory, so map it from an earlier step rather than typing it.
9

API Request (Beta)

Action

In Zapier“This is an advanced action which makes a raw HTTP request that includes this integration's authentication.”

An advanced step that sends your own request to Figma while reusing the connection you already set up, for the cases no ready-made action covers.

When to use it
a teammate comfortable with Figma's documentation needs one specific call that the list above lacks.
Watch out
it only reaches Figma addresses, and its Stop on error setting decides whether a failure halts the Zap.
Searches

Figma searches: look up what already exists

3 search steps look for data that already exists in Figma, so a later step can use it.

Searches sit at the bottom of the action list, under their own SEARCH heading. Each one fetches details a previous step did not carry. Figma offers no find-or-create variant: if nothing is found, nothing gets created.

1

Search File

Search

In Zapier“Searches for a file by key.”

Finds a file from its File Key and hands what it found to the next steps.

When to use it
your trigger comes from another app and only carries a Figma link, yet the next step needs the file itself.
Watch out
paste the key, not the full link.
2

Search File Meta

Search

In Zapier“Searches for a file by key and returns metadata.”

Looks a file up by its key and returns its metadata, for when you want to label or sort it.

When to use it
a digest for the client should list files with their details, not their whole content.
Watch out
it takes the same File Key as Search File, so a mistyped key breaks both.
3

Search File Version

Search

In Zapier“Searches for a file version by ID and returns its full metadata.”

Looks up one version of a file and returns its full details. The ID it expects joins the file key and the version id with a colon.

When to use it
right after New File Version, to enrich the log entry before it is filed.
Watch out
map the ID field of that trigger instead of assembling it yourself.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap and skips the steps that relied on it. Switched on, the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    This box turns a search into a find-or-create on apps that offer one. None of the Figma searches do, so you will not see it here.
  3. If multiple search results are found?
    Three ways out when several items match: keep the first one (the default), stop the Zap, or pass all of them on at once.
When it breaks

When a Figma Zap breaks

Six situations to know before you rely on a Figma Zap.

Zapier attaches one help article to Figma, the getting started guide. The rest comes from how triggers work in general and from what the operation labels say. Read these before you publish, and keep our Zapier troubleshooting page for the day a run turns red.

  • Old comments and versions are ignored

    A Zap only reacts to what happens after you publish it. The comments already on a file and the versions already saved stay where they are; moving that backlog is a separate job.

  • A comment Zap that answers itself

    A Zap that watches comments on a file and posts comments on that same file sets itself off again and again, and eats your task count fast.

  • File Updated seems late

    Its official description says it fires within 30 minutes of editing inactivity in the file. A designer who keeps working pushes it back; nothing is broken.

  • A paid-only step on a free account

    Operations labelled Paid Accounts Only, Requires Dev Seat or Enterprise Only most likely need that Figma plan or seat. Check yours before building a Zap on one.

  • A wrong File Key or team ID

    Most steps start from a File Key copied from the file address, and New Project File needs the team ID too. Both are mandatory, so a wrong one leaves the step without its target.

  • A sudden flood of items

    After a bulk import, a trigger that returns a huge batch at once can be held back by Zapier's flood protection.
Need help

Need help automating Figma with Zapier?

A person reads every message.

FAQ

Figma Zapier integration: your questions

01Is the Figma Zapier integration free?
Yes, Figma is not a premium app on Zapier, so you can connect it from the free plan. That plan gives you 100 tasks a month and Zaps of two steps only: one trigger, one action. As soon as you want a filter, a search or a second action, the Zap is multi-step and needs a paid plan. Separately, some Figma operations carry Paid Accounts Only, Requires Dev Seat or Enterprise Only in their name, which most likely points to your Figma plan or seat. Check both sides before you build.
02How many tasks does a Figma Zap use?
One task per action that succeeds, per run, and nothing for the trigger. Zapier checking Figma for new comments or versions is free too, however often it happens. So a Zap that reacts to each new comment costs one task per comment. If it also posts a message in another app, that is two. A step that fails is not counted. With 100 tasks a month on the free plan, a busy file can use them up quickly, so add a filter on a paid plan when only some comments matter.
03Does Figma trigger Zaps in real time?
Two of the seven triggers do: File Updated and New Comment (Paid Accounts Only). Figma tells Zapier directly, so they start the Zap right away on any Zapier plan. Note that File Updated, by its official description, fires within 30 minutes of editing inactivity in the file. The five others are polling triggers: Zapier checks at an interval set by your plan, 15 minutes on Free, 2 on Professional and 1 on Team and Enterprise. A Zap built on an instant trigger shows a lightning bolt in the editor.
04What does it take to connect Figma to Zapier?
A Figma account, and access to the files or projects you want the Zap to read or change if you do not own them. The connection itself happens from the Apps page in Zapier: add a connection, pick Figma, sign in in the tab that opens and grant access. Keep a file open in your browser too, because most steps ask for its File Key, which sits in the address bar. The New Project File trigger also needs your team ID and a personal access token on the connection.
05Why does a Figma comment Zap keep firing on its own?
Because it is probably reading its own output. If a Zap starts on a new comment in a file and one of its actions creates a comment in that same file, each run produces the next trigger. Zapier warns that this kind of loop burns through tasks quickly. The fix is to post the reply somewhere else, or to use React to Comment instead of Create Comment, which adds no new comment to the file.
06What if the Figma action you need is not in the list?
Then the API Request (Beta) action is the way in. It sends a request of your choice to Figma while reusing the connection you already set up, so there is no new login to handle. It only reaches Figma addresses, and its Stop on error setting decides whether a failed call halts the Zap or lets it continue. It does require reading Figma's own documentation to build the request, so it suits someone comfortable with that.
07Zapier, Make or n8n for Figma?
There is no single winner, only criteria. On Zapier, Figma exposes 19 operations: 7 triggers, two of them instant, 9 actions and 3 searches, and it is not a premium app, so a two-step Figma Zap runs on the free plan. Set that list against the Figma operations each of the other two tools offers, check which ones your use case actually needs, and weigh the tool your team already knows. The one that covers your exact event and action is the right pick for this job.
Same platform

Other docs you might need on this stack.

Browse all integrations