> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://contentful.com/developers/docs/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://contentful.com/_mcp/server.

# Content events

> Reference for content events which trigger webhooks.

## 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.

| **Content Type**                                                                         | `create` | `save` | `auto_save` | `archive` | `unarchive` | `publish` | `unpublish` | `delete` | `complete` |
| ---------------------------------------------------------------------------------------- | -------- | ------ | ----------- | --------- | ----------- | --------- | ----------- | -------- | ---------- |
| [ContentType](/references/content-management-api/content-types)                          | ✅ Yes    | ✅ Yes  | ❌ No        | ❌ No      | ❌ No        | ✅ Yes     | ✅ Yes       | ✅ Yes    | ❌ No       |
| [Entry](/references/content-management-api/entries)                                      | ✅ Yes    | ✅ Yes  | ✅ Yes       | ✅ Yes     | ✅ Yes       | ✅ Yes     | ✅ Yes       | ✅ Yes    | ❌ No       |
| [Asset](/references/content-management-api/assets)                                       | ✅ Yes    | ✅ Yes  | ✅ Yes       | ✅ Yes     | ✅ Yes       | ✅ Yes     | ✅ Yes       | ✅ Yes    | ❌ No       |
| [BulkContentOperation](/references/content-management-api/bulk-entry-content-operations) | ✅ Yes    | ❌ No   | ❌ No        | ❌ No      | ❌ No        | ❌ No      | ❌ No        | ❌ No     | ✅ Yes      |
| [Task](/references/content-management-api/entry-tasks)                                   | ✅ Yes    | ✅ Yes  | ❌ No        | ❌ No      | ❌ No        | ❌ No      | ❌ No        | ✅ Yes    | ❌ No       |
| [Comment](/references/content-management-api/entry-comments)                             | ✅ Yes    | ✅ Yes  | ❌ No        | ❌ No      | ❌ No        | ❌ No      | ❌ No        | ✅ Yes    | ❌ No       |
| [Release](/references/content-management-api/releases)                                   | ✅ Yes    | ✅ Yes  | ❌ No        | ✅ Yes     | ✅ Yes       | ❌ No      | ❌ No        | ✅ Yes    | ❌ No       |
| [Entry version (for Timeline)](/references/content-management-api/timeline-releases)     | ❌ No     | ✅ Yes  | ✅ Yes       | ❌ No      | ❌ No        | ❌ No      | ❌ No        | ❌ No     | ❌ No       |
| [Asset version (for Timeline)](/references/content-management-api/timeline-releases)     | ❌ No     | ✅ Yes  | ✅ Yes       | ❌ No      | ❌ No        | ❌ No      | ❌ No        | ❌ No     | ❌ No       |
| [Workflow](/references/content-management-api/workflows)                                 | ✅ Yes    | ✅ Yes  | ❌ No        | ❌ No      | ❌ No        | ❌ No      | ❌ No        | ❌ No     | ✅ Yes      |
| [Template Installation](/references/content-management-api/content-model-templates)      | ❌ No     | ❌ No   | ❌ No        | ❌ No      | ❌ No        | ❌ No      | ❌ No        | ❌ No     | ✅ Yes      |

> **Info**
>
> Entry version (for Timeline) and Asset version (for Timeline) events are not available for all plans.

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

> Reference for content events which trigger webhooks.