Short answer: Drop the "Baserow → Batch Update Rows" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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 | The Table ID assigned by Baserow. Find via the corresponding list/search operation in this app. Use the exact ID, not a name or label. |
Rows (JSON Array) items | json | Required | JSON array of row objects. Each object should have field names as keys. Example: [{"Name": "Alice", "Email": "alice@example.com"}] |
{"table_id": "{{trigger.table_id}}","items": "[{\"id\": 1, \"Name\": \"Updated\"}]"}
{"items": [{"id": 1,"Name": "Updated"}]}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.