Supabase: Select

Read rows from a Supabase table via the PostgREST API. Supports column projection, multiple filters, ordering, paging through arbitrarily large result sets, and runtime-bound filter values driven by an upstream JSON input.

The full result set is streamed to a JSONL file on the output (one row per line) — safe for large tables.

Pre-requisite: Install Supabase application in Profile > {Organization} > Applications. The Supabase API key must have read permission on the target table.

Parameters

Application—REQUIRED

Configured Supabase application (project URL + API key).

Table Name—REQUIRED

Target Postgres table name (PostgREST resource).

Select Columns

PostgREST select clause — comma-separated columns or a relation expression like id,name,profile(*). Empty means * (every column).

Filters

One or more PostgREST WHERE-style filters. Each filter is column op value. Values can be static (typed in the form) or dynamic (read from the JSON input at runtime via a dynamic key).

Page Size

Rows fetched per HTTP request. Smaller values reduce server load; larger values reduce round-trips. Defaults to 1000.

Limit

Maximum total rows to fetch across all pages. When omitted, the node keeps paging until the table is exhausted.

Offset

Rows to skip before the first page. Defaults to 0.

Order By

Optional column name passed to PostgREST order=. Empty means no ordering (PostgREST default).

Order Ascending

When Order By is set, sort ascending if enabled, descending otherwise.

Input

Trigger

Optional trigger to start the query.

Filters

Optional JSON whose keys provide values for filters configured with a dynamic key. Lets you parametrize the query at runtime.

Output

File—REQUIRED

JSONL file with one returned row per line.

Trigger

Fires once the query has been streamed to the file output.