Actions41
- Склады Продавца Actions
- Остатки На Складах Продавца Actions
- Категории Предметы И Характеристики Actions
- Создание Карточек Товаров Actions
- Карточки Товаров Actions
- Медиафайлы Actions
- Ярлыки Actions
- Цены И Скидки Actions
Overview
This node interacts with the Wildberries (WB) API to retrieve a paginated list of size information for a specific product identified by its article number (Nm ID). It is useful when you need to fetch detailed size data related to a particular product from WB's catalog, such as for inventory management, price comparison, or integration with other sales platforms.
Practical examples:
- Fetching available sizes for a given product to display on an e-commerce site.
- Synchronizing product size details between WB and your internal database.
- Analyzing size availability trends for specific products.
Properties
| Name | Meaning |
|---|---|
| Limit | Number of items to return per page (pagination). Maximum allowed is 1000. |
| Offset | The index after which to start returning data (used for pagination offset). |
| Nm ID | The Wildberries article number (product identifier) for which to get size information. |
Output
The node outputs JSON data containing a list of size details for the specified product. Each item in the output corresponds to a size variant associated with the product identified by the Nm ID. The structure typically includes size attributes and possibly stock or pricing info depending on the API response.
No binary data output is indicated.
Dependencies
- Requires access to the Wildberries API.
- Needs an API key credential configured in n8n for authentication with the WB API.
- The base URL and request headers are preconfigured based on the bundled OpenAPI specification.
Troubleshooting
Common issues:
- Invalid or missing Nm ID will result in no data or error responses.
- Exceeding the maximum limit (over 1000) may cause the API to reject the request.
- Network or authentication errors if the API key is not set or invalid.
Error messages:
- "Unauthorized" or similar indicates missing/invalid API credentials.
- "Bad Request" may indicate invalid parameters like negative offset or zero limit.
- "Not Found" if the Nm ID does not correspond to any product.
Resolution tips:
- Verify that the API key credential is correctly configured.
- Ensure Nm ID is valid and exists in WB's system.
- Use appropriate pagination values within allowed ranges.
Links and References
- Wildberries API Documentation (official API docs)
- n8n documentation on creating custom nodes
- Pagination best practices in REST APIs: https://restfulapi.net/pagination/