Actions40
- Customer Actions
- Inventory Actions
- Order Actions
- Products Actions
- Shipping and fulfillment Actions
- Location Actions
Order → Update Order
AI-generatedOverview
This node integrates with the Haravan platform, specifically allowing users to update orders among other resources. It is designed to listen for events such as orders, products, and accounts, and trigger workflows accordingly. The "Update Order" operation enables modifying existing order data on Haravan, which is useful for automating order management tasks like updating order status, customer details, or other order-related information.
Practical examples include:
- Automatically updating order statuses based on external triggers.
- Modifying shipping or billing information when certain conditions are met.
- Syncing order updates from Haravan to other systems via n8n workflows.
Properties
| Name | Meaning |
|---|---|
| Options | A collection of optional fields to customize the update request. |
| - Logging Request | Boolean option to enable logging of each API request sent to Haravan for debugging purposes. |
Output
The node outputs an array of JSON objects representing the result of the update operation(s). Each output item contains metadata about the execution, including:
executionId: Unique identifier for the current execution.resource: The resource type involved (e.g., "Order").operation: The operation performed (e.g., "Update Order").status: Status of the operation, typically"completed".timestamp: ISO string timestamp marking 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.
- 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 errors if the Haravan API endpoint is unreachable.
- Errors in input data format causing the update operation to fail.
Error messages:
- The node throws detailed errors wrapped in a standard error object, including the item index where the failure occurred.
- If "continue on fail" is enabled, failed items are returned with their error details instead of stopping the workflow.
Resolution tips:
- Verify that the API key credential is correctly set up and has necessary permissions.
- Ensure network connectivity to Haravan's API.
- Validate input data conforms to expected formats before running the node.