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 Order

AI-generated

Overview

This node integrates with the Haravan platform, specifically designed to interact with various Haravan resources such as orders, products, and accounts. For the "Order" resource with the "Get Order" operation, it retrieves order data from Haravan. This is useful for workflows that need to fetch order details automatically, for example, syncing order information into a CRM, triggering fulfillment processes, or generating reports based on order data.

Properties

Name Meaning
Options A collection of optional settings:
- Logging Request Boolean option to enable logging of each API request sent to Haravan, useful for debugging.

Output

The node outputs an array of JSON objects representing the results of the executed operations. Each output item contains at least the following fields:

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

The output JSON structure reflects the metadata about the operation rather than the actual order data fetched from Haravan. The provided source code snippet does not show direct fetching or returning of order details, indicating that either this logic is abstracted elsewhere or the node currently returns operation metadata only.

No binary data output is indicated in the code.

Dependencies

  • Requires an API key credential to authenticate with the Haravan platform.
  • Depends on an external Haravan library (../../nqdev-libraries/haravan) which likely handles API communication.
  • n8n environment must have this credential configured properly for the node to function.

Troubleshooting

  • Common Issues:

    • Missing or invalid API credentials will prevent successful connection to Haravan.
    • If the "Logging Request" option is enabled but no logs appear, ensure that the node's logger is properly configured.
    • The node’s current implementation appears to return only operation metadata; if actual order data is expected, verify that the node version supports this or check for additional configuration.

  • Error Messages:

    • Errors thrown during execution include context about the item index causing failure.
    • If continueOnFail is disabled, the node stops on first error; enabling it allows processing remaining items despite errors.
    • Common errors may relate to network issues, authentication failures, or invalid parameters.

Links and References

Discussion