How to Connect Supabase to n8n

Supabase provides the Postgres database that several systems in this library use as their prospect tracker. On n8n Cloud there is no bundled database, and a free Supabase project fills that role in a few minutes: it is standard Postgres, so every Postgres node in the workflows runs against it without edits.

What you need

• A Supabase account. The free tier includes a 500 MB Postgres database, which holds years of prospect data for a system this size.
• A running n8n instance (cloud or your own).
• About 10 minutes.

Create the project and get the connection string

1. Sign up at Supabase and create a new project. Pick a region near your n8n instance.
2. Set a strong database password when prompted and store it; Supabase shows it only once.
3. Open Project Settings, then Database. Copy the connection string in the “Session pooler” form. It looks like postgresql://postgres.xxxx:[password]@aws-0-region.pooler.supabase.com:5432/postgres.
4. Replace [password] with the password from step 2.

Create the credential in n8n

1. Go to Credentials and click Add credential.
2. Search for “Postgres” and pick the Postgres credential.
3. Fill the fields from the connection string: host, port 5432, database postgres, user, and the password. Turn SSL on.
4. Name the credential “Supabase LGL”. The library’s workflows reference that exact name on every Postgres node.

Create the tables

Each system’s spec lists its table columns in the workflow architecture section. The fastest route: open the SQL editor in Supabase, paste the CREATE TABLE statement for the prospect table (the spec’s prospect-table column list maps 1 to 1), and run it. The suppression table is two columns, email and date.

Verify it works

Open any library workflow that has a Postgres node, attach the credential, and run the node with a SELECT 1 query. A green result means the connection, SSL, and password are right. Then run the workflow’s own fetch query once; an empty result set is correct before the first sourcing run.

Cost and one gotcha

The free tier costs nothing and needs no card. The gotcha: Supabase pauses free projects after about a week of full inactivity, and a paused database makes every workflow fail until you resume it in the dashboard. The library’s schedules query it daily, which counts as activity, so this only bites while you are still setting up. If you pause your outreach for a vacation, expect to press Resume once when you come back.

Where the library uses Supabase

Any system whose workflow architecture names Postgres as the tracker: the sourcing workflow inserts prospects, enrichment updates their status, outreach reads what is due, and the reply handler moves them through the funnel. Systems that track in Google Sheets instead do not need it.