Supabase

Read and write rows in a Supabase database, or call one of its functions, so your workflow’s data lands in a real table you can query and share.

Needs a Supabase connection — 

Pick a saved connection in the Credential field, or create one from there. It signs in with a Bearer Token.

Connect Supabase →

What it does

Pick an Operation:

• Select rows: read rows from a table, with optional filters, chosen columns and a limit.
• Insert row: add one row.
• Update rows: change the rows that match your filters.
• Upsert row: add a row, or update it if a row with the same key already exists.
• Delete rows: remove the rows that match your filters.
• Call function (RPC): run a Postgres function in your database with named arguments.

Update rows and Delete rows refuse to run without at least one filter, so a missing filter can never change or erase a whole table.

The node uses your project’s anon (public) key. What that key may read and write is decided by the Row Level Security (RLS) policies on each table. If you paste the secret service_role key by mistake, the node stops before sending anything, because that key ignores RLS.

Where Data Store keeps small values in your browser, Supabase keeps them in a database outside it.

When to use it

• Collect scraped prices, job offers or leads into a table, one row per run.
• Check whether a record already exists before acting on it.
• Mark rows as processed after a workflow handled them.
• Trigger logic you wrote in the database, such as a function that computes a report.

Inputs and settings

For every choice

Setting	Type	What it does
Credential REQ(required)	Credential	Your Supabase project’s anon (public) key, stored as a Bearer Token credential. Do NOT use the service_role key — it bypasses Row Level Security and is rejected. Access is enforced by your RLS policies.

6 choices · pick operation to see its settings

Select rowsInsert rowUpdate rowsUpsert rowDelete rowsCall function (RPC)

Settings for Select rows

Setting	Type	What it does
Project URL REQ(required)	URL	Your Supabase project URL (Project Settings → API), e.g. https://abcd.supabase.co.
Table REQ(required)	Text	The table name.
Columns	Text	Comma-separated columns to return, or * for all.
Filters	Key-value pairs	column → operator.value pairs, e.g. id → eq.42, age → gt.18, name → like.*acme* (PostgREST operators).
Limit	Number	Maximum rows to return.

Showing settings for Select rows

Need an operation that isn't listed? — 

Call the Supabase API yourself with the HTTP Request node, and pick the same connection in its Credential field.

Use HTTP Request →

• Project URL is the address shown in Supabase under Project Settings → API, like https://abcd.supabase.co. Do not add /rest/v1.

• Filters take the column name as key and operator.value as value. Common operators:

  Value	Means
  eq.42	equals 42
  neq.done	is not done
  gt.18 / lt.100	greater than 18 / less than 100
  like.*acme*	contains acme (case-sensitive; ilike ignores case)
  in.(new,open)	is one of the listed values
  is.null	is empty

  A value without an operator, like just 42, does not work.

• Columns is a comma-separated list such as id,title,price. Empty means all columns.

• Row and Fields take column names as keys. Use expressions for values, for example title → {{ $input.title }}.

• On conflict names the column that identifies the same row, for example url or email. That column needs a unique constraint in the table. Empty means the primary key.

Outputs

• Output

• Select rows returns the matching rows, one item per row.
• Insert row, Update rows, Upsert row and Delete rows return the rows as they are after the change (for Delete, the rows that were removed). An empty result on Update or Delete means no row matched the filters, or RLS hid them.
• Call function (RPC) returns whatever the function returns.

Dependencies and credentials

• Credential (connection, Bearer Token): required. See Connect Supabase.

Use your project’s anon public key, saved as a Bearer Token credential:

1. In Supabase, open Project Settings → API.
2. Copy the key labelled anon public. Do not use service_role (secret).
3. Create a Bearer Token credential with it. See Create a credential.

Then give the anon role the access the workflow needs with RLS policies on each table, for example a policy that allows insert on prices.

Example workflow

1. A Context Menu trigger adds “Save to my table” to the right-click menu.
2. Get Page Metadata reads the page’s url and title.
3. Supabase, Upsert row, Project URL https://abcd.supabase.co, Table saved_pages, Row url → {{ $input.url }} and title → {{ $input.title }}, On conflict url. Saving the same page twice updates its row instead of adding a second one.

Common issues

• “This is a Supabase service_role key, which bypasses Row Level Security…”. You saved the secret key. Replace it with the anon key in the credential.
• “Supabase Error: 401 … the request was blocked” (or 403). An RLS policy does not allow this operation for the anon role. Add a policy for it on the table in Supabase.
• “Update requires at least one filter…” / “Delete requires at least one filter…”. Add a filter such as id → eq.{{ $input.id }}.
• “Supabase Error: 404 …”. The Table or Function name is wrong, or the table is not in the public schema.
• Select returns an empty list. The filters match nothing, or RLS hides the rows from the anon role. Check the filter format (eq.42, not 42) and the table’s select policy.

Related nodes

• Data Store: keep small values in the browser, no account needed.
• Baserow / NocoDB: a spreadsheet-like database.
• Airtable: rows in an Airtable base.
• Http Request: call other Supabase services, such as Storage.