Supabase webhooks, without the lost events
Send Supabase database webhooks to your services with a secret header check, durable storage, retries and replay.
Common problems, solved
- Database webhooks carry no signature by default.
- Add a secret header in Supabase; HookStead checks it and strips it before forwarding.
- Table changes need to reach services outside Supabase, reliably.
- HookStead stores every change event and delivers it with retries to one or more destinations.
Set up in five minutes
- 01In Supabase, open Database → Webhooks → Create a new hook and choose the table and events.
- 02Set the type to HTTP Request, method POST, and paste your HookStead source URL.
- 03Under HTTP Headers, add X-Webhook-Secret with the same value you enter here.
| Source option | Supabase (secret header) |
|---|---|
| Signature header | X-Webhook-Secret |
| Scheme | A secret header you add in Supabase, compared in constant time |