Webhooks in Contentful help responding to events such as "an entry was edited", "an asset has been published/unpublished", and similar.
Whenever an event like that occurs, you can set up a webhook that would call the specified URI in order to somehow react: for instance, you can send a notification to a Slack channel every time an entry has been edited to keep up with the changes.
Webhooks greatly extend integration possibilities provided by Contentful.
Go to Settings → Webhooks from the navigation bar at the top. Hit Add webhook, put in the credentials of the remote host and configure the rest (whatever is necessary in your environment) – and you're done.
Note that you can fine-tune the events on which the webhooks are called.
Note that the "Save" webhook is triggered when the entry (or an asset) has been saved with an API call, and "Autosave" is triggered when it's been autosaved in the UI.
For specific details on what's included in the HTTP request, please refer to the developer documentation.
All the webhooks you've created are always present on the main Webhooks screen.
Please note that there's a per-space limit of 20 webhooks.
To help you see how the webhooks are doing and to make sure that they work as expected, we show the status of every webhook call in the activity log. Click on a webhook, and the activity log will appear.
To see the request details (including the complete JSON) and the remote server response, click "View details".
Please refer to the developer documentation for the specific implementation details.