# Webhooks - Events Webhook event notifications sent by ButterCMS when content changes occur in your account. ButterCMS automatically sends webhook notifications for various content events including blog posts, pages, and collection items. These events enable real-time integration with your applications, triggering immediate responses to content changes. **Event Types**: Webhooks are triggered for create, update, publish, unpublish, and delete operations across all content types. Each event includes comprehensive payload data about the content that changed. **Delivery Method**: All webhook events are delivered as HTTP POST requests to your configured endpoint URLs, with JSON payloads containing event metadata and complete content data. **Configuration**: Webhook events are configured per content type in your ButterCMS account settings. You can select which events to receive and configure different endpoint URLs for different event types. ## Page - Published - [POST page-published](https://api.docs.buttercms.com/webhooks-events/webhookpagepublished.md): Triggered when a page is published or republished. This event fires when: - A draft page is published for the first time - An already published page is republished after changes - A scheduled page is automatically published ## Page - Draft Saved - [POST page-draft](https://api.docs.buttercms.com/webhooks-events/webhookpagedraft.md): Triggered when a draft page version is saved. This event fires when: - A new page is created and saved as draft - An existing draft page is updated and saved - A published page is updated but not yet republished ## Page - Unpublished - [POST page-unpublished](https://api.docs.buttercms.com/webhooks-events/webhookpageunpublished.md): Triggered when a published page is unpublished (but not deleted). This event fires when: - A published page is deliberately unpublished but kept in the system - A page is temporarily taken offline without permanent deletion ## Page - Deleted - [POST page-delete](https://api.docs.buttercms.com/webhooks-events/webhookpagedelete.md): Triggered when a published page is permanently deleted. This event fires when: - A page is permanently removed from the system - A page is moved to trash and then permanently deleted ## Page - Any Activity - [POST page-all](https://api.docs.buttercms.com/webhooks-events/webhookpageall.md): Triggered when any activity occurs on a page (create, update, publish, unpublish, delete). This is a catch-all event that fires for all page changes, useful for comprehensive page monitoring and cache invalidation across all page types. ## Blog Post - Published - [POST post-published](https://api.docs.buttercms.com/webhooks-events/webhookpostpublished.md): Triggered when a blog post is published or republished. This event fires when: - A draft blog post is published for the first time - An already published post is republished after changes - A scheduled post is automatically published ## Blog Post - Draft Saved - [POST post-draft](https://api.docs.buttercms.com/webhooks-events/webhookpostdraft.md): Triggered when a draft blog post is saved. This event fires when: - A new blog post is created and saved as draft - An existing draft is updated and saved - A published post is updated and saved as draft (effectively unpublishing) ## Blog Post - Deleted - [POST post-delete](https://api.docs.buttercms.com/webhooks-events/webhookpostdelete.md): Triggered when a published blog post is unpublished or deleted. This event fires when: - A published blog post is moved to trash - A published blog post is permanently deleted - A published blog post is unpublished (soft delete) ## Blog Post - Any Activity - [POST post-all](https://api.docs.buttercms.com/webhooks-events/webhookpostall.md): Triggered when any activity occurs on a blog post (create, update, publish, unpublish, delete). This is a catch-all event that fires for all blog post changes, making it useful for general blog post monitoring and cache invalidation. ## Collection Item - Published - [POST collectionitem-published](https://api.docs.buttercms.com/webhooks-events/webhookcollectionitempublished.md): Triggered when a collection item is published or republished. This event fires when: - A draft collection item is published for the first time - An already published item is republished after changes - A scheduled item is automatically published ## Collection Item - Draft Saved - [POST collectionitem-draft](https://api.docs.buttercms.com/webhooks-events/webhookcollectionitemdraft.md): Triggered when a collection item draft is saved. This event fires when: - A new collection item is created and saved as draft - An existing draft item is updated and saved - A published item is updated but not yet republished ## Collection Item - Unpublished - [POST collectionitem-unpublished](https://api.docs.buttercms.com/webhooks-events/webhookcollectionitemunpublished.md): Triggered when a collection item is unpublished (but not deleted). This event fires when: - A published collection item is deliberately unpublished but kept in the system - An item is temporarily taken offline without permanent deletion ## Collection Item - Deleted - [POST collectionitem-delete](https://api.docs.buttercms.com/webhooks-events/webhookcollectionitemdelete.md): Triggered when a collection item is deleted. This event fires when: - A collection item is permanently removed from the system - A collection item is moved to trash and then permanently deleted ## Collection Item - Any Activity - [POST collectionitem-all](https://api.docs.buttercms.com/webhooks-events/webhookcollectionitemall.md): Triggered when any activity occurs on a collection item (create, update, publish, unpublish, delete). This is a catch-all event that fires for all collection item changes, useful for comprehensive content monitoring across all collections. ## Media - Video Uploaded - [POST media-videouploaded](https://api.docs.buttercms.com/webhooks-events/webhookmediavideouploaded.md): Triggered when a video file is uploaded to the media library. This event fires when: - A new video file is uploaded to ButterCMS media library - Video processing is completed and the file is available