How can I resolve connection issues with Supabase Postgres in n8n?

Below are a couple of common issues when connecting to Supabase’s Postgres database that you might want to double-check:

1. Using the Correct Host
   Supabase provides a connection string that usually includes a pooler endpoint (for example, something like “xxxx.pooler.supabase.com”). In your example you’re using “lettercombination.supabase.co” as the host.

   • Ensure you’re using the exact host from your Supabase Database Settings. If you have connection pooling enabled (as indicated by “maximum number of connections: 100”), the host will likely have “pooler” in it.
   • If you’re set to use the pooled connection, update your host accordingly. Alternatively, if you want to bypass pooling, disable it in the Supabase settings and use the direct connection string.

2. SSL Configuration
   Supabase generally requires SSL connections.

   • Make sure the SSL option in your n8n Postgres credentials is set to “Require” or otherwise matches the settings provided in Supabase’s documentation.
   • If you’re testing with SSL off and it doesn’t connect, try with SSL on (and vice versa) using the value exactly as shown in the connection string.

3. Credentials Type in n8n
   n8n offers both a Postgres credential type and a Supabase-specific credential type.

   • If you’re connecting to Supabase, consider whether you may need to use the dedicated Supabase credentials. The Supabase credential in n8n expects a Host and a Service Role Secret (the API Key from Project Settings > API).
   • Using the database user “postgres” with a password reset might not be enough if you’re meant to supply the service role key as per the Supabase credentials documentation.

Double-check the connection string details and see if switching between credentials types makes a difference.

Here’s an example of how a connection string might look if you’re using connection pooling (note the pooler host):

BASHCopied
export DATABASE_URL=postgres://postgres.xxxx:your_password@xxxx.pooler.supabase.com:5432/postgres

Make sure your n8n Postgres credentials match these details. Updating the host and verifying the SSL option should resolve your issue.