Connect Supabase to native.builder

Supabase gives your app a real database, user accounts, file storage, and server-side functions. Once you connect it, you can describe what you want in chat — for example, “let users sign up and save their favourites” — and the Builder agent sets up the tables, security rules, and login flow for you. This guide covers connecting Supabase, pointing an app at the right Supabase project, and the things that commonly trip people up.

​

Before you start

You’ll need a Supabase account. You can create your first project during the connection flow, or let the agent guide you. You also need to be an owner or admin of your native.builder workspace to connect Supabase. Members can use a connection that’s already set up, but can’t create or remove one. If the Connect button isn’t there, ask whoever owns your workspace.

​

Connecting Supabase: two steps

There are two separate things to do, and it’s worth knowing why.

1. Connect your Supabase account to your workspace — one-time setup that lets Builder talk to Supabase on your behalf.
2. Choose which Supabase project each app uses — your Supabase account can hold many projects (databases). Each app you build needs to be pointed at one of them.

Step 1 alone doesn’t do anything visible. The Builder agent won’t touch Supabase until you’ve also done step 2.

​

Step 1: Connect your account

You can also connect from inside a project: open the integrations menu in the chat header and click Connect workspace. It’s the same workspace connection either way.

​

Step 2: Point your app at a Supabase project

That’s it. The agent can now create tables, set up logins, store files, and write server-side functions for this app. You can also ask in chat — “connect this app to my Supabase project” — and the agent will show your projects and link the one you choose.

​

Turning Supabase on and off for an app

The switch in the integrations menu controls whether the agent can work with Supabase in this app only.

• Off — stops the agent from reading or changing anything in Supabase. It does not delete your database, data, or anything else in your Supabase project.
• On again — remembers the project you’d picked before, so you don’t need to select it again.

Turn it off when you want the agent to focus on the front end, or when you want to be certain it isn’t going to modify your data while you work on something else.

​

Choosing the right organization

When you authorize native.builder, Supabase asks which organization to grant access to. Builder can then only see the projects inside that one organization. This is the single most common source of confusion. If you have more than one organization — a personal one and a team one, say — and you pick the wrong one, projects in the other organization simply won’t appear in your list. No error — they’re just not there. If a project you expect is missing, it’s almost certainly in a different organization than the one you authorized. Fixing it means disconnecting and reconnecting, choosing the right organization this time. There’s no way to switch organizations without disconnecting first — and disconnecting has a consequence worth reading in Disconnecting Supabase.

​

Creating a Supabase project yourself

You don’t have to — the agent can walk you through it — but if you create projects in the Supabase dashboard:

• New projects don’t appear instantly. The list loads when you open it. Close the dropdown and open it again to refresh. No need to reload the page.
• Create it in the organization you authorized. The create link may default to whichever org you last used in Supabase. If that’s not the connected org, the new project won’t show up in Builder.
• Give it a moment to finish setting up. A brand-new project takes a minute or two to provision. It can appear in the list before it’s healthy — wait until Supabase shows it as ready.
• Watch for paused projects. On Supabase’s free plan, projects pause after inactivity. A paused project still appears and can be selected, but every database operation will fail (and it can look like the agent is at fault). Un-pause it in the Supabase dashboard.
• Avoid duplicate project names. If two projects share a name and you ask the agent to link one by name, it can’t tell them apart. Pick from the list in the integrations menu instead.

​

Disconnecting Supabase

Disconnect from Settings → Integrations → Supabase → Disconnect. That’s deliberate — it prevents an app from quietly staying pointed at a project you no longer have access to. What disconnecting does not do: it doesn’t touch anything inside Supabase. Databases, tables, data, users, files, and functions stay put. It only removes native.builder’s access. To also revoke authorization on the Supabase side, do that in your Supabase account settings — that’s a separate action.

​

How the agent handles secrets

If your app needs an API key or other secret, the agent asks with a masked input, not as a normal chat message. Values entered that way go into Supabase’s secure secret storage. They never appear in the conversation, and the agent never sees them. Your app’s server-side code can read them; nobody reading the chat can. Entering a secret under a name you’ve used before replaces the old value. There’s no undo — double-check before saving a replacement.

​

Logins and preview links

If you build sign-up or login into your app, the agent automatically configures Supabase to accept Builder’s preview URLs. Without that, logging in from the preview panel would fail. This happens behind the scenes. You only need to know about it if you later change those settings manually in the Supabase dashboard — login from previews may stop working.

​

Troubleshooting

​

Quick reference

​

Next steps