Qubit Docs العربية

Supabase

Connect the PostgreSQL database behind your Supabase project, including projects created with Lovable. Qubit reads the tables in one schema, either by copying them on a schedule (Sync Mode) or by querying the database live (Direct Mode).

Before you start

You need your project's Session pooler connection details:

  1. In Supabase, open your project and click Connect in the top bar.
  2. Choose Session pooler and note the host, port, database, and user.
  3. Have the database password ready. You set it when you created the project and can reset it in Supabase's Database settings.

Use the Session pooler host, such as aws-0-eu-central-1.pooler.supabase.com. The direct host (db.<project-ref>.supabase.co) only accepts IPv6 connections, and Qubit cannot reach it.

Connect Supabase

  1. Open Data Catalog from the sidebar, click Add Data, then choose Connect a database.
  2. On the New Data Source page, click Supabase. It is under Databases.
  3. Enter a Connection Name.
  4. Fill in the connection details:
    • Session pooler host: the pooler host from Supabase. You can also paste the full postgresql:// connection string here, and Qubit fills in the port, database, username, and password from it.
    • Port: defaults to 5432.
    • Database: defaults to postgres.
    • Username: the pooler username, which includes your project ref after a dot, for example postgres.abcdefghijklmnop.
    • Database password: the database password. Do not use the anon or service_role API keys.
    • Schema: defaults to public.
  5. Under Connection Mode, choose Sync Mode or Direct Mode.
  6. To connect through an SSH bastion host instead, turn on Connect via SSH tunnel and fill in the SSH fields. The tunnel always uses Direct Mode.
  7. For Sync Mode, choose a Sync Schedule. The default is Daily.
  8. Click Create.

Qubit tests the connection before saving it, then takes you to the Data Catalog. In Sync Mode, the first sync starts right away.

If the test fails

The form shows the error message:

  • "This is Supabase's direct host, which is IPv6 only": replace the host with the Session pooler host shown under Connect in Supabase, and use the pooler username postgres.<project-ref>.
  • "Authentication failed": check the username and the database password.
  • "Schema does not exist": check the schema name. Supabase apps usually keep their tables in public.

For other errors, see PostgreSQL. Supabase uses the same checks.