Actions40
- Customer Actions
- Inventory Actions
- Order Actions
- Products Actions
- Shipping and fulfillment Actions
- Location Actions
Products → Get Collect
AI-generatedOverview
This node integrates with the Haravan platform, specifically designed to interact with various resources such as orders, products, and accounts. In the context of the Products resource and the Get Collect operation, it is intended to retrieve collection data related to products from Haravan.
Typical use cases include:
- Fetching product collections for inventory management.
- Synchronizing product grouping information between Haravan and other systems.
- Automating workflows that depend on product categorization or collection data.
For example, a user might use this node to automatically pull updated product collections daily to update their e-commerce storefront or analytics dashboards.
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. |
The "Options" property allows users to toggle detailed logging of requests, which can help during development or troubleshooting.
Output
The node outputs an array of JSON objects representing the results of the requested operation. Each item in the output corresponds to a processed input item and contains metadata about the execution:
executionId: Unique identifier for the current execution.resource: The resource type being operated on (e.g., "Products").operation: The operation performed (e.g., "Get Collect").status: Status of the operation, typically"completed".timestamp: ISO string timestamp when the operation was executed.
The output does not explicitly show the actual product collection data in the provided code snippet, but it is implied that the node would return relevant collection information from Haravan's API in the json field.
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 external Haravan library (
../../nqdev-libraries/haravan) for API interaction. - Needs proper configuration of credentials within n8n to connect to Haravan.
Troubleshooting
Common issues:
- Failure to authenticate due to missing or invalid API credentials.
- Network errors or timeouts when connecting to Haravan's 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 will stop on the first error; enabling it allows processing subsequent items.
Resolution tips:
- Verify API credentials are correctly set up in n8n.
- Enable "Logging Request" option to get detailed logs for debugging.
- Check network connectivity and API endpoint availability.
- Confirm that the resource and operation names match those supported by the node.
Links and References
- Haravan Official Website
- n8n Documentation
- For more details on Haravan API endpoints, consult Haravan's developer documentation (not included in the source).