Sapo Thực Hiện Đơn Hàng icon

Sapo Thực Hiện Đơn Hàng

Quản lý thực hiện đơn hàng trên Sapo

Overview

This node manages order fulfillments on the Sapo platform, focusing on operations related to fulfillment events. Specifically, the "Xóa Sự Kiện" (Delete Event) operation allows users to delete a specific fulfillment event associated with an order fulfillment. This is useful for maintaining accurate fulfillment histories by removing incorrect or obsolete events.

Common scenarios include:

  • Correcting fulfillment event records by deleting mistakenly created events.
  • Cleaning up outdated or irrelevant fulfillment events from an order's fulfillment history.

Example: If a fulfillment event was logged incorrectly (e.g., wrong status or message), this node can delete that event to ensure the fulfillment timeline reflects accurate information.

Properties

Name Meaning
ID Thực Hiện The numeric ID of the fulfillment instance to which the event belongs.
ID Sự Kiện The numeric ID of the specific fulfillment event to delete.

Output

The output JSON contains a simple confirmation object indicating success:

{
  "success": true
}

This confirms that the specified fulfillment event was successfully deleted.

Dependencies

  • Requires an API key credential for authenticating with the Sapo API.
  • Depends on the Sapo API base class to perform HTTP requests to the Sapo platform.
  • The node expects valid order and fulfillment IDs to identify the correct fulfillment event.

Troubleshooting

  • Error: Invalid or missing fulfillment/event ID
    Ensure that both the fulfillment ID and event ID are correctly provided and correspond to existing records in Sapo.

  • API authentication errors
    Verify that the API key credential is correctly configured and has sufficient permissions to delete fulfillment events.

  • Event not found or already deleted
    If the event ID does not exist or was previously deleted, the API may return an error. Confirm the event ID before attempting deletion.

  • Network or API downtime issues
    Temporary connectivity problems or Sapo API outages can cause failures. Retry after some time or check Sapo service status.

Links and References

Discussion