Supabase

Rowsend reads your Supabase users, usually from auth.users, through a view and a read-only login. You run one piece of SQL in Supabase; Rowsend writes it for you.

1. Copy the connection string

1. In Supabase, open your project and click Connect.
2. Choose Direct, then Session pooler, and copy the URI.
3. Replace [YOUR-PASSWORD] with your database password.

In Rowsend, open Contacts, click Connect a database, choose Supabase and paste the URI. Click Continue.

Rowsend uses this password once, to list your tables. It doesn’t save it.

2. Choose what Rowsend reads

Rowsend suggests auth.users with its email, sign-up and sign-in times. You can:

• join a second table, such as public.profiles, for names or plan details
• tick extra columns, which become custom fields
• switch to writing the select yourself

The select must return id, email and updated_at. See How syncing works.

3. Run the setup SQL

Click Open SQL editor. It opens Supabase’s SQL editor and copies the SQL. Paste it and run it.

The SQL:

• creates a rowsend schema with a contacts view
• creates a login called rowsend_reader that can only read that view

It contains a hash of the login’s password, not the password, so it’s safe to share.

4. Test and connect

Back in Rowsend, click Test and connect. The first sync starts straight away.

Supabase’s connection pooler can take a few seconds to see the new login. Rowsend retries a rejected login a few times before reporting an error.

Troubleshooting

Couldn’t load your tables. The password in the URI is wrong, or still a placeholder. You can fix it, or write the select yourself in the SQL box.

The login is rejected after several tries. Check that you ran the latest SQL. Changing the select in Rowsend changes the SQL, and Test and connect stays disabled until you’ve copied the current version.