Prerequisites
The connector should already be set up, with a Connector Profile and a Linked Account. See Getting Started on the Supabase connector page.Configure a Supabase Database Webhook
This connector uses Manual Webhooks. You must create a Database Webhook in the Supabase Dashboard for each table you want events from — storage.objects (files), storage.buckets (buckets), and/or auth.users (users) — pointing each webhook at the StackOne Native Webhook URL shown on this connection, which exists once the connection has been created. Repeat this procedure once per table.
Enable Database Webhooks on your project
In the Supabase Dashboard, open your project.
- Click Integrations in the left sidebar.
- Select Database Webhooks.
- If the Overview tab shows Enable database webhooks on your project, click Enable webhooks.
- This is a one-time step per project. Once enabled, Database Webhooks appears under Installed in the Integrations sidebar.

Name the webhook
Create a new database webhook for the table.
- Open the Webhooks tab.
- Click Create a new hook.
- Name: any name without spaces

Select the table to watch
Pick the table whose events you want to receive.
- Under Conditions to fire webhook, open the Table dropdown (Select a table).
objectsin thestorageschema — file events (Supabase Storage keeps every file in this table).bucketsin thestorageschema — bucket events.usersin theauthschema — user lifecycle events.- You can only select 1 table for a trigger — create one webhook per table.

Select the events
Under Events, tick the operations that should fire the webhook.
- Insert — Any insert operation on the table
- Update — Any update operation, of any column in the table
- Delete — Any deletion of a record
- Only the events selected here will fire the webhook on the table you’ve selected.

Configure the HTTP request target
Under Webhook configuration, keep Type of webhook set to HTTP Request. In the HTTP Request section, fill in the request.
- Method:
POST - URL: the Native Webhook URL from the Linked account
- The Native Webhook URL field on the Linked account is only available after the connection has been created.
- The URL of the HTTP request must include HTTP/HTTPS.
- Leave the default HTTP Headers row
Content-type: application/jsonin place.

Create the webhook
Click Create webhook. The new hook appears in the Webhooks list showing its Name, Table, Events, and the Webhook target URL.

Verify delivery
Trigger a write operation (insert, update, or delete a row) on the configured table and confirm the event arrives in StackOne.
- Supabase delivers webhooks asynchronously via the pg_net extension. Delivery is best-effort — failed requests are not automatically retried.
- You can inspect deliveries in the Supabase Dashboard Logs section, or by querying the
net._http_responsetable directly.
Available webhook events
The following Supabase events can be received. Only events enabled in StackOne are processed. For each table listed, configure a Database Webhook with the Insert, Update, and Delete events enabled.
- User Created (
INSERTonauth.users) — Fired when a new user signs up or is created. - User Updated (
UPDATEonauth.users) — Fired when a user record changes (profile, confirmation, ban, metadata) — and on every sign-in, since Supabase records the sign-in time on the user row. - User Deleted (
DELETEonauth.users) — Fired when a user is permanently deleted. - Storage Object Created (
INSERTonstorage.objects) — Fired when a file is uploaded to Supabase Storage. - Storage Object Updated (
UPDATEonstorage.objects) — Fired when a file is overwritten, moved, or its metadata changes. - Storage Object Deleted (
DELETEonstorage.objects) — Fired when a file is deleted from Supabase Storage. - Bucket Created (
INSERTonstorage.buckets) — Fired when a storage bucket is created. - Bucket Updated (
UPDATEonstorage.buckets) — Fired when a bucket’s settings change (visibility, size limit, allowed types). - Bucket Deleted (
DELETEonstorage.buckets) — Fired when a storage bucket is deleted.