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

Shipping and fulfillment → Get Fulfillment

AI-generated

Overview

This node integrates with the Haravan platform to interact with various resources such as orders, products, accounts, and specifically for this context, shipping and fulfillment. The "Get Fulfillment" operation retrieves fulfillment details from Haravan, which is useful for tracking shipment status, managing order deliveries, or synchronizing fulfillment data within automated workflows.

Practical examples include:

  • Automatically fetching fulfillment information when an order status changes.
  • Integrating fulfillment data into a CRM or ERP system.
  • Triggering notifications or follow-up actions based on shipment updates.

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.

Output

The node outputs an array of JSON objects representing the result of the requested operation. For the "Get Fulfillment" operation, the output JSON contains:

  • executionId: The unique identifier of the current execution.
  • resource: The resource type, here it would be "Shipping and fulfillment".
  • operation: The operation performed, e.g., "Get Fulfillment".
  • status: The status of the operation, typically "completed".
  • timestamp: The ISO string timestamp when the operation was executed.

Note: The actual fulfillment data retrieved from Haravan is not explicitly shown in the provided code snippet, indicating that the current implementation returns metadata about the operation rather than detailed fulfillment records. This might be a placeholder or simplified example.

If binary data were returned (e.g., documents or labels), it would be included in the output's binary property, but no such handling is present in the given code.

Dependencies

  • Requires an API key credential for authenticating with the Haravan platform.
  • Depends on the external Haravan library (../../nqdev-libraries/haravan) for node model definitions and possibly API interactions.
  • n8n environment must have this credential configured properly to allow API communication.

Troubleshooting

  • Common issues:

    • Missing or invalid API credentials will prevent successful API calls.
    • Network connectivity problems can cause request failures.
    • If the "Logging Request" option is enabled, excessive logs may slow down execution or clutter logs.

  • Error messages:

    • Errors thrown during execution are wrapped as NodeOperationErrors with item index information.
    • If continueOnFail is enabled, errors for individual items do not stop the workflow but are appended to the output with error details.

  • Resolution tips:

    • Verify API credentials and permissions.
    • Check network access to Haravan API endpoints.
    • Use the logging option selectively to debug specific issues.

Links and References

Discussion