Hookdeck webhook reliability
Community-contributed integration
This integration is community-maintained. Reference: ory/integrates/webhook-infrastructure/hookdeck.
Hookdeck is a webhook reliability layer with managed ingestion, automatic retries, rate limiting, replay, and observability. You route Ory Network Actions through Hookdeck so transient handler failures don't lose events and you get a queryable event store of every Ory webhook delivery.
How it works
Ory Action → Hookdeck Source → Hookdeck queue/retry → Hookdeck Destination → Your handler
- In Hookdeck, create a Source (HTTP endpoint Hookdeck exposes) and a Destination (your handler URL).
- Connect them with a Connection that defines retry policy, filtering, and transformations.
- Point your Ory Action webhook URL at the Hookdeck Source URL.
- Hookdeck buffers, retries with backoff, surfaces failures for replay.
Why route through Hookdeck
- Handler downtime resilience — Hookdeck adds a more aggressive retry layer with persistent storage than Ory Actions' built-in retries.
- Event replay — replay any historical Ory event into your handler from the Hookdeck dashboard.
- Filtering — drop events that don't matter before they reach your handler.
- Transformations — reshape the Ory payload to match your handler's expected schema without touching either side.
Notable
- Pass through the
X-Webhook-Secretheader from Ory to your handler so signature verification still works. - Compare with
webhook-infrastructure/svix— Svix focuses on outbound webhooks from your product to your customers; Hookdeck focuses on inbound reliability.
