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) API specifically for managing FBS (Fulfillment by Seller) supplies. The "Delete Supplies Trbx By Supplyid" operation allows users to delete a specific supply record identified by its unique Supply Id. This is useful in scenarios where a supply entry was created erroneously or needs to be removed from the system for data correction or cleanup purposes.
Practical examples include:
- Removing a mistakenly created supply shipment.
- Cleaning up outdated or canceled supply records.
- Automating supply management workflows that require deletion of certain supplies based on business logic.
Properties
| Name | Meaning |
|---|---|
| Supply Id | The unique identifier of the supply to delete. Example format: "WB-GI-1234567". |
Output
The node outputs JSON data representing the result of the delete operation. Typically, this will confirm whether the deletion was successful or provide details about any errors encountered. The exact structure depends on the WB API response but generally includes status and message fields.
No binary data output is expected from this operation.
Dependencies
- Requires an API key credential for authenticating with the Wildberries API.
- The node uses a base URL configured from a Swagger/OpenAPI specification related to WB orders FBS.
- Proper network access to the WB API endpoints is necessary.
Troubleshooting
Common issues:
- Invalid or missing Supply Id: Ensure the Supply Id provided matches the expected format and exists in the system.
- Authentication failures: Verify that the API key credential is correctly set up and has sufficient permissions.
- Network or API endpoint errors: Check connectivity and that the WB API service is operational.
Error messages:
- "Supply not found": The specified Supply Id does not exist; verify the ID.
- "Unauthorized": Authentication failed; check API credentials.
- "Bad Request": Input parameters may be malformed; ensure correct Supply Id format.
Resolving these typically involves verifying input values, credentials, and network conditions.
Links and References
- Wildberries API documentation (general): https://openapi.wildberries.ru/
- n8n documentation on creating custom nodes: https://docs.n8n.io/integrations/creating-nodes/