Actions40
- Customer Actions
- Inventory Actions
- Order Actions
- Products Actions
- Shipping and fulfillment Actions
- Location Actions
Inventory → Get
AI-generatedOverview
This node integrates with the Haravan platform to interact with various resources such as orders, products, accounts, and inventory. Specifically, for the Inventory - Get operation, it retrieves inventory-related data from Haravan. This can be useful in scenarios where you want to synchronize stock levels, monitor inventory changes, or trigger workflows based on inventory status.
Practical examples include:
- Automatically updating your internal database with current inventory counts.
- Triggering reorder workflows when stock falls below a threshold.
- Generating reports on inventory availability.
Properties
| Name | Meaning |
|---|---|
| Options | A collection of optional settings: |
| - Logging Request | Boolean flag to enable logging of each API request sent to Haravan for debugging purposes. |
The only input property under "Options" is Logging Request, which when enabled, logs every API request made by the node to assist with troubleshooting and debugging.
Output
The node outputs an array of JSON objects representing the results of the executed operations. For the Inventory Get operation, the output JSON contains:
executionId: The unique identifier of the workflow execution.resource: The resource name, e.g., "Inventory".operation: The operation performed, e.g., "Get".status: The status of the operation, typically"completed".timestamp: ISO string timestamp of when the operation was completed.
The output structure is generic and does not directly include detailed inventory data in this snippet, but the node is designed to return relevant inventory information fetched from Haravan's API.
No binary data output is indicated in the code.
Dependencies
- Requires an API key credential for authenticating with the Haravan platform.
- Depends on the external Haravan API service.
- Uses n8n's built-in helpers and error handling mechanisms.
- No additional environment variables are explicitly required beyond the API credential.
Troubleshooting
Common issues:
- Authentication failures due to invalid or missing API credentials.
- Network errors or timeouts when connecting to Haravan API.
- Unexpected empty or malformed responses if the API changes or if the requested resource/operation is incorrect.
Error messages:
- Errors thrown during execution will include the item index causing the failure.
- If "Continue On Fail" is disabled, the node stops on the first error; enabling it allows processing subsequent items.
- Enabling the "Logging Request" option can help diagnose issues by providing detailed request logs.