We are using all the deploy hooks, but what seems to be missing is a publish hook in the case a site has autopublish off. When a particular deployment is then published manually, there is no notification hook for such an event. This is necessary to fully keep track of deployment status in an external UI. Obviously the workaround would be to disallow login to the UI and make the publish request through the API, but it feels like an obvious oversight. Also the deployment records don’t make it obvious when a site was published other than the update_date changing. It would be nice to have a build_date and a publish_date where the publish date only changes when it’s really published and a preview_date when the preview URL is valid.
interesting idea, @richtera ! i wil try and get some 
on this for the future. thanks!
Also looking for this feature. (Publish hook)
Is this something which is planned for future release?
Hi @Simskii,
There’s a feature request, but we don’t know if/when it will be implemented. But we’ll update this thread in case it’s released.
Hi,
Has there been any updates for this feature request?
Thanks
Hi @kai.yang,
Unfortunately, nothing yet. But we’d update the thread if something changes.
This feature would be very useful. We would like to include this as part of Risk Mitigation and it’s causing us significant problems trying to mitigate this internally.
The ability to have notifications sent on publish/rollback is a very important feature we would like. Has there been any movement on this?
There’s no movement on this yet, I’m afraid. Could you please shed some light on:
We can include those details for the development team which can potentially make a better case in favour of this feature.
Sure!
We have no current way of knowing when a deployment has been published to our production sites other than to directly check Netlify. What we would like to know is if someone has published or rollbacked. This would be a “reporting” risk mitigation as we could notify certain stakeholders to verify that this was a correct publish/rollback.
It’s an awful thing to consider, but we need to be able to mitigate any potential damage that could be done by an unscheduled publish/rollback performed by a disgruntled employee, a bad actor, or even just a mistake.
It would be even better to be able to schedule these notifications to run during certain time frames, such as the weekend or non-working hours.
We have notifications for builds but those builds are benign until they have been published, so they’re a bit useful, but not what we’re trying to mitigate.
Thank you for sharing that. We’ve passed it on to the devs.
Has there been any movement on this? This would be an incredibly useful feature to add ontop of the current notification webhooks.
No, there’s no movement so far.