FILE_VERSION_UPDATE not triggered

same here, need an answer too😥

I’ve never got an answer here or with the ticket I’ve submitted so here’s my workaround if it can help you : 

• Create cron to trigger your workflow every X minutes 
• Get your projects from Figma API
• Get your project’s files from Figma API
• Filter only recent files 
• Get file version from Figma API
• Detect only new versions from these files
• Use a code node to filter the auto-saves out

Thank you!! Hope they’ll fix it soon!!😢 

Same issue here: the webhook triggers only when:

-  it is created

- it’s the first time a “version” is created right after the webhook was created => after that, the webhook is never triggered again.

Hey ​@Remy_Guestereguy ​@Chaine_ ​@valentinrichard Thanks for the post and for sharing your details 🙌 

I want to make sure I am understanding the issue. I created a test using my Figma account and webhook.site so I didn’t have to fuss with middleware for a quick test.

Here's what I set up:

• Registered three FILE_VERSION_UPDATE webhooks via POST /v2/webhooks — one each for team, project, and file context, all pointing at the same endpoint (a webhook.site URL)

• Confirmed all three came back ACTIVE and received the initial PING (HTTP 200) — the endpoint is reachable and the round trip works

• In a file inside that team/project, saved four named versions a few minutes apart (verified each exists via GET /v1/files/:key/versions, so they're server-side named versions, not autosaves)

• Checked the delivery log at GET /v2/webhooks/:id/requests for each webhook 🚨The GET webhook requests endpoint is super useful 🚨

Result: For every named version created after the webhooks were active, my /requests log shows zero FILE_VERSION_UPDATE attempts — only the original PING. Nothing arrived at the endpoint either, on any of the three contexts. I waited 40-plus minutes to try to deal with any latency. 

Is this close to how you are doing it?

Thanks for the additional information! — Jaycee

Hi ​@Jaycee Lewis 
 

You're right:

- when registering a `FILE_VERSION_UPDATE` webhook, then creting a new "version" on a figma file, the webhook does not trigger.
  Or to be more precise: it **may** trigger: in 5min, 4h, 4d, never (mostly never). Moreover, when creating multiple consecutive versions, the webhook may or may not trigger - in order or not (mostly in random order)
- a call to `/v1/files/${file_key}/versions` shows that manual versions have been created.
- a call to `/v2/webhooks/${webhook_id}/requests` shows that no `FILE_VERSION_UPDATE` has been trigerred.
- the `PING` always trigger as expected.
 

Thank you ​@valentinrichard 🙌 I’m going to work on geting this to my internal resources. I’ll post back here as needed. I appreciate the assist on this one. — Jaycee 

Hey, ​@valentinrichard 👋 If I open a support ticket, would you be willing to share your example and any additional details they may need? This will help a lot with getting this tracked. My guess is yes, and I don’t want to assume and then you end up with a surprise support ticket. Talk soon! — Jaycee

Yes, you can share my example, and if required, I’, glad to help.

Hey, ​@valentinrichard 👋 Apologies for the crossed wires on support tickets last week. I will open a ticket with your details and repro details from above. I’ll follow up here and add the ticket ID and email subject line for our support case. Thanks again and talk soon! – Jaycee