Webhooks
The Webhooks component copies database webhooks from the source project to the target project.
What Is a Database Webhook?
A Supabase webhook sends an HTTP request to an external URL each time an event occurs on a table (INSERT, UPDATE, DELETE). For example:
- Notifying an external service when a new user signs up
- Triggering a workflow when an order is created
- Sending data to an analytics tool
What Is Copied
For each webhook:
- Name of the webhook
- Table being monitored
- Trigger events (INSERT, UPDATE, DELETE)
- Destination URL
- Custom HTTP headers
Key Considerations
| Situation | Behavior |
|---|---|
| Webhook URL pointing to production | The URL is copied as-is — staging will call the same URL |
| Headers with tokens | Copied as-is |
Warning: If your webhooks point to production services (payment APIs, notifications, etc.), cloning them to staging will cause staging to send requests to those same services. Consider:
- Disabling this component for staging
- Modifying the webhook URLs on the target after the clone
Next Steps
- Realtime — Realtime configuration
- Clone options — Disable webhooks