HookWatch

HookWatch sits in front of your webhook endpoints, receives each webhook, records it, and forwards it to your app without changing how your provider sends them. It records delivery status, response codes, timing, and attempt history, categorises failures by reason, and supports manual and automatic retry and replay of captured deliveries. Repeated failures are grouped into incidents that can be routed to Slack or a webhook. The page also describes an MCP server and HTTP API so AI assistants can list failed deliveries and replay them. The page describes HookWatch as early beta, free during beta, and works with Stripe, GitHub, Telegram, Shopify, and Paddle.

Key features

• Delivery capture with status, provider, response code, and attempt count
• Statuses: delivered, failed, retrying, rate limited
• Manual and automatic retry and replay of captured deliveries
• Failure analysis categorising failures by signature, timeout, 5xx, or rate limit
• Incident grouping of repeated failures
• Alerts routed to Slack or a webhook (beta)
• Each endpoint gets its own capture URL
• MCP server with tools derived from API routes, and an HTTP API
• CLI for dashboard and tunnel
• Workspace isolation, masked write-only secrets, encryption at rest, outbound safety restrictions

Best suited for

• Teams running webhooks in production, such as Stripe, GitHub, Telegram, or Shopify integrations
• Developers debugging failed webhook deliveries
• Small teams who rely on webhooks

Pricing

Free during beta