Actions40
- Customer Actions
- Inventory Actions
- Order Actions
- Products Actions
- Shipping and fulfillment Actions
- Location Actions
Products → Get All Products
AI-generatedOverview
This node integrates with the Haravan platform, specifically designed to interact with various resources such as products, orders, and accounts. The "Get All Products" operation fetches a list of all products from the Haravan system. This is useful for workflows that need to synchronize product data, generate reports, or trigger actions based on product information.
Practical examples include:
- Automatically updating an external inventory system with the latest product catalog.
- Triggering notifications or marketing campaigns when new products are added.
- Generating product listings for e-commerce websites or marketplaces.
Properties
| Name | Meaning |
|---|---|
| Options | A collection of optional settings for the request. |
| - Logging Request | Boolean flag 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 "Get All Products" operation, the output JSON contains metadata about the execution such as:
executionId: Unique identifier for the current execution.resource: The resource type, here it would be "Products".operation: The operation performed, here "Get All Products".status: Status of the operation, typically "completed".timestamp: ISO string timestamp of when the operation was completed.
The actual product data fetched from Haravan is not explicitly shown in the provided code snippet, indicating this node may primarily return execution metadata or requires further implementation to return full product details.
No binary data output is indicated by the source code.
Dependencies
- Requires an API key credential to authenticate with the Haravan platform.
- Depends on an external library (
../../nqdev-libraries/haravan) which likely handles API communication. - n8n environment must have this credential configured properly for the node to function.
Troubleshooting
Common issues:
- Failure to authenticate due to missing or invalid API credentials.
- Network errors or timeouts when connecting to Haravan API.
- Unexpected empty or incomplete product data if the API response changes or is limited.
Error messages:
- Errors thrown during execution will include the item index causing the failure.
- If
continueOnFailis disabled, the node stops on first error; enabling it allows processing remaining items. - Debugging can be enhanced by enabling the "Logging Request" option to trace API calls.
Links and References
- Haravan Official API Documentation
- n8n Documentation for general node usage and credential setup