What problem does it solve?
Webhook integrations are vulnerable to forgery, duplicates, and unreliable delivery. This Skill provides a structured approach to reliably receive and send webhooks with strong verification, idempotency, and resilient error handling.
Core Features & Use Cases
- Receiving: Signature Verification: Always verify HMAC signatures on inbound payloads to prevent forgery; use raw body bytes and constant-time comparison; reject missing/invalid signatures with 401 and logs for investigation.
- Receiving: Replay Prevention: Enforce timestamps and nonce IDs to reject replayed events; tolerate small clock skew.
- Receiving: Idempotency (Critical): Use event IDs for deduplication; make handlers idempotent; retain IDs for 24-72h to balance storage and protection.
- Receiving: Fast Response: Acknowledge with 200/202 and process asynchronously via a queue to avoid retries; perform minimal upfront validation.
- Sending: Retry Strategy & Signature: When sending, sign payloads with a timestamp; implement exponential backoff and cap retries; distinguish 4xx vs 5xx behavior.
- Event Design & Delivery Tracking: Include event type and timestamp, provide full resource or ID, log attempts, and provide a retry dashboard; retain webhook logs for debugging.
- Security & Common Mistakes: Enforce HTTPS, rotate secrets, avoid including secrets in payloads, and prevent common misconfigurations.
Quick Start
Configure a webhook endpoint to verify signatures on inbound payloads and enqueue processing for asynchronous handling.