BaserowAdvanced icon

BaserowAdvanced

Consume the Baserow API
Join our community

Actions5

Overview

The BaserowAdvanced node's "Row: Update" operation allows you to update an existing row in a specified table within a Baserow database. This is useful for workflows where you need to modify data records, such as updating user information, changing order statuses, or correcting entries in your Baserow tables. The node supports both single and batch updates, and offers flexible ways to map input data to table columns.

Example scenarios:

  • Automatically update customer details when receiving new information from another system.
  • Batch-update inventory levels based on recent sales data.
  • Correct multiple rows in a table using data from another source.

Properties

Name Meaning
Database Name or ID Select the Baserow database to operate on. You can choose from a list or specify an ID using an expression.
Table Name or ID Select the table within the chosen database. Options are loaded dynamically based on the selected database.
Process in Batches If enabled, updates will be processed in batches for efficiency (recommended for large datasets).
Max Batch Size Maximum number of rows to process in each batch when batch processing is enabled.
Row ID The ID of the row to update. Required for the update operation.
Data to Send Choose how to provide the data for updating:
- Auto-Map Input Data to Columns: Automatically maps incoming JSON fields to table columns with matching names.
- Define Below for Each Column: Manually specify which fields to update and their values.
Inputs to Ignore (Only shown if "Auto-Map Input Data to Columns" is selected) Comma-separated list of input properties to exclude from the update. Leave empty to send all properties.
Fields to Send (Only shown if "Define Below for Each Column" is selected) Specify one or more fields to update:
- Field Name or ID: Select or enter the column.
- Field Value: Value to set for the field.

Output

  • The output is a JSON object representing the updated row(s), with field names mapped to their human-readable names (not internal IDs).
  • For batch operations, an array of such objects is returned, each corresponding to an updated row.
  • Example output:
    [
  {
    "id": 123,
    "Name": "John Doe",
    "Email": "john@example.com",
    "Status": "Active"
  }
]
  • If the operation is successful, the output contains the updated row data. If an error occurs and "Continue On Fail" is enabled, the output includes an error property with the error message.

Dependencies

  • External Service: Requires access to a Baserow instance (cloud or self-hosted).
  • API Key: Needs valid Baserow API credentials configured in n8n under the name baserowApi.
  • n8n Configuration: No special environment variables required beyond standard credential setup.

Troubleshooting

Common Issues:

  • Invalid Row ID: If the provided Row ID does not exist, the node will throw an error indicating the row was not found.
  • Missing Required Fields: If required fields are missing (e.g., Row ID, Table ID), the node will fail with a descriptive error.
  • Permission Denied: If the API key lacks permission to update the specified table/row, an authentication or authorization error will occur.
  • Batch Size Too Large: Setting a very high batch size may result in timeouts or API errors.

Error Messages & Resolutions:

  • "Row not found": Check that the Row ID exists in the selected table.
  • "Invalid credentials": Ensure the Baserow API credentials are correct and have sufficient permissions.
  • "Field does not exist": Verify that the field names/IDs used match those in the target table.

Links and References

Discussion