OtherReal-timeUpdated May 2026

Figma

Figma file, comment, and version events

Figma's webhook v2 fires on the events that matter for design-engineering handoff workflows, and Tiny Command surfaces three: File Updated (any edit to a file you've subscribed to), Version Created (a named version saved — the discrete handoff moment), and Comment Added (a new comment thread, the design-review hook). Three actions cover reads and writes: Get File (returns the file's node tree, components, and styles), List Comments, and Post Comment. The connection uses a Figma personal access token at team scope; the webhook subscription is per-team (so any file in the team can trigger), with downstream filtering by file ID if needed. Comment Added is the design-review workflow trigger — when a designer leaves a comment on a frame, the workflow can post to #design-review in Slack with a deep-link back to the comment, or open a Linear issue if the comment matches a pattern like "[bug] ...". File Updated fires often (debounced 30 seconds) so it's better suited to "sync the latest file" workflows than "react to every edit."

Connect Figma See 3 triggers

3triggers

3actions

≈ 2 minto set up

Freetier · no card

Triggers

Workflows start when Figma does.

3 real-time triggers, each backed by a webhook subscription. Events arrive within seconds and you don't have to set up polling.

Real-time · webhook-driven

Trigger live

When figma comment added

Fires when a comment is posted on a Figma file (new thread or reply). The design-review hook — auto-post to #design-review Slack, create a Linear issue if comment matches bug pattern.

See what it returns →

Trigger live

When figma file updated

Fires (debounced ~30s) on any file edit. Useful for "design changed → re-export assets" or "design touched → notify the engineer who built the matching component" workflows. No diff in payload — workflows that need the change run Get File and compare.

See what it returns →

Trigger live

When figma version created

Fires when a designer saves a named version — the discrete handoff moment. The hook for design-to-engineering automation: when v1.0 is saved, auto-create the engineering issue, post the version link to the team.

See what it returns →

Actions

Do anything Figma can do, from a workflow.

Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.

Action	What it does	Inputs
Get Figma File	Returns the file's node tree (canvases, frames, components, text), styles, and components. For "extract design tokens for our design system" or "validate this design has the right structure" introspection workflows.	1 fields	View →
List Figma Comments	Returns all comments on a file with author, position, and status. Useful for "summarise feedback on this design" rollup workflows.	1 fields	View →
Post Figma Comment	Posts a comment to a Figma file at an optional anchor position. For "automated linting feedback on design submissions" or "cross-tool sync — when this Linear issue closes, comment on the linked Figma file".	2 fields	View →

Recipes

Pre-built Figma workflows.

Clone any recipe and customize it in one click. Every recipe is fully editable.

Figma → Slack alerts

AI-triage every Figma event, ping the right channel only when it matters.

Figma → Google Sheets log

Every event matching a filter, appended to a running spreadsheet.

Figma → Notion database

Turn Figma into a Notion-backed source of truth, auto-tagged.

Before you build

Three things worth knowing.

Filter at the trigger

Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.

Authorize once, reuse anywhere

Connect Figma once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.

No JSON to read

Every Figma field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.

FAQ

Questions about the Figma integration.

If we missed yours, ping support. We usually reply within an hour.

How do I connect Figma to Tiny Command?

Open the Tiny Command workflow builder, drop in a Figma node, and click Connect. Authorize Figma once and any workflow on your account can use its triggers and actions. Most teams finish the connection in under two minutes.

What Figma triggers does Tiny Command support?

Tiny Command supports 3 real-time Figma triggers, including "Figma Comment Added", "Figma File Updated", "Figma Version Created". Each trigger fires within seconds of the event happening in Figma.

What Figma actions can I run from a workflow?

3 Figma actions are available out of the box, covering other operations like "Get Figma File". Every action accepts dynamic inputs from upstream nodes, whether that's a search result, an AI output, or a form field.

Is the Figma integration real-time?

Yes. Figma Comment Added and every other Figma trigger uses webhooks or push subscriptions, so workflows fire within seconds of the event in Figma rather than on a polling schedule.

Do I need to write code to use Figma with Tiny Command?

No. Every Figma trigger and action is fully configurable from the visual workflow builder. For edge cases that aren't covered, drop in a custom HTTP node and call any Figma API endpoint directly.

How much does the Figma integration cost?

There's a free tier you can start on without a credit card. Higher run volumes and team features come with paid plans. The Figma integration itself has no per-app surcharge.