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 → Create Order

AI-generated

Overview

This node integrates with the Haravan platform, primarily to handle various resources such as orders, products, and accounts. Specifically, for the Create Order operation under the Order resource, it facilitates creating new orders in Haravan by processing input data and sending it to the Haravan API.

Common scenarios where this node is beneficial include:

  • Automating order creation from external systems or form submissions.
  • Syncing orders from other e-commerce platforms into Haravan.
  • Triggering workflows based on new order creation events.

For example, a user might use this node to automatically create an order in Haravan whenever a customer completes a purchase on their website, ensuring inventory and sales data stay synchronized.

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 node also expects standard parameters for selecting the Resource (e.g., "Order") and Operation (e.g., "Create Order"), though these are not explicitly listed in the provided properties JSON but are referenced in the code.

Output

The node outputs an array of JSON objects representing the result of the executed operation(s). Each output item contains at least the following fields:

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

If multiple items are processed, the output will be an array of such objects, one per input item.

No binary data output is indicated in the source code.

Dependencies

  • Requires an API key credential to authenticate with the Haravan platform.
  • Depends on the external Haravan API service.
  • Uses internal helper libraries (nqdev-libraries/haravan) for model definitions and possibly API interactions.
  • Requires proper configuration of credentials within n8n to connect securely to Haravan.

Troubleshooting

  • Common issues:

    • Failure to authenticate due to missing or invalid API credentials.
    • Network errors or timeouts when connecting to the Haravan API.
    • Incorrect or incomplete input data causing the API to reject the order creation request.

  • Error messages:

    • Errors thrown during execution will include the item index to help identify which input caused the failure.
    • If continueOnFail is enabled, failed items will be returned with error details instead of stopping the workflow.
    • Typical errors may relate to invalid parameters or API response errors; users should verify input data and API access rights.

Links and References

Discussion