S
Receive Supabase webhooks on localhost
Supabase can call an HTTP endpoint on database changes (Database Webhooks) or during auth flows (Auth Hooks). Pipehero gives that endpoint a public URL pointing at your machine so you can develop against real payloads.
1Install Pipehero and start a tunnel
Install the CLI, log in, then expose your local port. You get a stable public URL like
myapp.t.pipehero.app.curl -fsSL pipehero.app/install | sh pipehero login pipehero start myapp --port 3000
2Create a Database Webhook
In the Supabase dashboard go to Database → Webhooks → Create, choose the table and events (INSERT/UPDATE/DELETE), and set the URL to your Pipehero endpoint. Add any custom header/secret you want to verify.
https://myapp.t.pipehero.app/webhooks/supabase
3Or wire an Auth Hook
For auth flows (e.g. send-email, custom access token), set the hook URL to your Pipehero endpoint and develop the handler locally.
4Inspect & replay
Every request shows up live in the dashboard (and the local panel at
localhost:4140) with headers and body. Hit Replay to re-send it to your localhost — no need to re-trigger the event at the provider. Requests that arrive while your CLI is offline are captured and can be replayed later.5Verify the signature
Database Webhooks let you send a custom secret header you fully control — add a Custom provider in Pipehero matching that header to get a ✓/✗ badge. Auth Hooks use standard-webhooks (Svix-style) signatures, which you can verify in your handler.
FAQ
Can I debug the pg_net delivery?
Yes — every delivery shows up in the live tail with headers and body, so you can confirm exactly what Supabase sent and replay it into your handler.
Related
Start debugging webhooks in a minute
Free plan, no credit card. Expose localhost, inspect and replay every webhook.
Get started free