How to Test Figma Webhooks
Figma webhooks notify your application when files are updated, comments are added, and library components change.
Looking for the broader picture? See the 7 best webhook testing tools (2026), or if you're already on Webhook.site, the 60-second migration to HookRay.
Figma Official Webhook Docs1. Figma Webhook Events
Figma can send the following webhook events to your endpoint:
FILE_UPDATEFILE_VERSION_UPDATEFILE_COMMENTFILE_DELETELIBRARY_PUBLISH2. Set Up a Test Endpoint with HookRay
Follow these steps to start receiving Figma webhooks for testing:
- Go to HookRay and click "Start Testing — Free" to get your unique webhook URL.
- Copy the URL (e.g.,
https://h.hookray.com/abc123). - In your Figma dashboard, navigate to the webhook settings and paste the HookRay URL as your endpoint.
- Select the events you want to receive (see list above).
- Trigger a test event — HookRay will show the incoming webhook in real-time.
3. Sample Figma Webhook Payload
Here's an example of what a Figma webhook payload looks like:
{
"event_type": "FILE_UPDATE",
"file_key": "abc123XYZ789",
"file_name": "Design System Components",
"triggered_by": {
"id": "12345",
"handle": "designer"
},
"timestamp": "2026-03-20T18:00:00Z",
"passcode": "webhook_passcode_123",
"webhook_id": "wh_abc123"
}4. Frequently Asked Questions
How do I test Figma webhooks without deploying?
Use HookRay to get an instant public webhook URL. Paste it into your Figma dashboard's webhook configuration, trigger an event, and watch the payload arrive in real time. No code, no ngrok, no deployment required. The free tier captures 100 requests per month and works on all Figma event types.
Why aren't my Figma webhooks arriving?
The four most common causes: (1) the endpoint URL isn't publicly accessible — Figma can't reach localhost; (2) the wrong events are subscribed in your Figma dashboard; (3) signature verification is rejecting the request before your handler runs; (4) Figma can't reach your server because of a firewall, expired SSL certificate, or wrong DNS. Use HookRay's URL to isolate which of these four is failing — if HookRay receives the webhook, the problem is in your handler. If HookRay doesn't, the problem is in Figma configuration.
Why am I getting 400 or 500 errors from my Figma webhook?
Figma reports the response status your endpoint returned. HookRay accepts any payload and returns 200 OK by default, so if you see 400/500 in your Figma dashboard while pointing at HookRay, the issue is in Figma's configuration (wrong event, malformed signing secret, etc.). If you point at your own endpoint and get 400/500, the issue is in your handler — capture the request with HookRay, replay it locally, and debug from the captured payload.
How do I verify Figma webhook signatures?
Figma signs each webhook request with a shared secret. Capture the raw headers and body using HookRay, then verify the signature in your application using Figma's SDK or a standard HMAC library. Once verification works against HookRay-captured data, you can safely deploy. Figma's docs (linked above) cover the exact signing algorithm.
Can I replay a captured Figma webhook?
Yes — HookRay's replay feature re-sends any captured webhook to a different endpoint with one click. This is the fastest way to fix a buggy handler: capture the payload once, fix your code, and replay until it works. No need to re-trigger the event in Figma.
5. Next Steps
- Use HookRay's webhook replay feature to re-send captured webhooks while building your handler
- Enable smart parsing (Pro plan) to see Figma-specific fields highlighted automatically
- Check the Figma webhook documentation for the complete event reference
Ready to test Figma webhooks?
Get a free webhook URL in 5 seconds. No signup required.
Start Testing Figma Webhooks — FreeFree PDF: Webhook Testing Cheat Sheet 2026
One-page reference for 50+ APIs — canonical events, signing methods, sample payloads. Print it, pin it, share it.
📄 Download the cheat sheet (PDF, 180KB)