Search Rows
baserow.search_rows
ActionDatabases & warehousesconnection required
Calls the Baserow API with the connection's credentials.
Walk every page of a table and return the rows matching a search term, up to a row cap.
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
8 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_id Numeric id of the table, from its URL in Baserow. Overrides the id on the connection. | string | No | — | — | 1234 |
search Text to look for in any cell of the row. | string | Yes | — | — | — |
order_by Comma-separated fields to sort by; prefix one with '-' for descending order. | string | No | — | — | -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. | object | No | — | — | {"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. | string | No | — | — | — |
max_rows Stop after this many rows; the output says whether the cap truncated it. | number | No | 200 | 1–10000 | — |
page_size How many rows to ask for per request while paging. | number | No | 200 | 1–200 | — |
user_field_names Use the field names shown in Baserow as keys. Turn off to use field_<id> keys instead. | boolean | No | true | — | — |
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"
}
]
},
"max_rows": 200,
"order_by": "-Created on",
"page_size": 200,
"table_id": "1234",
"user_field_names": true
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
items Every matching row that was fetched. | array | — |
count How many rows were fetched. | number | — |
total How many rows Baserow says match in total. | number | — |
pages How many pages were requested. | number | — |
truncated True when max_rows stopped the walk before the last page. | boolean | — |
table_id The table the rows came from. | number | — |
{
"count": 0,
"items": [],
"pages": 0,
"table_id": 0,
"total": 0,
"truncated": false
}Notes
- This issues one request per page, so a wide cap on a large table is several calls; narrow it with filters or a view where you can.
See Search 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.