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

Products → Delete Collect

AI-generated

Overview

This node integrates with the Haravan platform, specifically handling various resources and operations related to e-commerce data such as orders, products, and accounts. For the Products resource with the Delete Collect operation, it is designed to delete a product collection or association within Haravan.

Common scenarios for this node include automating product management workflows, such as removing outdated or discontinued product collections from your Haravan store automatically. This can help keep your product catalog clean and up-to-date without manual intervention.

Practical example: Automatically deleting a product collection when it no longer meets certain business criteria, triggered by an external event or schedule.

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.

Output

The node outputs JSON data representing the status of the executed operation for each input item. The output JSON includes:

  • executionId: Unique identifier for the execution instance.
  • resource: The resource type involved (e.g., "Products").
  • operation: The operation performed (e.g., "Delete Collect").
  • status: Status of the operation, typically "completed".
  • timestamp: ISO string timestamp marking when the operation was completed.

If multiple results are returned, they are aggregated into an array. The node does not output binary data.

Dependencies

  • Requires an API key credential for authenticating with the Haravan platform.
  • Needs network access to Haravan's API endpoints.
  • Optional logging depends on internal logger configuration.

Troubleshooting

  • Common issues:

    • Authentication failures due to invalid or missing API credentials.
    • Network connectivity problems preventing API calls.
    • Incorrect resource or operation parameters causing unexpected behavior.

  • Error messages:

    • Errors thrown during execution will include the item index for easier debugging.
    • If continueOnFail is enabled, errors for individual items will be included in the output rather than stopping the entire workflow.

  • Resolution tips:

    • Verify that the API key credential is correctly configured and has necessary permissions.
    • Ensure the resource and operation names match supported values.
    • Enable logging (Logging Request option) to get detailed request information for debugging.

Links and References

Discussion