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:
- 1Go to Supabase Dashboard → Database → Webhooks
- 2Click "Create a new hook" and select the table and events
- 3Set the type to "HTTP Request" and paste your Hookbase ingest URL
- 4Consider using IP allowlisting on your Hookbase source for security
Signature verification
Supabase does not sign its webhooks with an HMAC scheme, so a signing secret on the source would have nothing to verify. Use a custom source with no secret, and keep the ingest URL itself hard to guess.
How Supabase secures them instead: Supabase database webhooks do not include signature verification by default. Use IP allowlisting.
Supabase event types
6 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
auth.user.created
A new auth user was created
auth.user.updated
An auth user was updated
storage.object.created
A file was uploaded to storage
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