Incoming design request
Receive a JSON submission from your existing form backend at this Workflow's private webhook URL.
Ready-made Workflow
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.
What gets copied
FastHook recreates every Step, route, field mapping, and setting with new IDs in your workspace.
Receive a JSON submission from your existing form backend at this Workflow's private webhook URL.
This endpoint fetches the version history of a file, allowing you to see the progression of a file over time. You can then use this information to render a specific version of the file, via another endpoint.
Before activation
Send JSON submissions from your existing backend to the private webhook URL created in your Draft. No Webhook account is needed.
Connect your own Figma account and review the provider settings used by this Workflow.
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.
Questions
No. FastHook creates a disconnected Draft. Connect your own Figma accounts before activation.
Yes. The copied Workflow is an editable Draft. Review every Step, input, mapping, and route before you activate it.
FastHook recreates the Trigger configuration, Action Steps, routes, and mappings with new IDs. Provider accounts, credentials, and secrets are never copied.
Only after you connect the required accounts, finish the configuration, and explicitly activate the Draft.