Hey! That ENETUNREACH error usually means a network connectivity issue between n8n Cloud and your Supabase instance. Quick diagnosis steps:
Check if n8n Cloud IP is whitelisted in Supabase → Database → Project Settings → Network → IPv4 allow list (add 0.0.0.0/0 for testing, then restrict later)
Verify SSL mode in your connection string (usually ‘require’ for Supabase) — some proxies drop SSL
If you’re on n8n Cloud, you can’t directly test network connectivity — instead, try switching to Supabase’s connection pooler (port 6543) if you’re using a direct connection (port 5432), or vice versa.
Also: Are you using a direct Postgres connection or Supabase’s pooler? Pooler sometimes has stricter timeout settings. Have you tested this workflow locally first to rule out n8n Cloud infrastructure?
@Rudra_Bhattacharjee that error is IPv6 — n8n cloud can’t reach the IPv6 address supabase gave you. go to supabase dashboard → project settings → database, copy the connection string under “URI” with the IPv4 toggle ON, use that in your postgres credentials instead. here’s a minimal agent + postgres memory setup:
plug your supabase postgres creds (with the IPv4 URI) into the memory node, add your openai key to the model node, should connect right away.
I have seen this a couple times with n8n + Supabase setups that ENETUNREACH error usually isn’t about the credentials or node config itself.
It’s more of a network/connectivity issue, especially when IPv6 gets involved with cloud instances.
Most people try to fix it from the database side, but the issue is often happening earlier in the connection layer.
Quick question are you connecting using the default Supabase connection string or a modified one?