ANTE User ManualWebhooks
The Webhooks page lets you send automatic notifications to another website or system whenever your CMS content changes — for example, when a new article is published or an item is updated.
Overview
A webhook is a connection that points to a web address (URL) you provide. When one of the events you've chosen happens in the CMS, the system sends a notification to that address. This is useful for keeping an external website, app, or service in sync with your content without anyone having to update it by hand.
From this page you can create new webhooks, edit existing ones, turn them on or off, send a test notification, and delete webhooks you no longer need.
To open it, go to CMS → Webhooks.
Page Layout
If you have no webhooks yet, the page shows a No webhooks configured message inviting you to create one.
Once you have webhooks, each one appears as a card showing:
- The webhook name and an Active / Inactive status badge
- The target URL the notifications are sent to
- The events that trigger it, shown as small tags
- The content types it applies to, if any are linked
- A footer showing when it was last triggered (or Never triggered), and a failure count if any notifications have failed
Each card also has these action buttons:
| Button | What it does |
|---|---|
| Test | Sends a test notification to the URL right now and reports whether it succeeded |
| Disable / Enable | Turns the webhook off or on. The button label matches the current state |
| Edit | Opens the webhook so you can change its name, URL, or events |
| Delete | Removes the webhook permanently |
A Create Webhook button sits at the top right of the page.
Field Reference
When you create or edit a webhook, you fill in this form:
| Field | Required | Description |
|---|---|---|
| Webhook Name | Yes | A name to identify the webhook, e.g. Content Notification |
| URL | Yes | The web address that notifications are sent to, e.g. https://example.com/webhook |
| Events (comma-separated) | Yes | One or more events that trigger the webhook, separated by commas, e.g. entry.create, entry.update, entry.delete, entry.publish |
At least one event must be entered. If the name, URL, or events are missing, the system shows a message asking you to fill them in before saving.
Common Tasks
Creating a Webhook
- Click the Create Webhook button at the top right.
- In the dialog, fill in the form:
- Webhook Name (required) — a name for the webhook.
- URL (required) — the web address to notify.
- Events — type the events that should trigger the webhook, separated by commas.
- Click Create.
- The new webhook appears as a card in the list, set to Active.
Editing a Webhook
- On the webhook's card, click Edit.
- Change the Webhook Name, URL, or Events as needed.
- Click Update to save your changes.
Testing a Webhook
- On the webhook's card, click Test.
- The system immediately sends a test notification to the webhook's URL.
- A message confirms whether the test succeeded or failed. A failed test usually means the URL is unreachable or returned an error — check that the address is correct and the receiving system is online.
Enabling or Disabling a Webhook
- Click Disable on an active webhook to stop it from sending notifications. The status badge changes to Inactive.
- Click Enable on an inactive webhook to start it again. The status badge changes to Active.
A disabled webhook stays in your list but does not send any notifications until you enable it again.
Deleting a Webhook
- On the webhook's card, click Delete.
- A confirmation dialog warns that the action cannot be undone.
- Click Delete to confirm, or Cancel to keep the webhook.
Tips
- Use Test before you rely on it — sending a test notification confirms the receiving system can accept the webhook before real content events happen.
- Watch the failure count — if a card shows failures, the target URL may be down or incorrect. Test the webhook to check.
- Disable instead of deleting — if you only need to pause notifications temporarily, disable the webhook rather than deleting it, so you don't have to set it up again later.
- Check "Last triggered" — the footer tells you when the webhook last fired, which helps you confirm it is working.
Related Pages
- Content Manager — Manage your content
- Content Type Builder — Define your content types
- API Tokens — Manage access tokens for external systems
💡 Note: A webhook only notifies an external system that something changed — it does not send the content itself. The receiving system decides what to do with each notification.