Actions41
- Склады Продавца Actions
- Остатки На Складах Продавца Actions
- Категории Предметы И Характеристики Actions
- Создание Карточек Товаров Actions
- Карточки Товаров Actions
- Медиафайлы Actions
- Ярлыки Actions
- Цены И Скидки Actions
Overview
This node interacts with the Wildberries API to retrieve directory kinds related to categories, subjects, and characteristics. Specifically, the "Get Directory Kinds" operation fetches a list of directory kinds, which can be useful for understanding or categorizing product data according to Wildberries' classification system.
Common scenarios where this node is beneficial include:
- Enriching product data by mapping items to standardized directory kinds.
- Building integrations that require localized category information from Wildberries.
- Automating workflows that depend on product categorization metadata.
For example, an e-commerce manager might use this node to pull directory kinds in English (en) to display user-friendly category names on their storefront or to synchronize product attributes with Wildberries’ taxonomy.
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 kinds retrieved from the Wildberries API. The structure typically includes fields such as identifiers and localized names corresponding to each directory kind.
No binary data output is expected from this operation.
Dependencies
- Requires an API key credential for authenticating requests to the Wildberries API.
- The node uses a base URL defined in its internal configuration pointing to the Wildberries API endpoint.
- No additional environment variables are explicitly required beyond the API authentication setup.
Troubleshooting
Common issues:
- Incorrect or missing API credentials will result in authentication errors.
- Using unsupported locale values may cause the API to return unexpected results or errors.
- Network connectivity problems can prevent successful API calls.
Error messages:
- Authentication failures typically indicate invalid or absent API keys; verify and update credentials accordingly.
- If the API returns errors about unsupported locales, ensure the
Localeproperty is set to one of the supported values (ru,en,zh). - Timeout or connection errors suggest checking network access and API availability.
Links and References
- Wildberries API Documentation (for detailed API specs and usage)
- n8n documentation on creating custom nodes