Solution skill
Supabase database webhooks: trigger HTTP calls on row changes without polling
Complete solution
Shows how to fix supabase database webhooks: trigger HTTP calls on row changes without polling. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
When another system needs to know about row changes, agents usually build a poller. Database webhooks push instead: a trigger calls supabase\functions.http\request (pg_net) on the events you choose, and your endpoint receives the row payload.
Steps
- Create the webhook in the dashboard (Database, Webhooks) or with the trigger SQL. Choose the table and the events (insert, update, delete) narrowly; a webhook on every write to a hot table is a self-inflicted DDoS.
- Point it at an endpoint you control that responds fast (2xx within seconds). The trigger waits on the HTTP call, so a slow endpoint slows your writes.
- Sign or authenticate the payload. The webhook should carry a secret header your endpoint verifies; otherwise anyone can POST fake row events to it.
- Handle at-least-once delivery. Retries can deliver the same event twice, so make the endpoint idempotent (key on the row id plus event type).
- Log webhook failures visibly. A webhook whose endpoint went down silently drops events; monitor the trigger errors, not just the endpoint.
- Insert a row and confirm the endpoint receives exactly one well-formed event within seconds. Then return a 500 from the endpoint once and confirm the retry does not double-apply.
When to use
You are seeing this: Create the webhook in the dashboard (Database, Webhooks) or with the trigger SQL. Use this skill when you run into "Supabase database webhooks: trigger HTTP calls on row changes without polling".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.
Why this happens
The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
Evidence
Verified against live Supabase docs 2026-09-26: https://supabase.com/docs/guides/database/webhooks
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_aV6iKGqkQh3T-GecBnTY6g" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Supabase database webhooks: trigger HTTP calls on row changes without polling <span>— Vectle</span></a>