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 All Orders

AI-generated

Overview

This node integrates with the Haravan platform to interact with various resources such as orders, products, and accounts. Specifically, for the "Order" resource with the "Get All Orders" operation, it retrieves a list of all orders from the Haravan system. This is useful for workflows that need to process or analyze order data, synchronize orders with other systems, or trigger actions based on new or updated orders.

Practical examples include:

  • Automatically fetching all recent orders to update an external CRM or ERP system.
  • Monitoring order data to trigger notifications or fulfillment processes.
  • Aggregating order statistics for reporting purposes.

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.

The "Options" property currently supports only one option:

  • Logging Request: When enabled, the node logs detailed information about every API request it sends, which helps in troubleshooting and debugging.

Output

The node outputs an array of JSON objects representing the results of the executed operation. For the "Get All Orders" operation, each item in the output array corresponds to an order or a status object related to the execution.

The structure of each output JSON includes:

  • executionId: The unique identifier of the current workflow execution.
  • resource: The resource type, e.g., "Order".
  • operation: The operation performed, e.g., "Get All Orders".
  • status: The status of the operation, typically "completed".
  • timestamp: The ISO string timestamp when the operation was completed.

If the operation returns multiple items (e.g., multiple orders), they are pushed into the output array accordingly.

No binary data output is indicated by the source code.

Dependencies

  • Requires an API key credential for authenticating with the Haravan platform.
  • The node depends on the Haravan API being accessible and properly configured.
  • No additional environment variables or external services are explicitly required beyond the API authentication.

Troubleshooting

  • Common Issues:

    • Failure to authenticate due to invalid or missing API credentials.
    • Network connectivity issues preventing access to the Haravan API.
    • API rate limits or quota exceeded errors from Haravan.

  • Error Messages:

    • Errors thrown during execution will be wrapped as node operation errors with context about the item index.
    • If "continue on fail" is enabled, errors for individual items will be included in the output with error details.

  • Resolution Tips:

    • Verify that the API key credential is correctly set up and has necessary permissions.
    • Enable "Logging Request" to get detailed logs of API calls for debugging.
    • Check network connectivity and firewall settings.
    • Review Haravan API usage limits and ensure the workflow respects them.

Links and References

Discussion