Create Row: 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
Row Data (JSON) field_data	string	Required	JSON object with field names as keys, e.g. {"Name": "John", "Email": "john@test.com"}

Sample request

{
  "table_id": "e.g. 42",
  "field_data": "{\"Name\": \"John\"}"
}

Returns

{
  "id": 1,
  "Name": "John",
  "Email": "john@test.com",
  "order": "1.00000"
}

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

FAQ

Questions about Create Row.

What does the Create Row action do in Baserow?

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.

What inputs does Create Row require?

Required: Table ID, Row Data (JSON). 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 Create Row support batch operations?

Yes. Run Create Row 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