Update Rows (Batch)

baserow.update_rows

ActionDatabases & warehousesconnection required

Calls the Baserow API with the connection's credentials.

Change up to 200 rows in one request, each identified by its id.

Connection

3 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

Field	Type	Required	Default	Constraints	Example
table_id Numeric id of the table, from its URL in Baserow. Overrides the id on the connection.	string	No	—	—	1234
rows The rows to update: a list of objects that each carry the row's 'id' plus the values to write, at most 200 of them.	array	Yes	—	≥ 1 characters; array of object	[{"Status":"done","id":42}]
user_field_names Use the field names shown in Baserow as keys. Turn off to use field_<id> keys instead.	boolean	No	true	—	—

Every value below is the contract’s own example or default — nothing invented.

{
  "rows": [
    {
      "Status": "done",
      "id": 42
    }
  ],
  "table_id": "1234",
  "user_field_names": true
}

One shape.

Field	Type	Example
items The rows Baserow wrote, as they now stand.	array	—
count How many rows were written.	number	—
table_id The table that was written to.	number	—

{
  "count": 0,
  "items": [],
  "table_id": 0
}

The batch is atomic: an entry without an 'id', or one Baserow rejects, fails the whole request and writes nothing.

In a technical demo we add the Baserow connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.