Infrastructure
Supabase Webhooks
Open-source Firebase alternative. Receive events for database changes, auth events, and storage updates.
Connecting Supabase to Hookbase
Create a source in Hookbase first — it gives you an ingest URL to paste into Supabase. Then:
- 1Create the Hookbase source first and copy the Authorization header value Hookbase generated
- 2Go to Supabase Dashboard → Integrations → Database Webhooks and click "Create a new hook"
- 3Select the table and the events (Insert, Update, Delete)
- 4Set the type to "HTTP Request", method POST, and paste your Hookbase ingest URL
- 5Under HTTP Headers, add Authorization set to the Hookbase value (a "Bearer " prefix is fine too) and save
Signature verification
Set the source's provider to supabase and paste the signing secret. Every request is checked before the event is stored, and anything that fails is rejected rather than quietly recorded.
- Algorithm
- Shared secret echoed verbatim in a custom header (not HMAC-signed)
- Header
- Authorization
- Where to find the secret
- Supabase Dashboard → Integrations → Database Webhooks → your hook → HTTP Headers → add "Authorization" set to the value Hookbase generated (with or without a "Bearer " prefix). Supabase does not sign these webhooks.
Supabase event types
3 of the events people route most often. Hookbase accepts every event Supabase sends, whether or not it is listed here.
INSERT
A row was inserted into a table
UPDATE
A row was updated in a table
DELETE
A row was deleted from a table
What a Supabase webhook looks like
A INSERT payload. Hookbase stores the raw body exactly as it arrived, so this is also what you get back on a replay.
{
"type": "INSERT",
"table": "todos",
"record": {
"id": 1,
"title": "Buy groceries",
"completed": false,
"user_id": "uuid-123"
},
"schema": "public",
"old_record": null
}Start receiving Supabase webhooks
Create a source, paste the URL into Supabase, and watch the first event arrive. The free tier includes 1,000 events a month.
Get Started Free