Start free
ActionBaserowUpdated June 2026

How do I add a row to a Baserow table?

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

Create Row in Baserow — start free All 10 Baserow actions
Create Row 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
Table ID
table_id
stringRequiredTable ID. Example: 42
Row Data (JSON)
field_data
stringRequiredJSON 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.

Triggered by

Apps that pair well as the trigger for Create Row.

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 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. 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
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.
Action
Get Table Fields
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.
Create Row in Baserow — start free