Supabase node common issues#

Here are some common errors and issues with the Supabase node and steps to resolve or troubleshoot them.

Filtering rows by metadata#

To filter rows by Supabase metadata, set the Select Type to String.

From there, you can construct a query in the Filters (String) parameter to filter the metadata using the Supabase metadata query language, inspired by the MongoDB selectors format. Access the metadata properties using the Postgres ->> arrow JSON operator like this (curly brackets denote components to fill in):

1	`metadata->>{your-property}={comparison-operator}.{comparison-value}`

For example to access an age property in the metadata and return results greater than or equal to 21, you could enter the following in the Filters (String) field:

1	`metadata->>age=gte.21`

You can combine these operators to construct more complex queries.

Records are accessible through Postgres but not Supabase#

If queries for records return empty using the Supabase node, but are available through the Postgres node or with a Postgres client, there may be a conflict with Supabase's Row Level Security (RLS) policy.

Supabase always enables RLS when you create a table in a public schema with the Table Editor. When RLS is active, the API doesn't return any data with the public anon key until you create policies. This is a security measure to ensure that you only expose data you intend to.

To access data from a table with RLS enabled as the anon role, create a policy to enable the access patterns you intend to use.