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 post additional supply boxes to an existing supply identified by its Supply Id. It is useful in scenarios where you need to update a supply shipment by increasing the number of boxes associated with it, for example, when more inventory is added after the initial supply creation.
Practical examples:
- A seller wants to notify WB that 4 more boxes are being added to an already created supply shipment.
- Automating supply updates in bulk when new stock arrives and needs to be appended to existing shipments.
Properties
| Name | Meaning |
|---|---|
| Supply Id | The unique identifier of the supply shipment to which boxes will be added (e.g., "WB-GI-1234567"). |
| Amount | The number of boxes to add to the specified supply. |
Output
The node outputs JSON data representing the response from the WB API after posting the additional boxes to the supply. This typically includes confirmation details about the updated supply or any error messages returned by the API.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating requests to the Wildberries API.
- The node uses a base URL derived from a bundled OpenAPI specification related to WB orders FBS.
- Proper configuration of the API authentication within n8n is necessary for successful operation.
Troubleshooting
Common issues:
- Invalid or missing Supply Id can cause the API to reject the request.
- Insufficient permissions or invalid API credentials may result in authentication errors.
- Network connectivity problems can prevent communication with the WB API.
Error messages:
- Errors indicating supply not found usually mean the Supply Id does not exist or is mistyped.
- Authorization errors suggest checking the API key or token validity.
- Validation errors on the amount field occur if the number is zero, negative, or non-integer.
To resolve these, verify the Supply Id correctness, ensure valid API credentials are configured, and confirm the amount is a positive integer.
Links and References
- Wildberries API documentation (general reference for FBS supplies)
- n8n documentation on creating and configuring HTTP request nodes and API credentials