Content events

Content Events

Webhooks from these core entities are most commonly used to monitor when the state of any content from your space has been edited or updated.

Type / Action	`create`	`save`	`auto_save`	`archive`	`unarchive`	`publish`	`unpublish`	`delete`	`complete`
`ContentType`	Yes	Yes	No	No	No	Yes	Yes	Yes	No
`Entry`	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	No
`Asset`	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	No
`Task`	Yes	Yes	No	No	No	No	No	Yes	No
`Comment`	Yes	No	No	No	No	No	No	Yes	No
`Release`	Yes	Yes	No	Yes	Yes	No	No	Yes	No
`Workflow`	Yes	Yes	No	No	No	No	No	No	Yes
`Template Installation`	No	No	No	No	No	No	No	No	Yes

Common use cases for content event webhooks include:

running a test suite on a CI service when the content model of a development environment was changed
deploying a production build when content was published or un-published
deploying a preview build when the draft state of content has changed
re-building a search index when content was updated
feeding assets into an image detection service when they are uploaded
trigger email or chat authentication notifications due to editing activity
communicating creation and updates on tasks to the right stakeholders in real time