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 Transaction

AI-generated

Overview

This node integrates with the Haravan platform, enabling users to interact with various Haravan resources such as orders, products, and accounts. Specifically, for the Order resource and the Get Transaction operation, it retrieves transaction details related to an order from Haravan. This is useful in workflows where you need to fetch payment or transaction information associated with customer orders for processing, reporting, or triggering further automation.

Practical examples include:

  • Automatically retrieving transaction details after an order is placed to update accounting systems.
  • Fetching payment status to decide whether to proceed with order fulfillment.
  • Logging transaction data for auditing or customer service purposes.

Properties

Name Meaning
Options A collection of optional fields to customize the request behavior.
- Logging Request Boolean flag to enable logging of each API request sent to Haravan for debugging purposes.

The "Options" property currently supports one option:

  • Logging Request: When enabled (true), the node logs detailed information about each API request made, which helps in troubleshooting and debugging.

Output

The node outputs a JSON array where each item corresponds to the result of the executed operation per input item. For the "Get Transaction" operation on the Order resource, the output JSON contains the transaction details retrieved from Haravan.

The structure of the output JSON includes at least the following fields (based on static analysis):

  • executionId: The unique identifier of the current execution.
  • resource: The resource name, e.g., "Order".
  • operation: The operation performed, e.g., "Get Transaction".
  • status: The status of the operation, typically "completed" if successful.
  • timestamp: The ISO timestamp when the operation was completed.

If the node encounters multiple results, it returns them as an array. If errors occur and "Continue On Fail" is enabled, error details are included alongside the original input data.

No binary data output is indicated by the source code.

Dependencies

  • Requires an API key credential for authenticating with the Haravan platform.
  • Depends on the external Haravan API accessible via network.
  • The node uses internal helper libraries bundled under ../../nqdev-libraries/haravan for API communication.
  • No additional environment variables or n8n configurations are explicitly required beyond the API credential.

Troubleshooting

  • Common issues:

    • Authentication failures due to invalid or missing API credentials.
    • Network connectivity problems preventing access to Haravan API.
    • API rate limits or quota exceeded errors.
    • Incorrect resource or operation parameters leading to empty or error responses.

  • Error messages:

    • Errors thrown during execution will be wrapped as node operation errors with context about the item index.
    • If "Continue On Fail" is disabled, the node stops execution on the first error.
    • Enabling "Logging Request" can help identify request payloads and responses to debug issues.

  • Resolution tips:

    • Verify that the API key credential is correctly configured and has necessary permissions.
    • Check network connectivity and firewall settings.
    • Use the logging option to inspect requests and responses.
    • Ensure correct resource and operation names are selected.

Links and References

Discussion