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 integrates with the Wildberries (WB) API to create new FBS (Fulfillment by Seller) supplies. It allows users to post supply data directly to the WB system, automating inventory or shipment updates related to seller-managed fulfillment. This is useful for sellers who want to programmatically manage their supply chain and stock levels on the Wildberries platform.
A practical example would be a seller automatically creating a new supply record named "Тестовая поставка" (Test Supply) whenever new stock is prepared for shipment to the warehouse, streamlining the logistics process.
Properties
| Name | Meaning |
|---|---|
| Name | The name of the supply being posted. This is a string value representing the supply's designation or title. |
Output
The node outputs JSON data representing the response from the Wildberries API after posting the supply. This typically includes confirmation details about the created supply, such as its ID, status, or any messages returned by the API.
No binary data output is indicated in the source code.
Dependencies
- Requires an API key credential for authenticating with the Wildberries API.
- Depends on the Wildberries API endpoint defined in the bundled Swagger/OpenAPI specification (
03-orders-fbs_modified.json). - Uses the
@devlikeapro/n8n-openapi-nodepackage to build properties and handle requests. - The base URL for API requests is derived from the OpenAPI spec.
Troubleshooting
Common issues:
- Authentication failures if the API key is missing or invalid.
- Incorrect supply names or malformed request bodies causing API errors.
- Network connectivity problems preventing communication with the Wildberries API.
Error messages:
- Errors returned by the Wildberries API will be passed through; typical messages might include validation errors for supply data or authorization errors.
- To resolve, verify that the API key is correctly configured and that the supply name meets the API requirements.
Links and References
- Wildberries API documentation (refer to the official Wildberries developer portal for detailed API specs).
- n8n OpenAPI Node integration documentation: https://docs.n8n.io/integrations/builtin/app-nodes/n8n-openapi-node/