notifications-webhooks

What problem does it solve?

This Skill explains how Madoc TS webhook routes are wired, how webhook definitions are registered, and how webhook URLs are signed and validated to prevent delivery failures, mismatched events, and signature errors.

Core Features & Use Cases

• Router and endpoints: Describes CRUD, execution, and testing routes registered in services/madoc-ts/webhooks/router.ts and how to extend them.
• Registry and extensions: Explains WebhookExtension and WebhookServerExtension behavior for registering definitions, plugin overrides, and listing/management of webhooks.
• Signing and validation: Covers generation of JWS-signed webhook URLs, signature validation against public keys, expiration windows, and the public execution endpoint at /s/:slug/madoc/api/webhook.
• Use Case: Add a new outgoing event, ensure the signed URL generation matches client expectations, and validate incoming webhook requests from registered plugins.

Quick Start

Generate a signed webhook URL using the WebhookServerExtension.register flow, then validate the signature and execute a test payload against the /s/:slug/madoc/api/webhook endpoint.