Figma Trigger

Start workflow from Figma team events

Overview

Starts a workflow when events occur in a Figma team. Listens for file comments, file updates, file deletions, file version updates, and library publishes via Figma Webhooks V2 API. Requires a Figma personal access token and a Team ID. Each trigger instance subscribes to one event type at the team level.

Category: Development
Tool Name: figma_trigger
Version: 1

Appearance: Icon: si-figma | Color: #a259ff

Node Type

Trigger — webhook (receives incoming HTTP callbacks)

Input / Output

Direction	Port(s)
Input	None (trigger node)
Output	Output

Credentials

This tool requires Figma API credentials. See the Credentials Guide for setup instructions.

Parameters

Parameter	Type	Required	Default	Description
Team ID	string	Yes	—	The Figma Team ID to monitor. Found in the URL of a Figma Team page: figma.com/files/team/{TEAM-ID}/.
Trigger On	options	Yes	—	Which Figma event type to listen for.
				Options: fileComment (someone comments on a file), fileDelete (a file has been deleted — does not fire for the files inside a deleted folder), fileUpdate (a file saves or is deleted; happens when a file is closed or within 30 seconds after changes), fileVersionUpdate (a named version is created in a file’s version history), libraryPublish (a library file is published)

Output Data

Each delivery from Figma produces one output item. The webhook payload is copied onto the item unchanged, and three fields are added:

• _trigger — always figma_trigger_webhook
• _timestamp — ISO 8601 timestamp of when the request arrived
• _webhookEvent — the Figma event type, taken from the payload’s event_type field

The Figma payload itself carries:

• event_type — the event, e.g. FILE_COMMENT
• timestamp — the Figma event time
• webhook_id — the Figma webhook that delivered the event
• file_key, file_name — the file the event is about
• comment, comment_id, parent_id, order_id — comment detail, on comment events
• triggered_by — the Figma user who caused the event, with handle, id, and img_url

Figma’s PING health checks are acknowledged without starting the workflow, and each delivery’s passcode is verified before any item is produced.

Reference the payload downstream by expression, e.g. {{ $json.file_name }} or {{ $json.triggered_by.handle }}.

Usage Examples

• trigger workflow when someone comments on a Figma file
• start when a Figma file is updated
• listen for Figma file deletions
• detect when a new file version is created in Figma
• watch for Figma library publishes

Example Configuration

Fire when someone comments on a file in the team:

{
  "type": "figma_trigger",
  "parameters": {
    "teamId": "123456789",
    "triggerOn": "fileComment"
  }
}

Fire when a named version is created:

{
  "type": "figma_trigger",
  "parameters": {
    "teamId": "123456789",
    "triggerOn": "fileVersionUpdate"
  }
}

Fire when a library is published:

{
  "type": "figma_trigger",
  "parameters": {
    "teamId": "123456789",
    "triggerOn": "libraryPublish"
  }
}

Trigger Behavior

• Activation: When the workflow is activated, a webhook endpoint is registered with the service.
• Deactivation: The webhook is automatically unregistered when the workflow is deactivated.
• Payload: The incoming webhook payload is parsed and output as workflow items.
• Verification: Supports signature verification where applicable.

Tips

Entry point that fires when a Figma team event occurs. Subscribe to file comments, updates, deletions, version updates, or library publishes. Outputs the full Figma webhook payload for downstream processing.