Connect an Existing Project

If you already have a Supabase project with tables, auth, and storage set up, you can connect it directly to Noah. This is useful when you want to build a new frontend on top of an existing backend — without duplicating your database.

When to Use This

Sharing a single Supabase project across Noah apps is useful when you want to:

• Power multiple frontends (e.g., customer site and admin panel) with the same data
• Keep authentication, storage, and APIs consistent across builds
• Test new UI designs without duplicating your backend
• Bring an existing Supabase database into Noah and focus entirely on the UI

Connect an Existing Supabase Project

1. Open the Cloud Tab or Settings

   In your Noah project, click the Cloud tab in the toolbar, or go to Settings → Integration and click Connect next to Supabase.

2. Authorize Noah AI

   A Supabase authorization page opens. Review the permissions, select your organization, and click Authorize Noah AI.

3. Select Your Existing Project

   From the project list, choose the Supabase project you want to connect and click Connect.

   

Best Practices

Start with your schema

In your first prompt, mention the tables and fields you need so Noah knows what to work with.

Example:

• Table: Users → Fields: Name, Email, Date joined
• Table: Orders → Fields: Order ID, Status, Amount

Describe your setup

If your database is already live, say so. Noah will not auto-detect the schema unless you explain it in the chat.

List the pages you want

Tell Noah exactly what you need.

Example: “Create a Users page showing Name and Email, and an Orders page showing Status and Amount.”

One project, one purpose

Keep Noah projects focused. For example:

• One for your user-facing app
• One for your internal dashboard

When Noah generates migration scripts

Only push the script if you want to update the actual database.

• Push when: You are adding new fields or tables
• Do not push when: Your schema already includes everything you need

If multiple apps share the database

Database changes affect every connected Noah project. If one app adds a field, others can access it, but you will need to update those UIs separately.

Example scenario:

1. In App A, you prompt: “Add a Phone number field to user profiles.”
2. Supabase now has a new field: Phone number.
3. App B also connects to this database, but does not yet show the field.
4. In App B, prompt Noah: “Update Users page to show Phone number.”

Try it in a test project first

Exploring ideas? Connect to a test Supabase project before making changes to production.

Troubleshooting

I don't see my Supabase project in Noah

After signing in to Supabase, the project list is empty.

• Make sure you are signed in to the correct Supabase account
• Check that you selected the right organization during authorization

Changes in one Noah project affect another

Updating the database in one Noah project instantly affects another.

• This is expected behavior when projects share a database
• To isolate changes, connect each Noah project to a separate Supabase project