Actions40
- Customer Actions
- Inventory Actions
- Order Actions
- Products Actions
- Shipping and fulfillment Actions
- Location Actions
Customer → Update
AI-generatedOverview
This node integrates with the Haravan platform, allowing users to interact with various Haravan resources such as orders, products, and customers. Specifically, for the Customer - Update operation, it enables updating customer information on the Haravan system. This is useful in scenarios where customer data needs to be synchronized or modified automatically based on workflow triggers, such as updating contact details after a form submission or modifying customer tags after a purchase.
Practical examples include:
- Automatically updating customer addresses when they change via an external CRM.
- Modifying customer metadata or custom fields based on user behavior tracked in other systems.
- Enabling workflows that keep customer records consistent across multiple platforms.
Properties
| Name | Meaning |
|---|---|
| Options | A collection of optional settings for the update operation. |
| - Logging Request | Boolean flag to enable logging of each API request sent to Haravan for debugging purposes. |
The "Options" property currently supports one option:
- Logging Request: When enabled, the node logs detailed information about each API request made during the update process, which helps in troubleshooting and debugging.
Output
The node outputs an array of JSON objects representing the result of the update operations performed on the customer resource. Each output item contains at least the following fields:
executionId: The unique identifier of the current execution.resource: The resource type involved (e.g., "Customer").operation: The operation performed (e.g., "Update").status: The status of the operation, typically"completed".timestamp: The ISO string timestamp when the operation was completed.
If multiple items are processed, the output will be an array of such objects, one per input item.
No binary data output is indicated by the source code.
Dependencies
- Requires an API key credential for authenticating with the Haravan platform.
- The node depends on the Haravan API being accessible and properly configured.
- No additional environment variables or external services are explicitly required beyond the API authentication.
Troubleshooting
Common Issues:
- Failure to authenticate due to missing or invalid API credentials.
- Network connectivity issues preventing access to the Haravan API.
- Incorrect resource or operation parameters leading to unexpected results or errors.
Error Messages:
- Errors thrown during execution will include the item index to help identify which input caused the failure.
- If the node is set to continue on fail, errors will be included in the output alongside the original input data for easier debugging.
- Enabling the "Logging Request" option can provide detailed logs of API requests to diagnose issues related to request formatting or API responses.
Links and References
- Haravan Official API Documentation
- n8n Documentation on Creating Custom Nodes
- General API integration best practices for n8n workflows
Note: The provided source code snippet shows a generic execute method that sets operation status and timestamps but does not reveal the detailed API call logic for updating customers. The description and properties are inferred from the available metadata and typical usage patterns.