List Rows: Baserow action

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Table ID table_id	string	Required	Table ID. Example: 42
Page page	string	Optional	Page. e.g. "1"
Page Size size	string	Optional	Max 200
Order By order_by	string	Optional	Field name, prefix with - for descending
Search search	string	Optional	Search across all fields

Sample request

{
  "table_id": "e.g. 42",
  "page": "1",
  "size": "100",
  "order_by": "e.g. -Name",
  "search": "{{trigger.search}}"
}

Returns

{
  "next": null,
  "count": 1,
  "results": [
    {
      "id": 1,
      "Name": "John",
      "order": "1.00000"
    }
  ],
  "previous": null
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about List Rows.

What does the List Rows action do in Baserow?

Returns paginated rows with optional filtering using Baserow's filter syntax (field_id__equal, field_id__contains, etc.). For sync workflows pulling many rows, paginate with page_size=200 (the max).

What inputs does List Rows require?

Required: Table ID. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Baserow returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does List Rows support batch operations?

Yes. Run List Rows inside a Loop node to process arrays. Tiny Command handles Baserow's rate limits automatically so you don't have to throttle manually.

More actions