Skip to content
Start in the sandbox
All connectors
Figma logo

Figma

Content creation & media

Move briefs, assets and sign-offs through Figma without chasing between tools.

27 ways to read, 5 ways to write, each write switched on by you.

Try this in the sandboxBring us a workflow

Quality checks

Built and tested with example responses.

  1. Ready to connect: doneEvery listed action is built in.
  2. Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
Figma with Nexra

Connected, approved, proven.

The things teams do most with Figma, an example flow with a person in the loop, and what Nexra keeps as proof.

Top actions

  • React to commentcomment_reactions.createApproval by rule
  • Post commentcomments.createApproval by rule
  • List comment reactionscomment_reactions.listRead

Example flow

  1. Figma · List comment reactionscomment_reactions.listDone
  2. Figma · React to commentcomment_reactions.createMaker-checker
  3. Nexra · Record the decision and result in the evidence chainProven

Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches Figma.

What gets logged

  • Whether it ran on its own or who approved it, and under which rule
  • A fingerprint of the exact request sent to Figma
  • Figma's reply: what it created or changed
  • One entry in the evidence chain, linked to the one before

Try this in the sandbox

Run the whole flow with test data in your sandbox, then connect your own account when you are ready to go live.

Try this in the sandboxBring us a workflow

For developers

Technical detail

Figma REST API: read files, nodes, versions, folders, library components and styles, variables and webhooks; post comments and reactions; manage Dev Mode resources; write variables (Enterprise).

Figma, Inc. API docs
Source actions
27
Destination actions
5
Data types
27

What you can map

Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.

comment reactions2
  • React to commentDestinationProvider duplicate protectionApproval before production

    Add an emoji reaction to a comment.

  • List comment reactionsSource

    Emoji reactions on a comment.

comments2
  • Post commentDestinationNot retried automaticallyApproval before production

    Post a comment on a file, optionally pinned to a node or as a reply.

  • List commentsSource

    Comments and replies on a file.

component sets1
  • Get component setSource

    Metadata for one published component set by key.

components1
  • Get componentSource

    Metadata for one published component by key.

dev resources3
  • Create dev resourceDestinationNot retried automaticallyApproval before production

    Attach a Dev Mode link (for example a ticket or Storybook URL) to a node.

  • List dev resourcesSource

    Dev Mode links attached to nodes in a file.

  • Update dev resourceDestinationProvider duplicate protectionApproval before production

    Rename a dev resource or change its URL.

file component sets1
  • List file component setsSource

    Published component sets in a file library.

file components1
  • List file componentsSource

    Published components in a file library.

file metadata1
  • Get file metadataSource

    Lightweight file metadata: name, folder, last touched, creator, role and link access.

file nodes1
  • List file nodesSource

    Specific nodes from a file with their type, name and direct children.

file styles1
  • List file stylesSource

    Published styles in a file library.

file versions1
  • List file versionsSource

    Version history of a file, newest first, with labels and authors.

files1
  • Get fileSource

    File name, role, editor type, version, thumbnail and pages.

folder files1
  • List folder filesSource

    Files directly in a folder (formerly project files), optionally with branches.

image renders1
  • Render node imagesSource

    Render nodes to PNG, JPG, SVG or PDF and return Figma-hosted image URLs.

local variables1
  • List local variablesSource

    Variables created in a file (and remote variables it uses), with values per mode.

published variables1
  • List published variablesSource

    Variables published from a library file (no mode values).

styles1
  • Get styleSource

    Metadata for one published style by key.

subfolders1
  • List subfoldersSource

    Direct subfolders of a folder.

team component sets1
  • List team component setsSource

    Published component sets in a team library.

team components1
  • List team componentsSource

    Published components in a team library.

team folders1
  • List team foldersSource

    Top-level folders (formerly projects) in a team that the token can see.

team styles1
  • List team stylesSource

    Published styles in a team library.

users1
  • Get token ownerSource

    The authenticated user's ID, handle, avatar and email.

variable collections1
  • List variable collectionsSource

    Local variable collections in a file with their modes.

variables1
  • Create or update variablesDestinationNot retried automaticallyApproval before production

    Create or update variable collections, modes and variables, and set mode values, in one request (Enterprise).

webhook requests1
  • List webhook deliveriesSource

    Deliveries sent by a webhook in the last week, with response status and errors.

webhooks2
  • Get webhookSource

    One webhook's event type, context, status and endpoint.

  • List webhooksSource

    Webhooks on a team, project or file, or every webhook on a plan.

Access and limits

Authentication
Figma personal access token
Plans and access
Any Figma account can create a personal access token. Variables require Enterprise (writes need an Editor seat); limits depend on plan and seat type. The token sees what its user can see. Team IDs cannot be discovered through the API; copy them from the team URL.
Test environment
Figma has no sandbox. Use a token from a test account or a dedicated team with sample files.
Rate limits
Leaky-bucket limits per user and plan in three tiers: tier 1 (files, nodes, image renders) 10-20 per minute for Dev and Full seats; tier 2 (comments, dev resources, versions, folders, webhooks, variables reads) 25-100 per minute; tier 3 (library, users, metadata, variable writes) 50-150 per minute. View and Collab seats are much lower. HTTP 429 carries Retry-After in seconds; Nexra waits only for short delays.
Pagination
Versions and comment reactions follow pagination.next_page; team components, component sets and styles use page_size and a numeric after cursor; other lists return one page.
Provider events
Figma Webhooks V2 (FILE_UPDATE, FILE_VERSION_UPDATE, FILE_DELETE, LIBRARY_PUBLISH, FILE_COMMENT, DEV_MODE_STATUS_UPDATE) on a team, project or file. Nexra reads existing webhooks and their recent deliveries. Flows run on demand, on a schedule, or when a scheduled check finds new or changed records.

Before you build a flow

  • No deletes: comments, reactions, dev resources, webhooks, variables, modes and collections are never deleted. Variable writes refuse DELETE actions.
  • Webhooks are read only; Nexra does not create, update or pause them. Webhook passcodes are never returned.
  • Figma's file JSON can be very large. files.get returns file metadata with its pages (depth 1 by default, at most 4); use file_nodes.list for specific nodes.
  • Image renders return Figma-hosted URLs that expire after 30 days; downloading the image is an engine gap.
  • Projects are now folders: the v1 team projects and project files endpoints are deprecated, so Nexra uses the v2 folder endpoints. Folder metadata (GET /v2/folders/{id}/meta) needs a plan access token or OAuth and is not offered with a personal access token.
  • Variables endpoints are available only to full members of Enterprise organisations; variable writes also need an Editor seat.
  • OAuth apps, plan access tokens, activity logs, developer logs, payments, AI usage, library analytics and image fills are not implemented.
  • Figma has no updatedSince filter. Use lastModified from file metadata or file versions to detect changes.
  • Comment replies cannot be nested: a reply's commentId must be a top-level comment.

Developer reference

  1. Create the Figma, Inc. credentials described above with the narrowest permissions your flows need.
  2. In Nexra, open Connect, then Connections, then New connection, choose Figma, enter its settings and credentials, and tick only the write actions you need. Connection guide
  3. Test the connection, then use its actions as flow sources and destinations. Flow guide
Figma, Inc. docsAPI referenceFigma, Inc. docsAuthenticationFigma, Inc. docsRate limitsFigma, Inc. docsWebhooks

Machine-readable detail: GET /api/public/connect/connectors/figma and the Connections API.