Actions41
- Склады Продавца Actions
- Остатки На Складах Продавца Actions
- Категории Предметы И Характеристики Actions
- Создание Карточек Товаров Actions
- Карточки Товаров Actions
- Медиафайлы Actions
- Ярлыки Actions
- Цены И Скидки Actions
Overview
This node interacts with the Wildberries (WB) API to retrieve data related to product categories, items, and characteristics. Specifically, the "Get Directory Seasons" operation fetches a list of seasons from the directory, which can be useful for categorizing products by seasonality or filtering product data based on seasonal attributes.
Common scenarios where this node is beneficial include:
- E-commerce platforms wanting to organize or filter products by season.
- Inventory management systems that need to tag or sort items according to seasonal availability.
- Marketing automation workflows that tailor campaigns based on seasonal product categories.
For example, a user might use this node to get all available seasons in the WB catalog and then use that information to update their product database or trigger season-specific promotions.
Properties
| Name | Meaning |
|---|---|
| Locale | Language of the response fields subjectName and name. Possible values: ru (Russian), en (English), zh (Chinese). Not used in sandbox mode. |
Output
The node outputs JSON data containing the list of seasons retrieved from the WB directory. Each item in the output typically includes season-related fields such as identifiers and localized names depending on the selected locale.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating requests to the Wildberries API.
- The node uses the WB API base URL configured internally via the bundled OpenAPI specification.
- No additional environment variables are explicitly required beyond the API authentication setup.
Troubleshooting
Common issues:
- Incorrect or missing API credentials will cause authentication failures.
- Using unsupported locale values may result in incomplete or empty responses.
- Network connectivity problems can prevent successful API calls.
Error messages:
- Authentication errors typically indicate invalid or missing API keys; verify and re-enter credentials.
- HTTP errors like 4xx or 5xx suggest issues with request parameters or server availability; check the locale parameter and try again later.
- Empty or malformed responses may indicate changes in the WB API; ensure the node and its dependencies are up to date.
Links and References
- Wildberries API Documentation (official API docs, if publicly accessible)
- n8n documentation on creating custom nodes