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 their characteristics. Specifically, the "Get Directory Colors" operation fetches a directory listing of available colors used in the product catalog. This can be useful for workflows that need to standardize or filter products by color attributes, such as inventory management, product data enrichment, or e-commerce analytics.
For example, an e-commerce manager might use this node to obtain the list of all possible product colors in the WB catalog to ensure consistent color naming across listings or to generate reports on color trends.
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 directory of colors from the WB API. The structure typically includes color identifiers and their localized names according to the selected locale. This output can be used downstream in workflows to map or filter products by color.
No binary data output is indicated.
Dependencies
- Requires access to the Wildberries API.
- Optionally uses an API key credential for authentication (not explicitly required but supported).
- The node depends on a base URL configured from a Swagger/OpenAPI specification bundled within the node.
- No additional environment variables are specified.
Troubleshooting
Common issues:
- Incorrect or missing API credentials may cause authentication failures.
- Using unsupported locale values could result in unexpected or empty responses.
- Network connectivity problems can prevent successful API calls.
Error messages:
- Authentication errors typically indicate invalid or missing API keys; verify credentials.
- HTTP errors like 4xx or 5xx suggest issues with request parameters or server availability; check the locale parameter and API status.
- Parsing errors may occur if the API response format changes; ensure the node is updated accordingly.
Links and References
- Wildberries API documentation (if publicly available)
- n8n documentation on creating custom nodes and using API credentials