ActionBaserowUpdated June 2026

How do I get the schema of a Baserow table?

Short answer: You can get table fields in Baserow by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Baserow Get Table Fields 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.

Use this action All 10 Baserow actions

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: 456

Sample request

{
  "table_id": "e.g. 456"
}

Returns

[
  {
    "id": 1,
    "name": "Name",
    "type": "text",
    "primary": true
  },
  {
    "id": 2,
    "name": "Email",
    "type": "email"
  }
]

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

FAQ

Questions about Get Table Fields.

What does the Get Table Fields action do in Baserow?

Returns the column definitions for a table — each field's name, ID, type, and configuration (e.g., link to another table, formula, single/multi-select options). Useful at workflow-build time to validate field types before writes.

What inputs does Get Table Fields 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 Get Table Fields support batch operations?

Yes. Run Get Table Fields 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.

How do I get the schema of a Baserow table?

The fields this action accepts.

Apps that pair well as the trigger for Get Table Fields.

Questions about Get Table Fields.

Other Baserow actions.