Resources · Make integration

Figma Make integrationAutomate Figma with Make.

Your Figma comments deserve better than a tab left open all day. The Figma Make integration gives you 8 modules, the bricks of a scenario, which is the automation Make runs for you. Two of them watch your files. Here is the connection, then the first scenario.

Try the Figma integration on MakeSee the 8 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Figma Make integration actually automate?

It links your Figma account to Make once, then lets Make read and write the parts of Figma that carry conversation and history: comments left on a file, changes to that file, the files sitting inside a project, the projects of a team. Make does the waiting and the clicking. You describe what should happen.

Start with the conversation. Watch File Comments picks up a new comment on a file and passes it down the chain, so a design review stops living in a browser tab. Post a Comment sends the answer back into the file, where designers look.

Then the file itself. Watch File Updates fires when a file changes, and List File Version History reads the trail of saved versions behind it. Together they make a quiet log of what moved and when, with nobody filling in a form.

Third, the inventory. List Projects returns the projects of a team, List Project Files opens one of them, and List Comments reads what was said on a given file. That trio audits a whole client workspace before a redesign.

The honest part: nothing here draws, edits or exports a design. The 8 modules work around the file, not inside the canvas. Make an API Call covers the rest of the Figma API when a module is missing, and Make's Figma documentation says it was generated by AI from Figma's own docs, so check anything load-bearing at the source.

The same app exists on n8n. The Figma n8n integration page covers that side, n8n vs Make lays out the criteria, and Make training starts with scenarios like the one below.

Connect

How do you connect Figma to Make?

  1. 01

    Drop a Figma module in and open the connection

    In the editor, put any Figma module into a scenario and click Create a connection. A connection is your Figma account linked to Make one time, then reused by every Figma module you add later, so this part happens once and never again.

  2. 02

    Name it something you will recognize

    The Connection name field is optional, and leaving it empty is a false economy. Write the Figma team or the account it belongs to. The day a scenario stops running, you will know which login to check without opening every module.

  3. 03

    Authenticate the account

    Figma takes two ways in: OAuth 2, where a Figma window asks you to authorize Make, or an access token you paste. Either way an active Figma account is the prerequisite. Follow the instructions on screen and the window closes on its own once it works.

First scenario

Your first scenario: answer a Figma comment without opening Figma

GoalWhen someone leaves a comment on a Figma file, Make posts a reply on that same file.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to place the first module. Search Figma by name in the list of apps, then pick Watch File Comments.

  2. 02

    Point the trigger at your file

    Fill the module fields. Once the connection exists, Make lists what it can read on your account, so you choose from a list instead of hunting for an identifier somewhere in a URL.

  3. 03

    Add the reply

    Click the + on the right of the trigger and add Post a Comment. Map the file from the first module into the second one, so the reply lands on the file that was commented on.

  4. 04

    Test with Run once

    Click Run once and the scenario executes a single time. Each module then shows the bundles it received, a bundle being one item travelling down the chain, here one comment.

  5. 05

    Schedule it and switch it on

    Set the clock on the first module, what Make calls Scheduling: a new scenario runs every 15 minutes. Adjust that to the rhythm you need, then flip the scenario on.

Triggers

What starts a Figma scenario

2 modules start a scenario when something happens in Figma. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Figma as soon as it happens.

Figma1Watch File Comments

Watch File Comments

triggerIn the docs only

Watch File Comments keeps an eye on the conversation attached to a file and starts your scenario when a new comment appears.

How it fires
scheduled. Make checks Figma on the schedule set on this module, not the second somebody hits send.
When to use it
a client reviews a mockup late on Friday and the feedback has to reach people who never open Figma.
Watch out
the gap between the comment and your scenario is exactly that interval, 15 minutes at the shortest on the Free plan.
Figma2Watch File Updates

Watch File Updates

triggerIn the docs only

A design file moves all day. This one starts the scenario when the file changes, so the modules behind it can log what happened, read it, or tell somebody.

How it fires
scheduled. Make asks Figma at the rhythm set on the scenario, not the instant the file is saved.
When to use it
a marketing team pulls assets from one shared file and needs to know when the source moved.
Watch out
a busy file fires often, and every item handled costs an operation, one run of one module on one item, counted on your plan.
Modules

What Figma can do inside a scenario

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

Figma1

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Some corner of Figma has no module of its own. This one sends your request to any endpoint of the Figma API using the connection already in place, so the scenario keeps going instead of stopping at the edge of the catalog.

