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

Location → Get All Locations

AI-generated

Overview

This node integrates with the Haravan platform to retrieve data related to various resources such as orders, products, accounts, and specifically locations in this context. The "Get All Locations" operation fetches all location records from a Haravan store. This is useful for workflows that need to process or analyze store locations, manage inventory across multiple sites, or synchronize location data with other systems.

Practical examples include:

  • Automatically updating an external database with all store locations.
  • Triggering workflows based on location-specific events.
  • Generating reports that aggregate sales or stock by location.

Properties

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

Output

The node outputs an array of JSON objects representing the retrieved locations. Each object contains metadata about the execution (such as execution ID, resource type, operation performed, status, and timestamp). The actual location data structure is not explicitly detailed in the code snippet but would typically include fields like location ID, name, address, and other relevant attributes from Haravan's API.

No binary data output is indicated.

Dependencies

  • Requires an API key credential for authenticating requests to the Haravan platform.
  • Depends on the n8n-workflow package for core workflow utilities.
  • Uses an internal Haravan library (../../nqdev-libraries/haravan) which likely handles API communication and model definitions.
  • No additional environment variables are explicitly required beyond the API authentication.

Troubleshooting

  • Common issues:

    • Failure to authenticate due to missing or invalid API credentials.
    • Network errors when connecting to Haravan’s API.
    • Empty or incomplete location data if the store has no locations configured or API permissions are insufficient.

  • Error messages:

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

  • Resolution tips:

    • Verify that the API key credential is correctly configured and has necessary permissions.
    • Enable the "Logging Request" option to debug API calls and inspect request/response details.
    • Check network connectivity and Haravan service status.

Links and References

Discussion