Event Hooks
Event Hooks are outbound webhooks that fire when something happens in your project—such as an entry being published or a workflow transition. Each hook runs an action that either sends an HTTP request to a URL you specify or posts a message to a Slack channel.
Use Event Hooks to integrate Contismo with external systems: invalidate caches, sync data to other platforms, trigger builds, or notify your team in Slack.
Create an Event Hook
Section titled “Create an Event Hook”- Go to Settings → Event Hooks.
- Click Create Event Hook.
- Enter a name that identifies what the hook does.
- Choose a Trigger (see the table below).
- Optionally limit the hook to specific content models.
- Choose an Action — HTTP or Slack.
- Configure the action details and save.
Creating and managing Event Hooks requires the appropriate webhook permissions on your role.
Triggers
Section titled “Triggers”| Trigger | Fires when | | ------- | ---------- | | Entry Created | A new entry is created. | | Entry Updated | An existing entry is saved. | | Entry Published | An entry goes live. | | Entry Unpublished | A live entry is taken offline. | | Entry Moved to Trash | An entry is deleted (moved to trash). | | Entry Restored | A trashed entry is restored. | | Entry Permanently Deleted | An entry is permanently removed from trash. | | Workflow Transitioned | An entry moves to a new workflow state. |
You can optionally restrict a hook to one or more content models so it only fires for matching entries.
HTTP Actions
Section titled “HTTP Actions”An HTTP action sends a request to a URL you provide when the trigger fires.
Configure:
- URL — the endpoint that receives the request.
- Method — POST, PUT, or PATCH.
- Headers — custom headers sent with the request. Mark sensitive values as secret to store them encrypted.
- Signing Secret (optional) — when set, requests include an
X-EventHook-Signatureheader with an HMAC-SHA256 signature your endpoint can verify.
Your endpoint should respond with a success status code. Failed deliveries are recorded in the hook’s delivery log.
Slack Actions
Section titled “Slack Actions”A Slack action posts a formatted message to a Slack channel when the trigger fires.
Before you can use a Slack action:
- Connect Slack for the project — see Slack.
- When creating the Event Hook, choose Slack as the action and select a channel.
Delivery Logs
Section titled “Delivery Logs”Each Event Hook has a delivery log showing recent attempts—whether they succeeded or failed. From the Event Hooks list, click View Logs on a hook to inspect individual deliveries.
Use logs to debug integration issues, such as incorrect URLs, authentication failures, or Slack channels that are no longer available.
Permissions
Section titled “Permissions”Event Hooks are managed under Settings → Developers. Team members need webhook capabilities to list, create, update, or delete hooks. Slack actions additionally require Slack to be connected by someone with the Manage Integrations permission.
Related
Section titled “Related”- Slack — connect a Slack workspace for Slack actions.