Duaer

Integrations

Common issues with Supabase in Duaer

Common Supabase node issues in Duaer: filtering by metadata, Docker connections, and rows visible in Postgres but not Supabase.

Filter rows by metadata

Set Select Type to String and write Filters (String) as metadata->>property=operator.value, such as metadata->>age=gte.21. For values from expressions, write $1 and fill it in Filters (String) Parameters.

Cannot connect to a local Supabase from Docker

  • Only Supabase in Docker (official Docker Compose): set Host in the Supabase credential to http://localhost:8000.
  • Separate containers: put both on one Docker network and use the API gateway container name, http://supabase-kong:8000 by default.

Rows visible in Postgres but not Supabase

Usually Row Level Security (RLS). Tables created in the Table Editor have RLS on, and without policies a public key sees no rows. Put the project secret key (or legacy service_role) in Secret Key on the Supabase credential, not the publishable or anon key, or create policies for that role in Supabase.

Questions

Why does the Duaer Supabase node return no rows?

Usually RLS. Use a secret key in the Duaer Supabase credential, or create policies for that role in Supabase.

In this section