Design
Automate work across your stack
Connect Figma to FastHook to read design files, comments, versions and libraries, and route design information into your workflows.
Choose an app
Figma + FastHook + your toolsWebhook · Figma
Send a JSON webhook with a Figma file_key. Connect Figma and activate the Workflow to retrieve one page of named file versions. The response is available to later Workflow steps. Add a destination or filter before using the data outside FastHook. Supply page_size, before or after to navigate additional pages; access depends on the connected account and plan.
Webhook · Figma
Send a JSON webhook with file_key and body, where body is a Figma comment request such as {"message":"Review this design"}. Connect Figma and select a file the connected account can edit. Activate only after checking the sender and content: the Action posts a real comment that may notify collaborators. Repeated requests or manual reruns can create duplicate comments.
Webhook · Figma · Slack
Send a JSON webhook with a Figma file_key. Connect Figma and Slack, select a Slack channel, and activate the Workflow. FastHook reads metadata for a file the connected Figma account can access, then sends its name and key to Slack. Protect the incoming webhook and avoid sending private design details to a channel that should not see them. Repeated requests or manual reruns can send duplicate messages.
Webhook · Figma · Slack
Send a JSON webhook with a Figma file_key. Connect Figma and Slack, select a Slack channel, and activate the Workflow. FastHook reads metadata for a file the connected Figma account can access, then sends its name and key to Slack. Protect the incoming webhook and avoid sending private design details to a channel that should not see them. Repeated requests or manual reruns can send duplicate messages.
Figma · Slack
Connect Figma and Slack. Enter the Figma file key in the Trigger and choose a Slack channel in the Action before activation. FastHook creates one file-level FILE_UPDATE webhook and removes its owned webhook when no active Workflow needs it. Messages include only file name and key, not design contents. Figma may send repeated events; manual reruns can duplicate Slack messages.
Choose a Figma Action in your Workflow, connect through OAuth and grant the requested scopes. Copy a file key from its Figma URL, then map the required Action fields. A published Figma OAuth application is required for other users to connect.
Connect your accounts and map the required fields from earlier steps. Test with data you control before activation.
The current catalog contains 35 Actions derived from the official Figma OpenAPI specification. Twenty-four other documented endpoints require scopes unavailable to this public team app, deprecated scopes or a different token type. Catalog coverage does not mean live execution was verified. For a Figma Trigger, enter the file key from its URL. FastHook creates one webhook per selected event and removes owned webhooks when the source stops. Team and project context events are outside the managed Trigger set; use Figma webhook Actions to configure those manually. Folders, variables, library analytics and organization activity log Actions are excluded because their OAuth scopes are private or absent from this app’s scope picker. Other endpoints may require an Enterprise plan, admin rights or edit access. Figma limits file-content requests heavily for View and Collab seats. Figma returns HTTP 429 with Retry-After. Use the documented pagination cursor or page fields, and avoid frequent polling on restricted plans. The API returns temporary image URLs; large files and binary image downloads are not exposed as FastHook File outputs in this release. Disconnecting removes the FastHook connection. Revoke the grant in Figma to end provider-side access.
Build your Workflow
Choose a Figma Action in your Workflow, connect through OAuth and grant the requested scopes. Copy a file key from its Figma URL, then map the required Action fields. A published Figma OAuth application is required for other users to connect.
Start workflows from five file-level Figma webhook events. Read file content, metadata, images, nodes and version history. List and post comments and reactions on accessible files. Read published library assets and content. Manage dev resources and webhooks where your role and plan permit
The current catalog contains 35 Actions derived from the official Figma OpenAPI specification. Twenty-four other documented endpoints require scopes unavailable to this public team app, deprecated scopes or a different token type. Catalog coverage does not mean live execution was verified. For a Figma Trigger, enter the file key from its URL. FastHook creates one webhook per selected event and removes owned webhooks when the source stops. Team and project context events are outside the managed Trigger set; use Figma webhook Actions to configure those manually. Folders, variables, library analytics and organization activity log Actions are excluded because their OAuth scopes are private or absent from this app’s scope picker. Other endpoints may require an Enterprise plan, admin rights or edit access. Figma limits file-content requests heavily for View and Collab seats. Figma returns HTTP 429 with Retry-After. Use the documented pagination cursor or page fields, and avoid frequent polling on restricted plans. The API returns temporary image URLs; large files and binary image downloads are not exposed as FastHook File outputs in this release. Disconnecting removes the FastHook connection. Revoke the grant in Figma to end provider-side access.
Choose a ready-made Figma Workflow, connect your accounts, and test it before activation.
Explore Figma Workflow templates
