[DOCS-REQUEST] -

[dtsoden]

What information is missing?
Supabase connections have 2 possibilities:

• Postgres SQL Account (Missing under the context of Supabase) https://docs.n8n.io/integrations/builtin/credentials/postgres/
• Vector https://docs.n8n.io/integrations/builtin/credentials/supabase

Describe the page/pages you'd like
So in Supabase the Postgres connection is a bit of a nightmare to get sorted:

• Direct connection (most will try to use this but its IPv6 only and wont work for many users)
• Transaction pooler (will work but is meant when each interaction with Postgres is brief and isolated)
• Session pooler - (Only recommended as an alternative to Direct Connection, when connecting via an IPv4 network.)

So I got it to work on my own, but then when SSL came into the mix, the wheels fell off the bus. These connections need to be secure. When you enabled forced secure connections on Supabase https://supabase.com/docs/guides/platform/ssl-enforcement , they refuse to connect

Couldn’t connect with these settings 
self-signed certificate in certificate chain

this is despite downloading and installing their Supabase Root 2021 CA to both my personal and in local machines "Trusted Root Certification Authorities" then restarting n8n

Additional context
https://supabase-downloads.s3-ap-southeast-1.amazonaws.com/prod/ssl/prod-ca-2021.crt
Documentation is needed for to clearly connect to a Supabase Postgres SQL in a production ready secure way.

[dtsoden]

I was able to set an environment variable NODE_TLS_REJECT_UNAUTHORIZED=0 but this seams bad to do to get it to trust a self signed certificate which Supabase provides. Ideally this would be its own SUPABASE DB node and not a Postgres node