Webhook Notifier
Send outbound webhook notifications when content changes inside EmDash CMS.
Plugin
Webhook Notifier
Send outbound webhook notifications when content changes inside EmDash CMS.
Product Details
- Category
- Automation
- Status
- available
- Version
- Included in beta
- Price
- Included in beta
- License
- MIT
- Release Date
- TBD
- Compatibility
- EmDash CMS beta preview
- Maintainer
- EmDash CMS Team
Links
Webhook Notifier lets EmDash push signals to downstream systems when content changes—search indexing, chat notifications, CI pipelines, or custom review tools. The implementation is in packages/plugins/webhook-notifier.
Installation
- Choose receiving endpoints that use HTTPS and authenticate requests (shared secret, HMAC signatures, or mTLS—match what the plugin supports in your version).
- Enable the plugin in admin and register your first endpoint URL in a non-production project.
- Trigger a test event (for example, save a draft post) and confirm the receiver logs the payload you expect.
Configuration
Common settings include:
- Event filters — which collections or transition types fire webhooks (create, update, publish, delete).
- Payload shape — JSON bodies often include id, slug, timestamps, and actor; confirm against the plugin’s documented schema.
- Retry policy — exponential backoff versus dead-letter behavior when the receiver is down.
Example (conceptual): your indexer might expect a POST with a JSON body like:
{
"event": "publish",
"collection": "posts",
"slug": "launch-notes",
"url": "https://example.com/blog/launch-notes",
"occurredAt": "2026-04-04T12:00:00.000Z"
}Replace keys and URLs with what your release actually emits—verify against live logs before relying on this in production.
Usage scenarios
- Search — notify Algolia, Typesense, or an internal indexer to re-fetch changed URLs.
- Slack or Teams — lightweight alerts for editors when high-visibility pages update.
- Deployment hooks — trigger static rebuilds or cache purges in edge networks when content publishes.
Operational tips
- Log delivery failures and alert on sustained error rates.
- Rotate shared secrets on the same schedule as other integration credentials.
- Avoid infinite loops—do not let a webhook handler write back into EmDash in a way that retriggers itself unless you guard with idempotency keys.