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 retrieve detailed information about a specific supply using its unique Supply Id. It is useful for sellers or logistics managers who want to track or verify the status and details of their shipments handled through WB's fulfillment system.
A practical example would be querying the node with a known Supply Id like "WB-GI-1234567" to fetch all relevant data about that particular supply, such as shipment contents, status, dates, and other metadata.
Properties
| Name | Meaning |
|---|---|
| Supply Id | The unique identifier of the supply to retrieve. Example: "WB-GI-1234567". This property is required. |
Output
The node outputs JSON data containing detailed information about the specified supply. The structure typically includes fields describing the supply's attributes such as identifiers, status, contents, timestamps, and related metadata as provided by the WB FBS API.
No binary data output is indicated in the source code.
Dependencies
- Requires an API key credential to authenticate requests against the Wildberries API.
- The node uses a base URL configured from an imported OpenAPI specification JSON file.
- The node depends on the
@devlikeapro/n8n-openapi-nodepackage for building request properties and handling API interactions. - Proper configuration of credentials and network access to the WB API endpoint is necessary.
Troubleshooting
- Common issues:
- Invalid or missing Supply Id will cause the API call to fail or return no data.
- Authentication errors if the API key credential is not set or invalid.
- Network connectivity problems may prevent reaching the WB API.
- Error messages:
- Errors related to supply not found usually indicate an incorrect Supply Id.
- Authorization errors suggest checking the API key credential setup.
- Timeout or connection errors require verifying network settings and API availability.
Links and References
- Wildberries API documentation (official site or developer portal)
- n8n documentation on creating custom nodes and using API credentials
@devlikeapro/n8n-openapi-nodepackage repository or documentation for advanced usage