Hi everyone,
I’m currently trying to set up Postgres Chat Memory in n8n using a Supabase Postgres database, but I can’t get it to work and I’m stuck.
The screenshots show what I’ve done so far.
The credentials save, but I get an error notification.
Any help would be greatly appreciated. Thanks in advance!
Hi @Sanders_Rohling_Immo , welcome to the n8n community !
Could you please share “more details” about the message in red that appears?
Are you using port 5432 or 6543?
Hi @Sanders_Rohling_Immo Welcome!
What you are trying to do can be done and there is no bad about it, but i recommend using official SUPABASE nodes within n8n to perform any action related to supabase, they are more easy to setup and does not require much effort and can be get going in minutes.
@Sanders_Rohling_Immo Understood. Please consider REVOKING your credentials and then trying again to setup the PostgrSQL Memory, let me know if this works as revoking them would refresh the settings on both ends.
@Sanders_Rohling_Immo No, I didn’t mean revoking the database password. What I meant is that you should revoke/refresh your n8n API/connection credentials for Supabase (the Postgres credentials inside n8n) and then reconnect them, so the connection settings get refreshed on both sides.
@Sanders_Rohling_Immo
Happy to help. Just to confirm, have you already checked if SSL is enabled in the Postgres credentials in n8n? You can find it under Postgres Credentials, then Additional Options, and SSL.
So, my concern now is the changes you made that caused an error in something that could be the solution. I recommend making a checklist and validating all the steps, one at a time.
@Sanders_Rohling_Immo I guess now try using supabase’s Postgres connection string (host, port 5432, database, user, password, SSL required) directly in the n8n Postgres credential and select that in the Chat Memory node instead of any Supabase API keys. Let me know if this helps.
Let me elaborate that: Use a Postgres credential in n8n with your Supabase DB details, not any Supabase API key.
In Supabase settings > database, copy the Postgres connection string and map it like this in n8n’s Postgres credential:
Host: db.someHost.supabase.co
Port: 5432
Database: postgres
User: postgres
Password: your Supabase DB password
SSL: Require
Save and Test this Postgres credential, then select it in the Postgres Chat Memory node. If the test still fails, share the full error message and a screenshot of that Postgres credential (with password hidden). This will give us more context to see what exactly is the error
The Error:"No testing function found for this credential." is not a connection failure. It simply means that n8n’s “Test Connection” button logic does not exist for this specific type of Postgres setup. The button itself is failing, but your credentials might actually be correct
**
Step 1: Ignore the Test Button**
Close the credential window (click “X” or “Save” if allowed).
Execute the Node directly in your workflow (click “Execute Step”).
Step 2: The “IPv6” Trap (If execution fails)
If you try Step 1 and the node spins forever or errors out with “ETIMEDOUT”, you are hitting the Supabase IPv6 issue.
The Problem: You are using the Direct URL (db.aaqac...). This URL is IPv6 only. Most Docker containers (self-hosted n8n) do not have IPv6 enabled by default, so they cannot reach this address.
The Fix: You must use the Supavisor (Pooler) URL, but in Session Mode.
How to get the correct IPv4-compatible settings:
Go to Supabase → Connect.
Change Mode to Session (this is critical).
Copy the Host: It should look like aws-0-[region].pooler.supabase.com (NOT db.aaqac...).
Copy the Port: It should be 5432 (NOT 6543). Try Step 1 first. If that fails, apply Step 2.
!
. I am using port 6543.
