Short answer: Drop the "Baserow → Update Row" 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. |
Row ID row_id | string | Required | The Row ID assigned by Baserow. Find via the corresponding list/search operation in this app. Use the exact ID, not a name or label. |
Fields to Update (JSON) field_data | string | Required | Fields to Update (JSON). e.g. "{"Name": "Updated Name"}" |
{"table_id": "{{trigger.table_id}}","row_id": "{{trigger.row_id}}","field_data": "{\"Name\": \"Updated Name\"}"}
{"id": 1,"Name": "Updated Name"}
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.