Resources · n8n integration

Figma n8n integrationAutomate Figma with n8n.

Design files move all day, and nothing downstream hears about it. The Figma n8n integration is a trigger-only node: 5 events split across 2 families, delivered by webhook once the workflow is active. It suits design ops people who want handoff to run without a reminder.

Try the Figma integration on n8n

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the Figma n8n integration actually give you?

The Figma Trigger (Beta) node starts an n8n workflow when something happens in a Figma team. It listens to 5 events grouped in 2 families, file and library, and it works by webhook: a URL that Figma calls the moment an event fires, so the workflow runs within seconds instead of waiting for a scheduled check.

Start with comment triage. Set the trigger on fileComment, and every comment left on a file in the team becomes an n8n execution. From there the item goes wherever the team already talks, most often Slack, with the values you need pulled from the payload through an expression such as {{ $json.field }}. Designers stop watching notifications, and nobody has to remember to forward anything.

Second, a version log that writes itself. fileVersionUpdate fires when someone creates a named version in the version history of a file, which is the closest thing Figma has to a release marker. Append one row per event to Google Sheets or to Airtable, and the design changelog stops being a monthly archaeology session.

Third, design system announcements. libraryPublish fires when a library file is published, so the workflow can send the news to engineering by Gmail the second a component ships. One event, one message, no side channel.

The trigger is the whole node here. Anything beyond the event catalog goes through HTTP Request, which calls any endpoint of the Figma API while reusing the same credential through predefined authentication. That is the normal pattern: Figma Trigger to start the workflow, HTTP Request for the rest, and the usual n8n nodes in between.

Two things shape how you scope it. The trigger watches one team, named by Team ID, so a company with several teams needs several workflows or several triggers. And fileUpdate is broader than it looks: it fires when a file saves or is deleted, a save being counted when someone closes a file within 30 seconds after making changes. If that firing rate is more than a Slack channel can take, filter right after the trigger. The n8n training walks through that filtering step with a real workflow.

Connect

How do you connect Figma to n8n?

  1. 01

    Pick an authentication method

    Figma credentials in n8n support two methods: Access token and OAuth2. Both need a Figma account with an admin or owner level. A credential is created once in the Credentials menu of n8n and reused in every workflow, so this step happens one time even if you later build a dozen Figma workflows.

  2. 02

    Generate the token or register the app

    For the simple route, generate a Personal Access Token in Figma and paste it into the credential. For OAuth2 on a self-hosted n8n, open the Figma developer apps page, select Create a new app, give it a name such as n8n integration, copy the OAuth Redirect URL from n8n into Add a callback, then bring the Client ID and Client Secret back into n8n.

  3. 03

    Point the trigger at a team and activate

    In the node, fill Team ID with the identifier of the Figma team to monitor, then choose the event under Trigger On. Activating the workflow is what registers the webhook on the Figma side, which means a workflow left inactive receives nothing. Save, activate, then act in Figma to see the first execution arrive.

Triggers

What can the Figma Trigger listen to?

Figma Trigger (Beta) is the node that starts a workflow when something happens in Figma. It listens to 5 events, listed below by family. Pick one or several, activate the workflow: n8n registers the webhook on your Figma account.

What you see in n8n

Every event, by family

One row per object, one chip per action. The event to tick in the node is object.action; hover a chip to read exactly when it fires.

