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 Refunds

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 and the Get Refunds operation, it retrieves refund information related to orders from Haravan. This is useful in e-commerce workflows where you want to automate monitoring or processing of refunds, such as updating internal systems, triggering notifications, or generating reports.

Practical examples include:

  • Automatically fetching refund details after an order is refunded.
  • Syncing refund data with accounting or CRM systems.
  • Triggering follow-up actions based on refund status changes.

Properties

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

The only input property relevant here is the Options collection, which currently supports a single boolean flag to toggle detailed request logging.

Output

The node outputs an array of JSON objects representing the results of the executed operation. For the "Get Refunds" operation under the "Order" resource, the output JSON will contain refund-related data retrieved from Haravan.

The exact structure of the refund data is not explicitly defined in the provided code but typically includes refund identifiers, amounts, statuses, dates, and associated order information.

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 nqdev-libraries/haravan library for interfacing with Haravan's API.
  • The node expects proper configuration of credentials within n8n to access Haravan services.

Troubleshooting

  • Common Issues:

    • Authentication failures due to missing or invalid API credentials.
    • Network connectivity problems preventing access to Haravan's API.
    • Unexpected API response formats if Haravan updates their API.

  • Error Messages:

    • Errors thrown during execution are wrapped as node operation errors with item index context.
    • If "continue on fail" is enabled, failed items are returned with error details instead of stopping the workflow.

  • Resolution Tips:

    • Verify that the API key credential is correctly set up and has necessary permissions.
    • Enable the "Logging Request" option to get detailed logs for troubleshooting API calls.
    • Check network settings and firewall rules to ensure connectivity to Haravan endpoints.

Links and References

Discussion