Overview
This node is designed to update records of a custom resource in an external system. It allows users to specify which custom resource to target, identify the specific record by its ID, and then update one or more fields with new values. This functionality is useful when you need to programmatically modify existing data entries, such as updating user information, product details, or any other customizable entity managed by the external system.
Practical examples include:
- Updating a customer's contact information after receiving new data.
- Modifying the status or attributes of a project task.
- Changing configuration settings stored as custom resource records.
Properties
| Name | Meaning |
|---|---|
| Custom Resource Name or ID | Select the custom resource type from a list or specify its ID via an expression. |
| Custom Resource ID | The unique identifier of the specific record within the chosen custom resource that you want to update. |
| Fields | A collection of fields to update on the record. Each entry includes: |
| - Field Name or ID | The name or ID of the field to update, selectable from a list or specified via expression. |
| - New Value | The new value to assign to the specified field. |
Output
The node outputs JSON data representing the updated record(s) of the custom resource. This typically includes the fields after modification, reflecting the new values set during the update operation.
If the external system supports binary data for these resources, the node may also output binary data associated with the updated record, but this is not explicitly detailed in the provided code.
Dependencies
- Requires connection to an external system that manages custom resources.
- Needs appropriate API credentials or authentication tokens configured in n8n to access and modify the custom resource data.
- Utilizes internal methods for loading options dynamically (e.g., available models and fields), indicating dependency on the external system's API endpoints for metadata retrieval.
Troubleshooting
- Missing or invalid Custom Resource ID: The update operation requires a valid record ID. Ensure the ID is correct and exists in the external system.
- Field names or IDs not found: If the specified field does not exist in the selected custom resource, the update will fail. Verify field names are accurate and loaded properly.
- Authentication errors: Failure to authenticate with the external system will prevent updates. Check API credentials and permissions.
- Empty or malformed field values: Providing empty or incorrect values might cause the update to be rejected. Validate input data before execution.
Common error messages likely relate to invalid identifiers, permission issues, or network/API errors. Resolving them involves verifying inputs, credentials, and connectivity.
Links and References
- n8n Expressions Documentation
- Refer to the external system's API documentation for details on custom resource structure and update operations.