Overview
The Undb node for n8n allows you to interact with the Undb API, specifically to update records in a specified table. The "Record: Update" operation is used to modify existing records by their ID, either by auto-mapping input data to fields or by explicitly defining which fields to update and their new values.
Common scenarios:
- Updating customer information in a CRM table.
- Modifying order statuses in an e-commerce database.
- Correcting or enriching data in any custom Undb table.
Practical example:
Suppose you have a workflow that receives updated user details from another system. You can use this node to find the corresponding record in Undb (by Record ID) and update only the changed fields.
Properties
| Name | Meaning |
|---|---|
| Authentication | Selects the authentication method for connecting to Undb. Options: "Api Token", "Auth Api Token". |
| Table Name or ID | The ID of the table where the record exists. You can select from a list or specify an ID using an expression. |
| Record ID | The unique identifier of the record to update. Required for the update operation. |
| Data to Send | Determines how to provide the data for updating the record: - "Auto-Map Input Data to Fields": Automatically maps incoming data properties to destination fields. - "Define Below for Each Field": Manually define each field and value to update. |
| Fields to Send | (Shown if "Define Below for Each Field" is selected) Allows you to specify one or more fields to update, each with: - Field Name: The name of the field to update. - Field Value: The new value for the field. |
Output
- The output will be a JSON object representing the updated record as returned by the Undb API.
- Typical structure includes all fields of the record after the update, such as IDs, timestamps, and the updated field values.
- No binary data is produced by this operation.
Example output:
{
"id": "rec123",
"name": "Updated Name",
"email": "new@email.com",
"status": "active",
"updatedAt": "2024-06-01T12:34:56Z"
}
Dependencies
- External Service: Requires access to the Undb API at
https://demo.undb.com. - Authentication: Needs either an "Api Token" or "Auth Api Token" credential configured in n8n.
- n8n Configuration: Credentials must be set up in the n8n instance under the appropriate authentication type.
Troubleshooting
- Invalid operation error: If an unsupported operation is selected, the node will throw an error like
Invalid operation update. Ensure the operation is correctly set to "Update". - Missing required fields: If "Table Name or ID" or "Record ID" are not provided, the node will fail. Double-check that these fields are filled.
- Authentication errors: If credentials are missing or incorrect, you may receive authorization errors from the Undb API. Verify your API tokens and credential setup.
- Field mapping issues: When using "Auto-Map Input Data to Fields", ensure your input data keys match the destination field names in Undb.
Links and References
- n8n Documentation: Expressions
- Undb API Documentation (refer to official documentation for API details)
- n8n Credentials Setup Guide