Actions34
- Сборочные Задания Actions
- Метаданные Actions
- Поставки FBS Actions
- Post Supplies
- Get Supplies
- Patch Supplies Orders By Supplyid By Orderid
- Get Supplies By Supplyid
- Delete Supplies By Supplyid
- Get Supplies Orders By Supplyid
- Patch Supplies Deliver By Supplyid
- Get Supplies Barcode By Supplyid
- Get Supplies Trbx By Supplyid
- Post Supplies Trbx By Supplyid
- Delete Supplies Trbx By Supplyid
- Patch Supplies Trbx By Supplyid By Trbxid
- Delete Supplies Trbx Orders By Supplyid By Trbxid By Orderid
- Post Supplies Trbx Stickers By Supplyid
- Пропуска Actions
- Доставка Курьером WB DBW Actions
Overview
This node interacts with the Wildberries (WB) FBS (Fulfillment by Seller) API to delete a specific order associated with a supply and a transport box (Trbx). The operation "Delete Supplies Trbx Orders By Supplyid By Trbxid By Orderid" targets the removal of an assembly order identified by its order ID within a particular transport box and supply.
Typical use cases include:
- Automating cleanup or correction of orders mistakenly assigned to a transport box.
- Managing supply chain workflows by programmatically removing obsolete or incorrect assembly tasks.
- Integrating with inventory or logistics systems to maintain accurate order statuses in WB's fulfillment system.
Example: Deleting an order with ID 5632423 from transport box "WB-TRBX-1234567" under supply "WB-GI-1234567".
Properties
| Name | Meaning |
|---|---|
| Supply Id | The unique identifier of the supply (поставка) where the order is located. |
| Trbx Id | The unique identifier of the transport box (короб) containing the order. |
| Order Id | The numeric ID of the assembly order (сборочное задание) to be deleted from the supply. |
Output
The node outputs JSON data representing the response from the WB API after attempting to delete the specified order. This typically includes confirmation of deletion or error details if the operation failed.
No binary data output is indicated.
Dependencies
- Requires access to the Wildberries API, which likely needs an API key or authentication token configured in n8n credentials.
- The node uses a base URL and request defaults derived from a Swagger/OpenAPI specification for the WB FBS orders API.
- Proper network connectivity to the WB API endpoint is necessary.
Troubleshooting
Common issues:
- Invalid or missing Supply Id, Trbx Id, or Order Id leading to API errors.
- Authentication failures due to missing or incorrect API credentials.
- Network connectivity problems preventing communication with the WB API.
- Attempting to delete an order that does not exist or has already been deleted.
Error messages:
- Authorization errors: Check API credentials and permissions.
- Not found errors: Verify that the provided IDs are correct and exist in the WB system.
- Validation errors: Ensure all required parameters are provided and correctly formatted.
Resolving these usually involves verifying input parameters, ensuring valid credentials, and confirming the existence of the targeted order.
Links and References
- Wildberries API documentation (if publicly available)
- n8n documentation on creating custom nodes and using HTTP request nodes
- OpenAPI/Swagger specifications for WB FBS orders API (referenced internally in the node)