Nqdev: Tích hợp HaravanInstall

Overview

This node integrates with the Haravan platform to interact with various resources such as orders, products, and accounts. Specifically, for the Products resource with the Get All Collects operation, it is designed to retrieve all "collects" related to products from Haravan. Collects typically represent associations between products and collections (categories or groups) in an e-commerce context.

Common scenarios where this node is beneficial include:

• Synchronizing product-collection relationships from Haravan into another system.
• Automating workflows that depend on product categorization.
• Generating reports or analytics based on product grouping.

For example, a user might use this node to fetch all collects to update their inventory management system or to trigger marketing campaigns based on product collections.

Properties

The only input property available 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 operation. Each item in the output corresponds to a processed input item and contains metadata about the execution:

• executionId: The unique identifier for the current execution run.
• resource: The resource name (e.g., "Products").
• operation: The operation performed (e.g., "Get All Collects").
• status: The status of the operation, typically "completed".
• timestamp: ISO string timestamp marking when the operation was completed.

The output does not directly contain the fetched collects data but rather a summary object per input item indicating the operation's completion status. This suggests that the actual fetching logic or data retrieval may be handled elsewhere or requires further implementation.

No binary data output is indicated.

Dependencies

• Requires an API key credential for authenticating with the Haravan platform.
• Depends on the external Haravan API accessible via network.
• Uses internal helper methods from the n8n workflow environment for parameter retrieval and output formatting.

Troubleshooting

• Common issues:

  • Missing or invalid API credentials will prevent successful connection to Haravan.
  • Network connectivity problems can cause request failures.
  • Enabling the "Logging Request" option helps diagnose API communication issues by providing detailed request logs.

• Error messages:

  • Errors thrown during execution are wrapped and reported with the item index for easier identification.
  • If "Continue On Fail" is enabled, errors do not stop the entire workflow but are attached to the corresponding output item.

Links and References

• Haravan Official API Documentation
• n8n Documentation
• n8n Node Development Guide

Note: The provided source code's execute() method currently returns only metadata about the operation execution without performing the actual API call to get collects. Additional implementation would be required to fetch and return the collects data from Haravan.