Figma

Read Figma files, export images, manage comments and reactions, browse teams and projects, and inspect components and styles from FlowRunner agents through the Figma REST API.

23 actions available

A design-review flow runs against a Figma file

Agent reads the file metadata and version to confirm it is current

Agent exports the relevant frames to images for the review record

Agent confirms each node rendered before assembling the summary

Agent checks the file's existing comments for open threads

Agent drafts the review comment and the exported assets

A person approves the comment before the agent posts it to the shared file

What This Integration Enables

The Figma connector reaches across files, images, comments, projects, and the design system. Agents read the full document tree or specific nodes, read lightweight file metadata and version history, and export nodes to PNG, JPG, SVG, or PDF, with an option to re-host the images in FlowRunner file storage for durable copies. They read the raw image fills in a file. On comments, agents read a file's comments, post comments and replies, delete comments, and read or add emoji reactions. They browse team projects and project files, and inspect the published component inventory: team components, file components, single components, component sets, and team and file styles. Get Me confirms the token. Webhook actions manage Figma v2 subscriptions, but the service does not wire event delivery to a FlowRunner trigger, so a receiving endpoint must be hosted separately. Most of these actions read; the writes touch a shared comment thread, and the surrounding flow decides which need a person.

Without FlowRunner

Exports done by hand Someone opens each frame and exports it for release notes or handoff

Design system tracked manually Components and styles get inventoried by clicking through the library

Review comments posted blind An automated comment could land on a shared file with no one reviewing the wording

With FlowRunner

Exports rendered in the flow The agent exports frames to durable copies as part of the flow

Design system synced Components, sets, and styles feed documentation and trackers automatically

Review comments gated A comment on a shared file pauses for approval before it posts

Use Case Scenarios

Release-Note Asset Export

When a new file version is published, the agent reads the version with Get File Versions, exports the changed frames with Export Image, and re-hosts the images in FlowRunner file storage for durable copies. It then assembles a design handoff page embedding the exported assets and the file metadata. The team stops exporting frames one at a time for every release.

Design System Inventory

The agent calls Get Team Components, Get Team Component Sets, and Get Team Styles to pull the published design system, then writes each component's name, key, and containing file into a tracking sheet. Get File Components narrows the same inventory to a single file when only one design is in scope. The inventory stays current without anyone clicking through the library.

Reviewed Design Comment

A review flow inspects a file, exports the frames in question, and drafts a comment summarizing what changed. Instead of posting straight to the shared file, the agent presents the draft for approval. On sign-off it calls Post Comment, pinning it to the right node. The reviewer keeps control of what lands on a file the whole design team can see.

Human-in-Loop Highlight

Reading a file, exporting frames, and inspecting the design system are safe reads that no one else sees. Posting a comment to a shared Figma file is different: every collaborator on that file sees the comment, it can pin to a specific node and start a thread, and a poorly worded automated note is awkward to walk back. Deleting a comment is worse, since it also removes the replies underneath it. This is [human-in-the-loop](/concepts/human-in-the-loop/) at the boundary between drafting a note and publishing it to a shared file. Before posting or deleting a comment on a shared file, the agent pauses, assembles the exact comment text and the node it would pin to, and routes to a person through their preferred channel. The message is specific: "This would post a review comment pinned to the Checkout frame in the Payments file, visible to everyone on it. Approve the wording, or edit it first?" The agent handles the reads, the exports, and the assembly; a person owns every note that reaches the shared file.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

23 actions

Files

Get File Retrieves the full document tree for a Figma file, including the node hierarchy, components, styles, and metadata, with depth and node filters for large files.
Get File Nodes Retrieves only the specified nodes from a file rather than the whole tree, for a lighter response when you know which frames or components you need.
Get File Metadata Retrieves lightweight metadata for a file (name, last-modified time, thumbnail, version) without the node tree, as a fast freshness check.
Get File Versions Retrieves the version history of a file, listing each saved version with its label, description, time, and author.

Images

Export Image Renders one or more nodes to PNG, JPG, SVG, or PDF and returns image URLs. With Save To Storage enabled, images are re-hosted in FlowRunner file storage for durable copies.
Get Image Fills Retrieves download URLs for the images used as fills within a file, the raw uploaded images referenced by node fills.

Comments

Get Comments Retrieves all comments on a file, including message text, author, time, resolution status, and pin location.
Post Comment Posts a new comment on a file or a reply to an existing comment, optionally pinned to a node or canvas position. Comments on shared files route through human review.
Delete Comment Permanently deletes a comment from a file. Only the comment's author can delete it, and deleting a top-level comment removes its replies.
Get Comment Reactions Retrieves the emoji reactions on a specific comment, including the reacting user.
Add Comment Reaction Adds an emoji reaction to a comment, using a Figma-supported shortcode.

Projects

Get Team Projects Lists the projects belonging to a Figma team, taken from the team ID in a team URL.
Get Project Files Lists the files within a project, returning each file's key, name, thumbnail, and last-modified time.

Components and Styles

Get Team Components Lists the published components in a team's libraries, paginated, with key, name, description, and containing file.
Get File Components Lists the published components defined within a single file, scoped to that file.
Get Component Retrieves full metadata for a single published component by its key, including its containing file and component set.
Get Team Component Sets Lists the published component sets (variant groupings) in a team's libraries, paginated.
Get Team Styles Lists the published styles (color, text, effect, grid) in a team's libraries, paginated.
Get File Styles Lists the published styles defined within a single file, scoped to that file.

User and Webhooks

Get Me Retrieves the profile of the user who owns the configured access token, useful as a connection check.
List Webhooks Lists the Figma v2 webhook subscriptions visible to the token. These operations manage subscriptions only; event delivery is not wired to a FlowRunner trigger.
Create Webhook Creates a Figma v2 webhook that posts events to an external HTTPS endpoint you host and secure. Delivery is not wired to a FlowRunner trigger.
Delete Webhook Deletes a Figma v2 webhook by its ID, stopping future event deliveries to its endpoint.

Start building with Figma

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us