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

Inventory → Get Count

AI-generated

Overview

This node integrates with the Haravan platform to listen for and interact with various resources such as orders, products, and accounts. Specifically, for the Inventory - Get Count operation, it retrieves the count of inventory items from Haravan. This is useful in scenarios where you want to monitor stock levels or synchronize inventory data between Haravan and other systems automatically.

Practical examples include:

  • Automatically fetching the total number of inventory items to trigger workflows based on stock availability.
  • Monitoring inventory changes to update external databases or notify teams when stock counts change.

Properties

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

Output

The node outputs a JSON array where each item contains metadata about the execution related to the requested resource and operation. For the Inventory Get Count operation, the output JSON includes:

  • executionId: The unique identifier of the current workflow execution.
  • resource: The resource name, e.g., "Inventory".
  • operation: The operation performed, e.g., "Get Count".
  • status: The status of the operation, typically "completed".
  • timestamp: The ISO string timestamp when the operation was executed.

No binary data output is produced by this node.

Example output JSON structure:

[
  {
    "executionId": "some-execution-id",
    "resource": "Inventory",
    "operation": "Get Count",
    "status": "completed",
    "timestamp": "2024-06-01T12:00:00.000Z"
  }
]

Dependencies

  • Requires an API key credential to authenticate with the Haravan platform.
  • Depends on the Haravan API being accessible and responsive.
  • No additional environment variables are explicitly required beyond the API authentication setup.

Troubleshooting

  • Common issues:

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

  • Error messages:

    • Errors thrown during execution will indicate the item index causing the failure.
    • If continueOnFail is disabled, the node stops on the first error; enabling it allows processing subsequent items.

  • Resolution tips:

    • Verify that the API key credential is correctly configured and has necessary permissions.
    • Enable the "Logging Request" option to debug API requests and responses.
    • Check network connectivity and firewall settings.
    • Review Haravan API documentation for any recent changes.

Links and References

Discussion