I would add to this also getting webhook events when a site is reverted to a prior version, which breaks CMS collections, and so requires re-syncing CMS collection IDs to any externally kept data. If there was a webhook event for that, I could automatically trigger a re-syncing process.

Shipped—API and Webfhook updates

• Item Unpublish Webhook - The collection_item_unpublishedwebhook has been added so you can be notified when an unpublish is triggered.

• Site Publish Webhook - The site_publish webhook now includes domains and publishedBy, so you don’t have to wonder anymore who and what was published.

Look forward to the above updates to publishing webhook.

I agree on all accounts as well!

Plus, if you wanna be extra nice, include your webflow.com domain as a HTTP referrer in the header, so I can whitelist you guys. Right now I am just receiving your always different AWS IP addresses as sender info.

C&P of my question on yor Discord, Brendan sent me here.
oliver-didntbreak-comYesterday at 12:05 PM

Hi, in your webhook events could you please include an indication about the destination that it deployed to? Ideally the URL host name. http://developers.webflow.com/#trigger-types[12:07 PM]rn I don't have a way of telling whether the deployment went to "projectname.webflow.io" or my actual domain (or both), is that correct or am I missing something?

I agree on all counts ! But I put emphasis on which DOMAIN the publish action happened to and also whether UN-publish or PUB-lish : )

Please please please!