When to use it
what you need is in none of the seven other modules.
Watch out
you write the request yourself, so keep Figma's API reference open next to the editor.
Figma2

Post a Comment

Action

In Make“Posts a comment to a file.”

Post a Comment writes into the file itself, where designers actually look. The note lands on the mockup instead of in an inbox somebody muted weeks ago.

When to use it
a copy was approved somewhere else and the file has to carry the instruction.
Watch out
an action handles one item at a time, so a list coming out of a search means one comment per item.
Figma3

List Comments

Search

In Make“Lists all comments left on a file.”

Everything said on a file, in one pass. List Comments returns the comments as separate items: none if the file is quiet, several if the review was lively.

When to use it
you want to reread the feedback on a file on demand, rather than watching it all day.
Watch out
a search returns what it finds, so plan the empty case before the scenario meets a silent file.
Figma4

List File Version History

Search

In Make“Lists the version history of a file.”

Figma keeps every saved version of a file. List File Version History hands that trail to the scenario, which can archive it, count it or pass it to the next module.

When to use it
a client asks what changed since the version they signed off on.
Watch out
history grows with the file, and each entry is one more item crossing your scenario.
Figma5

List Project Files

Search

In Make“Lists the project files in a given project.”

Give it a project, it gives back the files inside. Handy the moment a scenario has to work on a whole project instead of the one file you picked by hand.

When to use it
auditing a client project file by file, without opening any of them.
Watch out
it needs the project first, which is exactly what the next module is for.
Figma6

List Projects

Search

In Make“Lists all the projects of a certain team.”

List Projects climbs one level up and returns the projects belonging to a team. It is the starting point when the scenario should cover everything, not the two files you happen to remember.

When to use it
mapping what exists before deciding what deserves automating.
Watch out
a team grows, so a scenario built on this list handles a few more items every month.
Need help

Need help automating Figma with Make?

A person reads every message.

FAQ

Questions people ask next

01Is the Figma Make integration free?
Yes, from the Free plan. Figma is a standard app in Make, not one of the enterprise apps reserved to the Enterprise plan, so all 8 modules are available without paying Make anything. The limits are what deserve a look: the Free plan allows 2 active scenarios, 15 minutes minimum between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of transfer. Paid plans take the interval down to 1 minute, lift the cap on active scenarios and push execution to 40 minutes. Your Figma subscription is a separate matter, settled with Figma.
02What do you need to connect Figma to Make?
An active Figma account, and one of two ways to prove it is yours: OAuth 2, where a Figma window asks you to authorize Make, or an access token taken from your Figma account and pasted into the connection. Nothing else. In practice you add a Figma module to a scenario, click Create a connection, name it if you want to, then enter the credentials or follow the instructions on screen. If you build your own OAuth app on the Figma developers page, Figma asks for a callback URI, Make gives you the one to paste, and Figma hands back a client ID and a client secret.
03Does the Figma trigger react in real time?
No. Both Figma triggers are scheduled, which means Make goes and asks Figma at the interval set on the first module, rather than Figma pushing the news the second it happens. A new scenario runs every 15 minutes, which is also the floor on the Free plan, while paid plans go down to 1 minute. Neither Figma trigger is an instant one, the kind an app wakes up itself and Make marks with a lightning badge, so the only lever you have is the interval. For a comment or a file change, that is usually plenty.
04What if a Figma module is missing in Make?
Make an API Call is the answer. It sends your own request to any endpoint of the Figma API, through the connection already sitting in your scenario, which covers what the listed modules leave out. Two things are worth knowing first. You write the request yourself, so the Figma API reference stays open beside you. And Make's documentation for this app states that it was generated by AI from Figma's own docs and may contain mistakes, so anything load-bearing gets checked with Figma directly. If the request still will not fit, n8n exists.
05Make or n8n for Figma?
It depends on who maintains the thing. Make hands you 8 ready modules, a visual editor and one connection to set up, which is the short road when you want it running this afternoon. n8n speaks better to a team that already writes code, wants the automation in a repository, or has to host it in house. The Figma catalogs are not identical on both sides, so the honest test is to list the 2 or 3 things you really want automated and check each one against both tools. For a design team, neither answer is absurd.
Hack'celeration Lab

Get our weekly automation tips.

No spam. Unsubscribe anytime.

Same platform

Other docs you might need on this stack.

Browse all integrations