Row → Update
AI-generatedOverview
This node updates a specific row in a Baserow database table. It allows you to select the target database and table, specify the row by its ID, and define which fields to update—either by auto-mapping input data or by specifying each field and value manually. This is useful for workflows that need to modify existing records in Baserow based on dynamic or static data.
Common scenarios:
- Updating customer information in a CRM table when new data arrives.
- Modifying inventory quantities after a sale.
- Synchronizing changes from another system into Baserow.
Example:
If you receive updated user details from an external API, you can use this node to find the corresponding row in your Baserow "Users" table (by Row ID) and update their email or status fields.
Properties
| Name | Type | Meaning |
|---|---|---|
| Database Name or ID | options | The Baserow database to operate on. You can select from a list or provide an ID via expression. |
| Table Name or ID | options | The table within the selected database. Select from a list or provide an ID via expression. |
| Row ID | string | The unique identifier of the row you want to update. |
| Data to Send | options | Determines how the data is provided: - Auto-Map Input Data to Columns: Uses incoming JSON keys as column names. - Define Below for Each Column: Manually specify each field and value to update. |
| Inputs to Ignore | string | (Only with Auto-Map) Comma-separated list of input properties to exclude from updating. Leave empty to send all properties. |
| Fields to Send | fixedCollection | (Only with Define Below) List of fields to update, where each entry specifies: - Field Name or ID: The column to update. - Field Value: The new value for that column. |
Output
The output is a JSON object representing the updated row, with field names mapped to their human-readable names (not internal IDs).
Example output:
{
"id": 123,
"Name": "John Doe",
"Email": "john@example.com",
"Status": "Active"
}
- All columns of the updated row are included.
- If the operation fails and "Continue On Fail" is enabled, the output will include an
errorproperty with the error message.
Dependencies
- External Service: Requires access to a Baserow instance.
- API Key: Needs valid Baserow API credentials configured in n8n under the name
baserowApi. - Environment: No special environment variables required beyond standard n8n credential setup.
Troubleshooting
Common Issues:
- Invalid Database/Table/Row ID: If the provided IDs do not exist, the node will throw an error such as "Not found" or "Invalid ID".
- Missing Required Fields: If required fields are omitted, Baserow may reject the request.
- Field Mapping Errors: If using auto-map, ensure input keys match Baserow column names exactly.
- Authentication Errors: If credentials are missing or invalid, errors like "401 Unauthorized" will occur.
Error Handling:
- If "Continue On Fail" is enabled, failed items will output an
errorproperty with the error message and an emptyjsonobject.