List Rows

baserow.list_rows
ActionDatabases & warehousesconnection required

Calls the Baserow API with the connection's credentials.

Fetch one page of rows from a table, with optional search, sort, filter tree and view.

Connection

Required
Yes — the node will not save without one
Auth type
API key
Providers
Baserow
Secret shape
the database token, or {"token": "…"}
Config it needs
base_url, table_id
Resolved by
config.connection_id, else node.connection_id

Configuration

10 fields, none required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
table_id
Numeric id of the table, from its URL in Baserow. Overrides the id on the connection.
stringNo——1234
page
Which page of rows to fetch, counting from 1.
numberNo11–1000000—
size
How many rows per page. The instance's own cap still applies: 200 on hosted Baserow, whatever BASEROW_ROW_PAGE_SIZE_LIMIT says self-hosted.
numberNo1001–10000—
search
Only return rows with a cell matching this text.
stringNo———
order_by
Comma-separated fields to sort by; prefix one with '-' for descending order.
stringNo——-Created on
filters
A Baserow filter tree, e.g. {"filter_type": "AND", "filters": [{"field": "Status", "type": "equal", "value": "todo"}]}. Field names follow user_field_names.
objectNo——{"filter_type":"AND","filters":[{"field":"Status","type":"equal","value":"todo"}]}
view_id
Numeric id of a view whose own filters and sorts should be applied as well.
stringNo———
include
Comma-separated list of the only fields to return.
stringNo———
exclude
Comma-separated list of fields to leave out of the response.
stringNo———
user_field_names
Use the field names shown in Baserow as keys. Turn off to use field_<id> keys instead.
booleanNotrue——

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "filters": {
    "filter_type": "AND",
    "filters": [
      {
        "field": "Status",
        "type": "equal",
        "value": "todo"
      }
    ]
  },
  "order_by": "-Created on",
  "page": 1,
  "size": 100,
  "table_id": "1234",
  "user_field_names": true
}

Output

One shape.

result

FieldTypeExample
items
The rows on this page, in the table's order.
array—
count
How many rows this page returned.
number—
total
How many rows match in total, across every page.
number—
page
The page number that was fetched.
number—
has_more
True when Baserow reported a further page.
boolean—
next_page
The page number to fetch next, or null on the last page.
number—
table_id
The table the rows came from.
number—
{
  "count": 0,
  "has_more": false,
  "items": [],
  "next_page": 0,
  "page": 0,
  "table_id": 0,
  "total": 0
}

Notes

  • Baserow pages with page/size, not a cursor: follow next_page until has_more is false, or use Search Rows to walk the pages in one step.

See List Rows run in a workflow.

In a technical demo we add the Baserow connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.