Supabase

Overview

The Supabase connector reads changes from your project's Postgres database through logical replication, so workflows react to writes without polling or database webhooks. Each change arrives as a typed event with the table schema attached, and every event shows up in the trace of the run it started.

Teams use it to send a SendGrid welcome email when a profile row is created, to create a HubSpot contact for each new workspace and to grant Stripe credits after an onboarding step is saved.

Supported plans

• Free, Pro, Team and Enterprise projects in any Supabase region

• Direct connections on port 5432, or the IPv4 add-on if your network lacks IPv6

• Edge functions and storage called over HTTPS with a scoped key

How logical replication works

Tessel uses a publication for the tables you choose and a replication slot it reads continuously. Changes are decoded with pgoutput and delivered in commit order. The pooled connection on port 6543 does not support replication, so Tessel always uses the direct connection.

create publication tessel_pub
  for table public.orders, public.profiles;

create role tessel with login replication
  password '<password>';
grant select on public.orders, public.profiles to tessel;

create publication tessel_pub
  for table public.orders, public.profiles;

create role tessel with login replication
  password '<password>';
grant select on public.orders, public.profiles to tessel;

create publication tessel_pub
  for table public.orders, public.profiles;

create role tessel with login replication
  password '<password>';
grant select on public.orders, public.profiles to tessel;

Row level security

Change events come from the replication stream, so row level security policies do not filter them. Read and write actions run as the tessel role, so add policies for that role on tables where RLS is on, or the actions will see no rows.

Permissions needed

Create a dedicated role in the SQL editor. It needs replication and read access to the tables in the publication. Write access and an API key are only required for the write, edge function and storage actions.

• REPLICATION and LOGIN on the tessel role

• SELECT on every table in the publication

• A secret API key only if you call edge functions or storage