Nqdev: Tích hợp Haravan icon

Nqdev: Tích hợp Haravan

Tích hợp Haravan với n8n để lắng nghe các sự kiện như đơn hàng, sản phẩm, tài khoản... và tự động kích hoạt các workflow tương ứng.

Actions40

Order → Get Checkout Count

AI-generated

Overview

This node integrates with the Haravan platform to perform various operations related to e-commerce data such as orders, products, and accounts. Specifically, for the "Order" resource and the "Get Checkout Count" operation, it retrieves the count of checkouts/orders from Haravan. This can be useful for monitoring sales performance, tracking order volume over time, or triggering workflows based on order activity.

Practical examples include:

  • Automatically updating a dashboard with the latest checkout counts.
  • Triggering marketing campaigns when checkout counts reach certain thresholds.
  • Auditing order volumes for business analytics.

Properties

Name Meaning
Options A collection of optional settings:
- 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 where each object contains metadata about the executed operation, including:

  • executionId: Unique identifier for the current execution.
  • resource: The resource type, e.g., "Order".
  • operation: The operation performed, e.g., "Get Checkout Count".
  • status: Status of the operation, typically "completed".
  • timestamp: ISO string timestamp of when the operation was executed.

The output does not contain the actual checkout count data directly but rather a status object indicating the operation was completed. The node’s current implementation appears to focus on returning operation metadata rather than detailed API response data.

No binary data output is produced by this node.

Dependencies

  • Requires an API key credential for authenticating with the Haravan platform.
  • Depends on the external Haravan API service to fetch order-related data.
  • Uses internal helper libraries bundled with the node for API communication and workflow integration.

Troubleshooting

  • Common issues:

    • API authentication failures due to invalid or missing credentials.
    • Network connectivity problems preventing access to Haravan API.
    • Unexpected empty or incomplete responses if the API changes or if there are no orders.

  • Error messages:

    • Errors thrown during execution will include the item index causing the failure.
    • If "continue on fail" is disabled, the node stops on first error; enabling it allows processing subsequent items.

  • Resolution tips:

    • Verify that the API key credential is correctly configured and has necessary permissions.
    • Enable the "Logging Request" option to debug API requests and responses.
    • Check network connectivity and Haravan API status.
    • Review input parameters to ensure correct resource and operation names.

Links and References

Discussion