Overview
The node "Llotus Tables" integrates with NocoDB to perform various operations on database tables, specifically focusing here on the Row Update operation. It allows users to update existing rows in a specified table by sending new data for one or more columns. This is useful when you want to modify records programmatically based on input data from previous nodes or external sources.
Common scenarios include:
- Updating customer information in a CRM table.
- Modifying inventory quantities in a stock management system.
- Changing status fields in task or project management databases.
For example, if you have an automation that processes incoming orders, you can use this node to update the order status or add shipment tracking details directly into your NocoDB table rows.
Properties
| Name | Meaning |
|---|---|
| Authentication | Choose the authentication method: either using an API Token or a User Token. |
| API Version | Select the API version to use (currently only v0.200.0 onwards supported). |
| Workspace Name or ID | The workspace context under which the base/project exists (only for API version 3). |
| Base Name or ID | The base or project within the workspace where the target table resides. Required for all versions. |
| Table Name or ID | The specific table in the base/project where the row update will occur. Required. |
| Primary Key Type | Defines the primary key field type used to identify rows (Default id, Airtable imported ncRecordId, or Custom primary key name). Relevant for API versions 1 and 2. |
| Field Name (Custom Primary Key) | If using a custom primary key, specify its field name here. |
| Row ID Value | The value of the primary key identifying the row to update. Required for API versions 1 and 2. |
| Data to Send | How to provide the data for updating the row: - Auto-map input data fields to columns (input JSON keys must match column names). - Define each column's value manually below. - Use the table schema to select fields. |
| Inputs to Ignore | When auto-mapping input data, list any input properties to exclude from being sent to the table. |
| Fields to Send | When defining data manually, specify each field's name and value. Supports binary data upload by referencing binary properties from previous nodes. |
Output
The output is a JSON array where each element corresponds to a processed input item. For the update operation, each output item contains the updated row data merged with the response from the API, including any changes made by the server.
If binary data is uploaded as part of the update (e.g., file attachments), the node handles uploading these files separately and includes references to them in the updated row data.
Dependencies
- Requires access to a NocoDB instance with appropriate permissions.
- Needs either an API token or user token for authentication.
- Uses NocoDB REST API endpoints, primarily
/api/v2/tables/{table}/recordswith PATCH method for updates. - For binary uploads, uses
/api/v2/storage/uploadendpoint. - Node settings require specifying API version and selecting workspace/base/table via dynamic options loaded from NocoDB.
Troubleshooting
Error: Missing or invalid primary key
Ensure the correct primary key type and value are provided. For API versions 1 and 2, the primary key field and its value must be set correctly to identify the row to update.Error: Table or base not found
Verify that the workspace, base/project, and table IDs or names are correct and accessible with the provided credentials.Binary upload failures
Check that the binary property names are correct and that the binary data exists on the input item. Also, ensure the API token has permission to upload files.API rate limits or network errors
These may cause request failures; consider enabling "Continue On Fail" to allow partial processing.Empty or unexpected responses
Confirm that the row ID exists in the table and that the API version matches the expected schema.