Skip to main content

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.

1

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.
Supabase Database Webhooks overview page with the Enable webhooks button highlighted
2

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
Create a new database webhook panel with the Name field highlighted
3

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).
  • objects in the storage schema — file events (Supabase Storage keeps every file in this table).
  • buckets in the storage schema — bucket events.
  • users in the auth schema — user lifecycle events.
  • You can only select 1 table for a trigger — create one webhook per table.
Table dropdown open showing schema-qualified tables to select
4

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.
Table selected and the Insert, Update and Delete event checkboxes ticked
5

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/json in place.
HTTP Request configuration with Method POST and the URL field containing the Native Webhook URL highlighted
6

Create the webhook

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

Webhooks list showing the newly created webhook row with table, events and 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_response table 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 (INSERT on auth.users) — Fired when a new user signs up or is created.
  • User Updated (UPDATE on auth.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 (DELETE on auth.users) — Fired when a user is permanently deleted.
  • Storage Object Created (INSERT on storage.objects) — Fired when a file is uploaded to Supabase Storage.
  • Storage Object Updated (UPDATE on storage.objects) — Fired when a file is overwritten, moved, or its metadata changes.
  • Storage Object Deleted (DELETE on storage.objects) — Fired when a file is deleted from Supabase Storage.
  • Bucket Created (INSERT on storage.buckets) — Fired when a storage bucket is created.
  • Bucket Updated (UPDATE on storage.buckets) — Fired when a bucket’s settings change (visibility, size limit, allowed types).
  • Bucket Deleted (DELETE on storage.buckets) — Fired when a storage bucket is deleted.

Verify

Your Connector should now be able to receive and process events. Try triggering an event and you should see an Event appear in the Connector logs.