Select Rows
supabase.select
ActionDatabases & warehousesconnection required
Calls the Supabase API with the connection's credentials.
Read rows from a table or view through PostgREST, narrowing them with structured filters, a column list, an ordering and limit/offset paging.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- Supabase
- Secret shape
- the project API key, or {"api_key": "…"} / {"service_role_key": "…"}
- Config it needs
- base_url, schema
- Resolved by
- config.connection_id, else node.connection_id
Configuration
7 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
table The table or view to act on, in the connection's schema. | string | Yes | — | — | orders |
select Columns to return, comma separated (PostgREST 'select='). Embedded resources are allowed, e.g. id,total,customer(name,email). Defaults to * (every column). | string | No | — | — | id,total,created_at |
filters Rows to return. PostgREST filters as a list of objects, e.g. [{"column": "status", "operator": "eq", "value": "active"}, {"column": "id", "operator": "in", "value": [1, 2, 3]}]. Supported operators: eq, neq, gt, gte, lt, lte, like, ilike, match, imatch, in, is, isdistinct, fts, plfts, phfts, wfts, cs, cd, ov. Add "negate": true to invert one filter (not.eq). Values for 'in' take a list; 'is' takes null, not_null, true, false or unknown. An expression may also supply a plain {"column": value} object, which is shorthand for equality on each key. Leave empty to return every row. | array | No | — | array of object | — |
order Ordering, as PostgREST spells it: column.asc, column.desc, or a comma-separated list. Add .nullsfirst / .nullslast to place nulls. | string | No | — | — | created_at.desc |
limit Maximum rows to return. Leave unset for the project's PostgREST default (1000 rows on Supabase's hosted platform). | number | No | — | ≥ 1 | — |
offset Rows to skip before returning any — page N is offset = N * limit. | number | No | — | ≥ 0 | — |
schema Postgres schema for this call (sent as Accept-Profile / Content-Profile). Overrides the connection's schema; leave blank for the connection default. | string | No | — | — | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"order": "created_at.desc",
"select": "id,total,created_at",
"table": "orders"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
table The table the call was made against. | string | — |
items The rows PostgREST returned (Prefer: return=representation). | array | — |
count How many rows were returned. | number | — |
{
"count": 0,
"items": [],
"table": ""
}Notes
- A service_role (or sb_secret_…) key has BYPASSRLS and skips every Row Level Security policy on the project; an anon/publishable key is filtered by them.
See Select Rows run in a workflow.
In a technical demo we add the Supabase connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.