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 "Order" resource and the "Get Order Count" operation, it retrieves the total number of orders from the Haravan system. This is useful in scenarios where you want to monitor order volume, generate reports, or trigger workflows based on order counts.

Practical examples include:

• Automatically fetching the current count of orders to update dashboards.
• Triggering alerts or follow-up actions when order counts reach certain thresholds.
• Integrating order count data into broader business analytics workflows.

Properties

Output

The node outputs a JSON array where each item contains information about the executed operation. For the "Get Order Count" operation, the output JSON includes fields such as:

• executionId: The unique identifier for this execution instance.
• resource: The resource type, e.g., "Order".
• operation: The operation performed, e.g., "Get Order Count".
• status: The status of the operation, typically "completed".
• timestamp: The ISO string timestamp when the operation was completed.

Note: The provided source code snippet does not explicitly show the actual retrieval of the order count value from the Haravan API or its inclusion in the output JSON. Instead, it returns metadata about the operation execution. In a fully implemented version, the output would also include the actual order count data retrieved from the API.

The node does not appear to output binary data.

Dependencies

• Requires an API key credential to authenticate with the Haravan platform.
• Depends on the external Haravan API service to fetch order data.
• Uses internal helper methods from the n8n workflow environment for input/output handling and error management.

Troubleshooting

• Common Issues:

  • Missing or invalid API credentials will prevent successful communication with Haravan.
  • Network connectivity issues can cause request failures.
  • Enabling the "Logging Request" option can help debug API request/response problems by providing detailed logs.

• Error Messages:

  • Errors thrown during execution are wrapped and reported with context about the item index.
  • If "Continue On Fail" is enabled, errors do not stop the workflow but are included in the output for inspection.
  • Typical errors may relate to authentication failures, rate limiting, or malformed requests.

Links and References

• Haravan Official API Documentation
• n8n Documentation