Actions40
- Customer Actions
- Inventory Actions
- Order Actions
- Products Actions
- Shipping and fulfillment Actions
- Location Actions
Shipping and fulfillment → Update Fulfillment
AI-generatedOverview
This node integrates with the Haravan platform to handle various resources and operations related to e-commerce management, such as orders, products, and accounts. Specifically, for the "Shipping and fulfillment" resource with the "Update Fulfillment" operation, it allows users to update fulfillment details of an order in Haravan.
Typical use cases include:
- Automatically updating shipment status or tracking information after a package is dispatched.
- Synchronizing fulfillment data between Haravan and other systems like warehouses or shipping providers.
- Triggering workflows based on fulfillment updates to notify customers or update inventory.
Properties
| Name | Meaning |
|---|---|
| Options | A collection of optional fields to customize the request behavior. |
| - Logging Request | Boolean option to enable logging of each API request sent to Haravan for debugging purposes. |
The node supports additional properties depending on the selected resource and operation, but for the "Update Fulfillment" operation under "Shipping and fulfillment," the main configurable property is the "Logging Request" option.
Output
The node outputs JSON data representing the result of the fulfillment update operation. The output structure includes:
executionId: The unique identifier of the current execution.resource: The resource type, here "Shipping and fulfillment".operation: The operation performed, here "Update Fulfillment".status: The status of the operation, typically "completed".timestamp: The ISO string timestamp when the operation was executed.
If multiple items are processed, the output is an array of such JSON objects, one per input item.
No binary data output is indicated by the source code.
Dependencies
- Requires an API key credential to authenticate with the Haravan platform.
- Depends on the external Haravan API service for performing fulfillment updates.
- The node uses internal helper libraries (bundled) for interacting with Haravan's API.
Troubleshooting
Common issues:
- Authentication failures due to invalid or missing API credentials.
- API rate limits or network connectivity problems causing request failures.
- Incorrect or incomplete fulfillment data leading to API errors.
Error messages:
- Errors thrown during execution will include the item index for easier debugging.
- Enabling the "Logging Request" option can help trace API requests and responses to identify issues.
- If "Continue On Fail" is enabled, failed items will be returned with error details instead of stopping the workflow.
Links and References
- Haravan Official API Documentation
- n8n documentation on Creating Custom Nodes