Subscribe to catalog drift with webhooks

Send signed model, catalog, and lifecycle changes to the systems that need to react without polling.

Why use webhooks

Webhooks turn catalog drift into an operational signal. Use them to open migration work, re-run a compatibility check, notify owners, or block a release when a deployment is deprecated or retired.

Create an endpoint

1. Expose a public HTTPS receiver that returns a successful status quickly.
2. Name the endpoint by destination and environment.
3. Enter the URL and select Add endpoint.
4. The app subscribes it to catalog changes plus lifecycle deprecation and retirement events.

Store the signing secret

The whsec_… signing secret is revealed once. Store it in the receiver’s secret manager and verify every delivery before processing the body.

Test and operate

1. Select Test to queue a delivery.
2. Monitor the last delivery status, attempt count, response status, and failure count.
3. If a delivery is marked dead, fix the receiver and select Replay.
4. Revoke endpoints that are unused or compromised; revocation is immediate.

Safety rules

• Only HTTPS URLs without embedded credentials or custom ports are accepted.
• Local, private, and reserved network destinations are rejected.
• Make handlers idempotent because retries and replay can deliver the same event again.
• Respond before running slow work; queue downstream processing.