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
The node interacts with the Wildberries (WB) API to retrieve supply data related to FBS (Fulfillment by Seller) shipments. Specifically, the "Get Supplies" operation fetches paginated lists of supply records from the WB system. This is useful for sellers or logistics managers who want to programmatically monitor and manage their FBS supplies, track shipment statuses, or integrate supply data into their own systems.
Practical examples include:
- Automatically syncing supply shipment data into an inventory management system.
- Generating reports on recent FBS deliveries.
- Triggering workflows based on new supply arrivals.
Properties
| Name | Meaning |
|---|---|
| Limit | Pagination parameter that sets the maximum number of supply records to return in one request. |
| Next | Pagination parameter indicating the starting point for the next batch of data. For the first request, it should be 0; subsequent requests use the value from the response's next field. |
Output
The node outputs JSON data containing a list of supply records retrieved from the WB API. The structure includes pagination metadata such as the next value to facilitate fetching subsequent pages. Each supply record typically contains details about individual FBS shipments.
No binary data output is indicated.
Dependencies
- Requires access to the Wildberries API endpoint for FBS orders.
- Needs an API key credential or similar authentication token configured in n8n to authorize requests.
- The base URL and API schema are derived from a bundled OpenAPI specification file.
Troubleshooting
Common issues:
- Incorrect or missing API credentials will cause authentication failures.
- Providing invalid pagination parameters (
limitornext) may result in empty responses or errors. - Network connectivity problems can prevent successful API calls.
Error messages:
- Authentication errors typically indicate misconfigured or expired API keys.
- Validation errors may occur if required parameters like
limitornextare omitted or set incorrectly.
Resolutions:
- Verify and update API credentials in n8n settings.
- Ensure
limitandnextparameters are correctly set according to the API documentation. - Check network access and firewall settings.
Links and References
- Wildberries API documentation (for FBS supplies and pagination) — consult the official WB developer portal.
- n8n documentation on creating and configuring HTTP request nodes and handling pagination.