Connect Supabase to Town
Signups counted, the growth update drafted, and any production question answered in plain English, straight from your app's live tables. A secure connection to your Supabase project. Nothing to install.
Bo counted the week's signups in Supabase and drafted your growth update.
See it work: a routine built on your production data
Draft the growth update from your production numbers
Set it up once. Monday's numbers find you.
Open Integrations in Town
Go to Integrations in your Town workspace (free to create) and find Supabase.
Add your project keys
Grab your project reference and service role key from your Supabase dashboard's API settings and paste them in when prompted. Nothing to install or configure.
Put your tables to work
Done — signups counted, the growth update drafted, and any production question answered the moment you ask.
Routines that use Supabase
Ready-made routines from the Town library, built on Supabase. Install one and tailor it to how you work.
Just ask your Townie
Your app already writes the truth to Supabase. Town reads it back out: answers in chat, updates drafted, rows filed for approval.
“How many teams upgraded this week?”
Counted from your live tables, answered in chat.
“What plan is dana@acme.com on?”
Plan, signup date, and last login, pulled from your users table.
“Mark Acme's workspace as comped.”
The row updated in Supabase, held for your approval.
Supabase integration FAQ
Town's Supabase integration is a secure connection to your Supabase project — the Postgres database behind your app. Your Townie can read and count rows in your tables, call the Postgres functions you've defined, and, with your approval, insert, update, or delete rows. A separate Supabase Management API connection adds project tools: generate TypeScript types from your schema and create new projects. You connect with your project's keys; there's nothing to install.
Town reaches Supabase only when you (or a routine you configured) ask for it, using the project credentials you provide. Reads return the rows you ask about; every write — inserting, updating, or deleting rows, or calling a function — is held for your approval by default. Read more about how Town approaches security.
Not without you seeing it first. By default every write pauses for your approval — inserts, updates, upserts, deletes, and Postgres function calls all wait until you say go, and creating a project through the Management API does too. Town's tools work row by row through Supabase's data API; there's no free-form SQL tool that could touch your schema.
The tables and Postgres functions in the project you connect. Under the hood these are Town's Supabase tools: select rows, count rows, insert and batch-insert rows, update, upsert, and delete rows, and call a Postgres function. Connect the Supabase Management API as well and Town can also generate TypeScript types from your schema and create new projects.
No — the connection works with Supabase's free tier, since every Supabase plan includes the database API Town uses. On the Town side you just need an account — free to start, and the connection works on every Town plan.
The Supabase dashboard is built for whoever's comfortable in a SQL editor. Town brings your app's data to everyone else, in the places work happens — signups counted in chat, the growth update drafted to your inbox, and a row fixed from a single approved sentence.
What is Supabase?
Supabase is the open-source backend developers build their apps on: a real Postgres database plus auth, storage, and instant APIs. If your app runs on it, your users, signups, and orders already live in its tables.
Supabase holds your app's truth; Town puts it to work. Connected, production numbers land in your updates and briefs, plain-English questions get counted answers, and a new row is one approved sentence away.
