ActionBaserowUpdated May 2026
How do I list rows from a Baserow table?
Short answer: Drop the "Baserow → List Rows" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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.
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
Other Baserow actions.
Action
Batch Create Rows
Creates multiple rows in one API call — much more efficient than per-row Create Row for ingestion workflows. Up to ~200 rows per call. For "ingest CSV upload into Baserow" or "sync 500 leads from CRM" workflows, this is the right path.
ActionBatch Delete Rows
Removes multiple rows by ID list. Useful for cleanup workflows — "delete all rows older than N days", "remove rows matching this status after archival to warehouse".
ActionBatch Update Rows
Updates multiple rows in one call. Each entry has the row ID + the fields to change. Useful for sync workflows that reconcile Baserow with an external source (e.g., "update prices on 200 product rows from a price-list sync").
ActionCreate Row
Inserts a single row into a Baserow table with field values keyed by field name or ID. For bulk ingestion (>20 rows), prefer Batch Create Rows which is significantly more efficient per-row.
ActionDelete Row
Removes a specific row by ID. Irreversible. For bulk deletes, use Batch Delete Rows. For "soft delete" semantics, add a deleted_at field rather than hard-deleting so you can audit.
ActionGet Row
Returns the row by ID with all field values typed per column. Use after List Rows or as a confirmation lookup before destructive operations.
Send list rows from your workflows.
Triggered by anything in the catalog. Free tier available. No credit card.
