Supabase

Developer Tools

Postgres development platform with auth, storage and realtime APIs.

Signature verification supported 3 events supported

Why use Hookfire with Supabase?

Instant push notifications

Get notified on your phone the moment a Supabase webhook fires. No more checking dashboards.

Subscribe to what matters

Choose exactly which Supabase events trigger notifications. Filter out the noise.

Team-wide delivery

Control who on your team gets notified and how: push notifications, record only, or both.

Setup in under 2 minutes

Copy a webhook URL, paste it in Supabase, and you're done. No code required.

Supported events

Event	Sample notification
Row inserted `INSERT` 🆕 New row in profiles A row was added to public.profiles	🆕 New row in profiles A row was added to public.profiles
Row updated `UPDATE` ✏️ Row updated in profiles A row in public.profiles changed	✏️ Row updated in profiles A row in public.profiles changed
Row deleted `DELETE` 🗑️ Row deleted from profiles A row was removed from public.profiles	🗑️ Row deleted from profiles A row was removed from public.profiles

What people use Supabase alerts for

Know when someone tells you something Survey responses, feature requests and new signups, as they land.

How to connect Supabase

Supabase Database Webhooks call Hookfire when a row is inserted, updated or deleted in a table you choose: a new row in profiles when someone signs up, a new order, a status change.

Step 1: Create an Integration

Go to your organization’s Integrations page.
Click Add Integration and select Supabase.
You’ll receive a unique Webhook URL. Copy it.

Step 2: Add the Webhook in Supabase

In the Supabase Dashboard, open your project.
Go to Integrations → Webhooks and create a webhook.
Give it a name and choose the table.
Under Events, tick Insert, Update and/or Delete.
For Type of webhook, choose HTTP Request, method POST, and paste your Hookfire webhook URL.
Under HTTP Headers, add the header from Step 3.
Create the webhook. Repeat for each table you want to hear about.

Step 3: Signing Secret (custom header)

Database Webhooks are not signed, so Hookfire checks a secret header instead:

Make up a long random string.
In the webhook’s HTTP Headers, add a header named X-Hookfire-Secret with that string as the value.
Paste the same string into the Signing Secret field on your Hookfire integration page.

Deliveries without the header, or with a different value, are refused.

Step 4: Subscribe to Events

On your Hookfire integration page, toggle on Row inserted, Row updated and/or Row deleted.

The notification names the table. Your own columns are in the delivery under record (and old_record for updates and deletes), so on Max you can rewrite the wording to show them, for example New signup: {{record.email}}, and add a payload rule such as table is profiles when one integration covers several tables.

Step 5: Test

Click the Test button next to an event on your integration page, or insert a row into the table.

Supported Events

Event	Description
`INSERT`	A row was inserted
`UPDATE`	A row was updated
`DELETE`	A row was deleted

Why not Auth Hooks? Supabase Auth Hooks run inside sign-up and login and wait for the answer, and the Send Email and Send SMS hooks replace Supabase’s own delivery. Pointing one at a notification service would delay or break your users’ sign-ins and emails, so Hookfire does not use them. A Database Webhook on your profiles table gives you the same signup alert without being in the way.

Reference: Database Webhooks.