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 "Get Supplies Orders By Supplyid" operation retrieves detailed information about orders associated with a specific supply identified by its unique Supply Id. This is useful for sellers or logistics managers who want to track or audit the orders linked to a particular shipment or supply batch.
Practical examples include:
- Fetching all order details for a given supply to verify shipment contents.
- Integrating supply order data into inventory or accounting systems.
- Monitoring fulfillment status and troubleshooting supply chain issues.
Properties
| Name | Meaning |
|---|---|
| Supply Id | The unique identifier of the supply whose orders you want to retrieve. Example: "WB-GI-1234567". |
Output
The node outputs JSON data containing the list of orders related to the specified supply ID. The structure typically includes order details such as order IDs, product information, quantities, statuses, and other relevant metadata returned by the WB API for that supply.
No binary data output is indicated in the source code.
Dependencies
- Requires an API key credential for authenticating requests to the Wildberries API.
- The node uses a base URL and request defaults configured from a bundled OpenAPI specification file.
- No additional external dependencies are explicitly required beyond standard HTTP request capabilities.
Troubleshooting
- Missing or invalid Supply Id: Ensure the Supply Id is provided and correctly formatted; otherwise, the API call will fail or return no data.
- Authentication errors: Verify that the API key credential is set up properly and has sufficient permissions.
- Network or API errors: Check connectivity and API availability; transient errors may require retries.
- Unexpected response structure: If the API changes, the node’s output format might differ; updating the node or OpenAPI spec may be necessary.
Links and References
- Wildberries API documentation (official site or developer portal)
- n8n documentation on creating custom nodes and using credentials
- General REST API usage guides