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

Customer → Get

AI-generated

Overview

This node integrates with the Haravan platform, allowing users to interact with various Haravan resources such as customers, orders, products, and accounts. Specifically, for the Customer - Get operation, it retrieves customer data from Haravan. This is useful in scenarios where workflows need to fetch customer details for processing, reporting, or triggering further automation based on customer information.

Practical examples include:

  • Automatically retrieving customer profiles when a new order is placed.
  • Syncing customer data between Haravan and other systems.
  • Triggering personalized marketing campaigns based on customer attributes.

Properties

Name Meaning
Options Collection of additional options for the request.
- Logging Request Boolean option to enable logging of each API request sent to Haravan for debugging purposes.

The only input property under "Options" is:

  • Logging Request: When enabled (true), the node logs every API request made to Haravan, which helps in troubleshooting and debugging API interactions.

Output

The node outputs an array of JSON objects representing the results of the executed operations. For the Customer Get operation, the output JSON will contain the retrieved customer data structured according to Haravan's API response format.

The output structure includes at least these fields (based on static analysis):

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

If the operation returns multiple items, 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.
  • Depends on the external Haravan API service.
  • Uses internal helper libraries bundled with the node for interacting with Haravan.
  • No environment variables are explicitly required beyond the API authentication credential.

Troubleshooting

  • Common issues:

    • API authentication failures due to invalid or missing credentials.
    • Network connectivity problems preventing access to Haravan API.
    • Rate limiting or quota exceeded errors from Haravan API.
    • Unexpected empty or malformed responses if the requested customer does not exist.

  • Error messages:

    • Errors thrown during execution are wrapped and reported 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 configured and has sufficient permissions.
    • Enable "Logging Request" option to capture detailed request/response logs for debugging.
    • Check network connectivity and firewall settings.
    • Handle cases where customer data might be missing or incomplete gracefully in your workflow.

Links and References

Discussion