Reliable Webhook Relay
Secure, fast and globally distributed
Never miss an event —deliver it, or start a task.
A webhook gateway that receives events from any provider, verifies signatures, routes and delivers them to your destinations, and can trigger a multi-step task when a rule matches.
Compatible with:
- GitHub
- Sentry
- Stripe
- Slack
- Microsoft Teams
- Discord
- Grok Bot
- Telegram
- Lark
Inbound Webhooks (GitHub / Sentry / Stripe / Custom)Webhook Gateway (Verify / Route)Destination delivery or task trigger
Real-time Observability
Track events, deliveries and more
Enterprise-Grade Security
Verify signatures, prevent abuse
Live gateway console
Live Events Stream
17:32:3511ms
"id": "evt_01J8K0001",
"type": "github.push",
"source": "github",
"data": {"repository":"hooks/events"}
17:32:3514ms
"id": "evt_01J8K0002",
"type": "stripe.payment_succeed",
"source": "stripe",
"data": {"amount":8900,"currency":"usd","customer":"cus_9x8F2"}
17:32:358ms
"id": "evt_01J8K0003",
"type": "order.created",
"source": "custom",
"data": {"orderId":"ord_1024","total":320.5,"items":3}
Event Flow
hooksRelay
Illustrative demo data — not live metrics, latency measurements, or an SLA.
P99 Latency8.4 ms
Delivery Ratedemo
Active Relays38 PoPs
Core Architecture
Stop losing webhooks to downtime, timeouts, and rate limits.
Hooks sits between your providers and your application. It absorbs spikes, verifies signatures, and retries failed deliveries — at least once, so deduplicate at the destination.
Fast Edge Ingestion
Edge ingestion acknowledges webhooks immediately, preventing provider timeouts from Stripe, Shopify, or GitHub.
Zero-Config Signature Firewall
Automatically verifies HMAC SHA-256 signatures before untrusted traffic touches your backend.
Dead Letter Queue
When your backend returns 5xx or is mid-deployment, Hooks queues the event and retries with exponential backoff. When the attempt budget is spent, the delivery is kept as a dead letter you can replay.
In-Flight Payload Transforms
Strip sensitive fields, extract keys, or fan one event out to your database and your analytics warehouse — no proxy microservices.
Browse 11 ready-made transformsWebhook-triggered Tasks
A trigger is a source plus an event type, with optional filters: GitHub issues.labeled + the agent label starts a task — in parallel with delivery.
Simple, usage-based pricing
Try it free. Pay per 10,000 requests.
Start with a one-time free grant, then buy blocks of 10,000 requests. Credits never expire and never renew automatically.
Request blocks:
Recommended Plan:Pro
$3 one-time
Free
One-time trial for side projects
$0 one-time grant
- 1,000 accepted requests per account
- 7-day event retention
- 3 endpoints, 2 destinations each
- 1 workspace member
- HMAC verification and retries
Pro
From $3 for shipping teams · credits never expire
$3 one-time
- 30,000 requests for $3
- Or $1 per 10,000 requests
- 30-day event retention
- Unlimited endpoints and destinations
- 5 team members
- Admin, editor and viewer roles
Scale
For platforms above one million requests
Custom / volume pricing
- Over 1,000,000 requests / month
- 60-day event retention
- Unlimited endpoints and destinations
- 25 team members
- 5 MiB request body limit
Questions
Answers before you wire anything up.
What is Hooks?
Hooks is a webhook gateway that receives events from any provider, verifies signatures, routes and delivers them to your destinations, and can trigger a multi-step task when a rule matches.
How is a Task triggered?
Create a Task and set a trigger: a source (for example GitHub), an event type (for example issues.labeled), and optional filters. When a matching webhook arrives at any endpoint for that source, Hooks starts a run. This is separate from destination delivery, which forwards a rendered payload to an endpoint. Triggers match workspace-wide, so it does not matter which endpoint receives the event.
Which sources can send events to Hooks?
Hooks ships adapters for over 100 providers, including GitHub, Stripe, Slack, Linear, and Sentry. The generic source accepts any sender that can sign requests with Hooks' HMAC-SHA256 scheme; providers with another signature scheme need an adapter.
How do I verify a webhook came from the provider?
Hooks verifies the provider's HMAC-SHA256 signature when the event arrives and rejects timestamps old enough to be a replay. Every request forwarded to your destination carries its own Hooks signature, with code samples for Node, Go, and Python in the docs.
What happens when a destination is down?
Failed deliveries retry automatically with exponential backoff, up to 5 attempts by default (1–10 configurable per destination). Retries reuse the same delivery ID, so your destination can deduplicate them; a retryable failure that runs out of attempts becomes a dead letter you can replay. Delivery is at-least-once, never exactly-once.
Do I need to run any infrastructure?
No. Hooks runs on Cloudflare Workers with D1 storage. The Free plan includes 1,000 accepted requests as a one-time grant, and Pro is $1 per 10,000 requests, a one-time purchase starting at $3 for 30,000 requests, and credits never expire.
Can I use Hooks with AI agents?
Yes. Forward events to agents such as Grok Bot, t3code, or Paseo with payload templates, or turn an event into an agent task with the payload-to-task tool. Both are destination delivery: Hooks forwards a rendered payload to the agent's HTTP endpoint. To start a durable, multi-step Task run from an event instead, use a Task trigger.