WbProducts icon

WbProducts

n8n node to interact with WB API

Actions41

Overview

This node interacts with the Wildberries (WB) API to retrieve directory information related to categories, products, and characteristics. Specifically, for the "Get Directory Countries" operation under the resource "Категории Предметы И Характеристики," it fetches a list of countries from the directory. This can be useful when you need to obtain country data for product categorization, localization, or filtering purposes.

Practical examples include:

  • Populating dropdowns with country options in product management workflows.
  • Localizing product information based on country-specific data.
  • Integrating country directory data into inventory or catalog systems.

Properties

Name Meaning
Locale Language of the response fields subjectName and name. Possible values: ru (Russian), en (English), zh (Chinese). Note: This property is not used in sandbox mode.

Output

The node outputs JSON data containing the list of countries retrieved from the WB directory. The structure typically includes country identifiers and localized names according to the selected locale. There is no indication that binary data is returned by this operation.

Example output JSON snippet might look like:

[
  {
    "id": 1,
    "name": "Russia",
    "subjectName": "Россия"
  },
  {
    "id": 2,
    "name": "China",
    "subjectName": "Китай"
  }
]

Dependencies

  • Requires an API key credential for authentication with the Wildberries API.
  • The node uses a base URL defined in its configuration, which points to the WB API endpoint.
  • No additional external services are explicitly required beyond the WB API access.

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 your credentials.
    • HTTP errors such as 4xx or 5xx suggest issues with request parameters or server availability; check the locale parameter and API status.
    • Empty or malformed responses may indicate changes in the API or incorrect usage; review the node configuration and update if necessary.

Links and References

Discussion