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 → Search

AI-generated

Overview

This node integrates with the Haravan platform, enabling users to interact with various Haravan resources such as orders, products, and customers. Specifically, for the Customer - Search operation, it allows searching customer data within Haravan. This can be useful in workflows that require retrieving customer information based on certain criteria, automating customer management tasks, or syncing customer data with other systems.

Practical examples include:

  • Automatically fetching customer details when a new order is placed.
  • Searching for customers to update their profiles or segment them for marketing campaigns.
  • Integrating customer search results into CRM or support ticketing workflows.

Properties

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

The "Options" property currently supports one setting:

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

Output

The node outputs an array of JSON objects representing the results of the executed operation. For the Customer Search operation, the output JSON will contain the search results or status information related to the search.

The structure includes fields such as:

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

If multiple results are returned, they are aggregated into the output array.

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 external Haravan API service.
  • No additional environment variables or configurations are explicitly required beyond the API authentication.

Troubleshooting

  • Common Issues:

    • API authentication failures due to invalid or missing credentials.
    • Network connectivity issues preventing access to Haravan API.
    • Rate limiting or quota exceeded errors from Haravan API.

  • Error Handling:

    • The node attempts to continue processing items if the "Continue On Fail" option is enabled; otherwise, it throws an error with context about the failed item.
    • Errors during execution are wrapped and reported with item index information to help identify problematic inputs.

  • Debugging Tips:

    • Enable the "Logging Request" option to get detailed logs of API requests and responses.
    • Check the workflow's execution logs for error messages and stack traces.
    • Verify API credentials and network connectivity.

Links and References

Discussion