Actions40
- Customer Actions
- Inventory Actions
- Order Actions
- Products Actions
- Shipping and fulfillment Actions
- Location Actions
Products → Get Collect Count
AI-generatedOverview
This node integrates with the Haravan platform to interact with various resources such as orders, products, and accounts. Specifically, for the Products resource and the Get Collect Count operation, it retrieves the count of collections associated with a product. This can be useful in scenarios where you want to analyze how many collections include a particular product, helping with inventory management, marketing segmentation, or reporting.
Practical examples:
- Automatically fetching the number of collections a product belongs to for dynamic categorization.
- Triggering workflows based on collection counts, e.g., promoting products that appear in multiple collections.
- Generating reports on product distribution across collections.
Properties
| Name | Meaning |
|---|---|
| Options | A collection of optional settings: - Logging Request: Enable logging of each API request sent to Haravan for debugging purposes (true/false). |
Output
The node outputs an array of JSON objects, each representing the result of the executed operation per input item. For the Get Collect Count operation, the output JSON contains fields related to the count of collections linked to the specified product.
The exact structure is not explicitly detailed in the source code, but typically it would include at least:
- The count of collections for the product.
- Metadata about the execution such as resource, operation, status, and timestamp.
No binary data output is indicated by the code.
Dependencies
- Requires an API key credential for authenticating with the Haravan platform.
- The node depends on the external Haravan API service.
- Optional logging can be enabled for debugging API requests.
- No additional environment variables are explicitly required beyond the API credentials.
Troubleshooting
Common issues:
- Authentication failures due to invalid or missing API credentials.
- Network errors or timeouts when connecting to the Haravan API.
- Incorrect resource or operation parameters leading to empty or error responses.
Error messages:
- Errors thrown during execution will include context about 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 helps diagnose API request issues by providing detailed logs.
Links and References
- Haravan API Documentation (for details on API endpoints and data structures)
- n8n documentation on creating custom nodes