Actions16
Overview
This node interacts with a cloud commerce platform to manage various resources such as customers, subscriptions, orders, and plans. Specifically, for the Customer - Update operation, it updates existing customer records by their unique ID. This is useful in scenarios where customer information needs to be modified or enriched after creation, such as updating tax IDs, adding external references, or changing descriptions.
Practical examples include:
- Updating a customer's tax identification number after receiving new documentation.
- Adding an external system reference ID to link customer data across platforms.
- Modifying the description field to reflect changes in customer status or notes.
Properties
| Name | Meaning |
|---|---|
| Customer ID | The unique identifier of the customer to update (string). |
| Additional Fields | Optional fields to update on the customer: |
| - Description | A textual description or notes about the customer. |
| - External ID | An external reference ID to associate with the customer. |
| - Tax ID | The tax identification number of the customer. |
Output
The node outputs JSON objects representing the updated customer data returned from the API. Each output item corresponds to one input item processed. The structure typically includes all relevant customer fields after the update, reflecting the new state of the customer record.
No binary data output is indicated in the source code.
Dependencies
- Requires an initialized API service client configured with appropriate credentials (e.g., an API key or authentication token) to communicate with the cloud commerce platform.
- The node depends on a resource registry that manages available resources and their operations.
- Proper configuration of the API credentials within n8n is necessary for successful execution.
Troubleshooting
- Resource Not Found Error: If the specified resource (e.g., "customer") is not recognized, ensure the node's resource parameter is correctly set and that the resource is supported by the integration.
- Operation Errors: Errors during execution may occur if the customer ID does not exist or if required fields are missing. Verify that the Customer ID is correct and that any additional fields conform to expected formats.
- API Authentication Failures: Ensure that the API credentials are valid and have sufficient permissions to perform update operations.
- Continue On Fail Behavior: If enabled, the node will continue processing subsequent items even if some fail, returning error messages in the output JSON under an
errorproperty.
Links and References
- No direct external links are provided in the source code. For more details, consult the cloud commerce platform’s official API documentation related to customer management and update operations.