file.*4
    library.*1

      Configuration notes

      01Set Up The Figma TriggerThis node is the entry point of the workflow and the only Figma node involved. When the workflow is activated, n8n registers a webhook with Figma, meaning a URL that Figma calls each time a selected event happens, which is why execution starts within seconds and no polling interval exists to configure.

      This node is the entry point of the workflow and the only Figma node involved. When the workflow is activated, n8n registers a webhook with Figma, meaning a URL that Figma calls each time a selected event happens, which is why execution starts within seconds and no polling interval exists to configure.

      Key parameters

      • Team ID: the Figma team the trigger monitors, required. It comes from the URL of the team page, figma.com/files/team/{TEAM-ID}/, and it scopes every event the workflow will see.
      • Trigger On: the event the node listens to. The list holds 5 entries spread over 2 families, file and library.
      Use cases
      a design ops lead who wants Figma activity to reach the tools the rest of the company already reads, without asking designers to copy anything by hand.
      When to use it
      whenever the workflow should start from Figma itself rather than from a schedule.
      02File Commented, Updated, Version Updated, DeletedFour of the 5 events belong to the file family, and each answers a different question. fileComment fires when someone comments on a file. fileUpdate fires whenever a file saves or is deleted, a save being counted when a file is closed within 30 seconds after changes. fileVersionUpdate fires when a named version is created in the version history of a file. fileDelete fires when a file has been deleted, counted file by file, so removing a whole folder is not reported as one event per file inside it.

      Four of the 5 events belong to the file family, and each answers a different question. fileComment fires when someone comments on a file. fileUpdate fires whenever a file saves or is deleted, a save being counted when a file is closed within 30 seconds after changes. fileVersionUpdate fires when a named version is created in the version history of a file. fileDelete fires when a file has been deleted, counted file by file, so removing a whole folder is not reported as one event per file inside it.

      Key parameters

      • Trigger On: one of the four file events per node. A workflow that needs two of them uses two Figma Trigger nodes.
      • Team ID: keeps all four events scoped to a single team.
      Use cases
      send comments to the designer on duty, and log named versions as they appear. Values from the incoming item are read with an expression like {{ $json.field }}.
      03Library PublishlibraryPublish is the library family on its own, and it fires whenever a library file is published. That publish is the moment a component or a style reaches everyone consuming the library, which makes it the cleanest signal that the design system changed. Nothing else in the event list carries that meaning.

      libraryPublish is the library family on its own, and it fires whenever a library file is published. That publish is the moment a component or a style reaches everyone consuming the library, which makes it the cleanest signal that the design system changed. Nothing else in the event list carries that meaning.

      Key parameters

      • Trigger On: set to Library Publish for a workflow that only reacts to design system releases and ignores day to day file activity.
      • Team ID: the published library has to belong to the team the trigger watches, otherwise nothing arrives.
      Use cases
      announce a design system release to engineering, or open a review item each time the library ships. Whatever the payload carries is reachable through {{ $json.field }}.
      When to use it
      when the interesting unit is the release, not the file.
      Need help

      Need help automating Figma with n8n?

      A person reads every message.

      FAQ

      Figma and n8n, the questions that come next

      01Is the Figma n8n integration free to use?
      Yes on the n8n side. The Figma Trigger (Beta) node ships with n8n, so there is nothing to install and nothing extra to pay for the node itself, whether the workflow runs on n8n Cloud or on a self-hosted instance under the Community Edition and its Sustainable Use license. A workflow built on one runs the same way on the other, so a team can prototype on Cloud and move to its own server later without rewriting the trigger. What Figma itself costs is a separate question and depends on your own Figma setup.
      02What credentials or permissions does the Figma Trigger need?
      Two methods are supported: Access token and OAuth2. Both require a Figma account at admin or owner level, which is the part most people miss on the first try. The access token route uses a Personal Access Token generated in Figma and pasted into the n8n credential. The OAuth2 route needs an app registered on the Figma developer apps page when n8n is self-hosted, with the Client ID and Client Secret copied into n8n. Figma OAuth2 credentials use webhooks:read and webhooks:write by default, and a Custom Scopes slider lets you edit the Enabled Scopes list.
      03What are the limits of the Figma node in n8n?
      It depends on what you are trying to do. The catalog here is 5 events in 2 families, file and library, and one required Team ID, so a workflow always starts from team activity rather than from a lookup. Anything outside that catalog goes through HTTP Request, the generic n8n node that calls any endpoint of the Figma API while reusing the same credential through predefined authentication. One scoping detail matters in practice: File Deleted is counted file by file, so a folder removal does not report as an event for each file it contained. On the Figma side, webhooks need the paid Professional plan; the free Starter plan cannot deliver them, so the team has to be on a plan that supports it before the trigger receives anything.
      04Does the Figma Trigger react in real time?
      Yes. The Figma Trigger works by webhook, which is a URL that n8n registers with Figma when you activate the workflow and that Figma calls as soon as an event fires. Each event lands within seconds, and there is no polling interval to set, so nothing is being checked on a timer. One consequence to plan for: the webhook is registered at activation, so a workflow left inactive receives nothing at all, and events that happened while it was off do not queue up. Activate first, then test by acting in Figma.
      05n8n or Make for Figma automation?
      It depends on three criteria, not on which tool is better. Hosting: n8n runs on your own server through Docker or npm, or on n8n Cloud, while Make is hosted only, so teams with design files under an internal policy usually land on self-hosting. Cost model: Make bills per operation, which matters for a File Updated trigger that fires on every save. Visual logic: both draw the workflow on a canvas, and the choice often comes down to which editor your team reads faster after a month away from it.
      Same platform

      Other docs you might need on this stack.

      Browse all integrations