Webhooks are a way to notify other applications when a change happens.

You can use webhooks to connect IncludeCore to your custom backend, Zapier or any system that supports webhooks.

You can enable or disable it for each endpoint using the Manage webhooks & add-ons tab.

A webhook will be sent to the specified URL regardless of whether the change was made via the API or the CMS. If you choose to enable it for the GET request as well, and you don't specify an entry ID, an empty entry_id field will be sent.

Webhooks are sent for both API and CMS actions, and you can also choose to enable them for databases, static screens and global items. A typical use case for webhooks with static screens and global items is if your website is built statically and you need to trigger the build and deployment again when there's a change to a screen.

To verify that a webhooks request is coming from us, you can check that your project's webhooks key (which you can find in your project settings) matches the Authorization Bearer token that we attach to each webhooks request.

Webhooks format

    "action_method": "post",
    "component_name": "Contact Form",
    "component_id": 7261,
    "project_name": "Test",
    "project_id": 4843,
    "entry_id": 9251,
    "cms_action": true,
    "retrieve_url": "https://www.includecore.com/api/projects/4843/databases/7261-Contact%20Form/entries/9251"

Zapier flow example

Last updated