What are Supabase webhooks?
Supabase webhooks send an HTTP request when an event occurs in your Supabase account. Teams use them to react to database changes from inserts, updates, and deletes without repeatedly polling an API. Hookflo gives each delivery a searchable record and can notify the right team when an event arrives or signature verification fails.
Events to monitor
Choose the event types that matter in your Supabase configuration. Common examples include:
- INSERT
- UPDATE
- DELETE
Connect Supabase to Slack or email
- Create a webhook in Hookflo and select Supabase.
- Copy the unique Hookflo webhook URL.
- In Supabase Dashboard → Database → Webhooks, add the Hookflo URL and choose the event types to send.
- Hookflo generates an x-webhook-token for this endpoint. Add it as a request header in the Supabase Database Webhook configuration.
- Save the endpoint, send a test event, and choose Slack or email for notifications.
Verify signatures and debug delivery issues
Supabase must send the generated x-webhook-token header exactly as shown in Hookflo. Do not paste it into the webhook URL.
When a delivery fails, check the selected event, destination URL, and provider-specific signing secret first. Hookflo keeps the event payload and verification result together so the issue is easier to diagnose.
Read Supabase webhook documentationHow do I send Supabase database webhooks to Slack?
Create a Supabase webhook in Hookflo, copy its URL and x-webhook-token, configure the database event in Supabase, and connect a Slack notification channel in Hookflo.