ActionBaserowUpdated September 2026

How do I list rows from a Baserow table?

Short answer: You can list rows in Baserow by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Baserow List Rows action to a workflow, map its 5 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

List Rows in Baserow — start free All 10 Baserow actions

List Rows in Baserow — start free

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.

Triggered by

Apps that pair well as the trigger for List Rows.

Any of these apps can fire this action as part of a workflow.

Google Sheets → Baserow

2 Google Sheets triggers

HubSpot → Baserow

18 HubSpot triggers

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 run history shows the failed step with its input and the error message Baserow returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does List Rows support batch operations?

Run List Rows inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Baserow's rate limits.

More actions