Actions40
- Customer Actions
- Inventory Actions
- Order Actions
- Products Actions
- Shipping and fulfillment Actions
- Location Actions
Inventory → Get All
AI-generatedOverview
This node integrates with the Haravan platform to interact with various resources such as orders, products, and inventory. Specifically, for the Inventory resource with the Get All operation, it is designed to retrieve all inventory data from Haravan. This can be useful in scenarios where you want to synchronize your inventory data between Haravan and other systems, monitor stock levels, or automate inventory management workflows.
Practical examples include:
- Automatically fetching all inventory items to update a local database.
- Triggering alerts or actions when inventory levels change.
- Integrating inventory data into reporting or analytics pipelines.
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. |
Output
The node outputs an array of JSON objects representing the results of the executed operation. For the Inventory Get All operation, the output JSON will contain inventory data retrieved from Haravan. Each item in the output corresponds to an inventory record or a status object indicating the execution details.
The output JSON structure includes:
executionId: The unique identifier of the current execution.resource: The resource name, e.g., "Inventory".operation: The operation performed, e.g., "Get All".status: The status of the operation, typically "completed".timestamp: The ISO string timestamp when the operation was completed.
If binary data were involved (not indicated here), it would be summarized accordingly.
Dependencies
- Requires an API key credential for authenticating with the Haravan platform.
- Depends on the external Haravan API service to fetch inventory data.
- The node uses internal helper libraries bundled under
nqdev-libraries/haravanfor API interactions. - No additional environment variables are explicitly required beyond the API authentication.
Troubleshooting
Common issues:
- Authentication failures due to invalid or missing API credentials.
- Network connectivity problems preventing access to the Haravan API.
- API rate limits or quota exceeded errors.
- Unexpected response formats if the Haravan API changes.
Error messages:
- Errors thrown during execution will include the item index causing the failure.
- If "continue on fail" is enabled, failed items will be included in the output with error details.
- To resolve errors, verify API credentials, check network connectivity, and ensure correct resource and operation parameters.
Links and References
- Haravan Official API Documentation
- n8n documentation on Creating Custom Nodes