Start free
ActionBaserowUpdated June 2026

What tables exist in this Baserow database?

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

List Tables in Baserow — start free All 10 Baserow actions
List Tables 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.

FieldTypeRequiredDescription
Database ID
database_id
stringRequiredDatabase ID. Example: 123
Sample request
{
  "database_id": "e.g. 123"
}
Returns
[
  {
    "id": 1,
    "name": "Contacts",
    "order": 1,
    "database_id": 123
  }
]

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

Triggered by

Apps that pair well as the trigger for List Tables.

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

Gmail → Baserow
1 Gmail triggers
Slack → Baserow
13 Slack triggers
Google Sheets → Baserow
2 Google Sheets triggers
HubSpot → Baserow
18 HubSpot triggers
FAQ

Questions about List Tables.

What does the List Tables action do in Baserow?
Returns every table in a Baserow database with name, ID, and row count. The lookup for resolving table IDs at workflow-build time and for inventorying database structure.
What inputs does List Tables require?
Required: Database 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 Tables support batch operations?
Yes. Run List Tables inside a Loop node to process arrays. TinyCommand 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.
Action
Batch 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".
Action
Batch 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").
Action
Create 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.
Action
Delete 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.
Action
Get 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.
List Tables in Baserow — start free