WbProducts icon

WbProducts

n8n node to interact with WB API

Actions41

Overview

This node interacts with a product catalog API to retrieve detailed information about items within categories and their characteristics. Specifically, the "Get Object All" operation under the resource "Категории Предметы И Характеристики" fetches a list of items (objects) filtered by various parameters such as language locale, name substring, pagination limits, and parent category ID.

Use cases include:

  • Fetching all products or items matching a search term across multiple languages.
  • Retrieving paginated lists of items for display or further processing.
  • Filtering items by their parent category to organize or analyze hierarchical data.

For example, you could use this node to get all items named "Носки" (socks) in Russian or English, limiting results to 1000 entries starting from a specific offset, which is useful for batch processing or syncing product catalogs.

Properties

Name Meaning
Locale Language of the response fields. Options: ru (Russian), en (English), zh (Chinese). Not used in sandbox mode.
Name Search term for item names (e.g., "Носки"). Performs substring search in any supported language.
Limit Maximum number of items to return. Maximum allowed is 1000.
Offset Position number from which to start returning results (for pagination).
Parent ID ID of the parent category of the item, used to filter items belonging to a specific category.

Output

The node outputs JSON data containing an array of items matching the query parameters. Each item typically includes its properties such as name, identifiers, and possibly other metadata depending on the API schema.

If the API supports binary data (e.g., images or files related to items), the node would handle it accordingly, but based on the provided code and properties, the output focuses on JSON structured data representing product objects.

Dependencies

  • Requires connection to the external WB API (Wildberries or similar) that provides product and category data.
  • Needs an API key credential configured in n8n for authentication with the external service.
  • The base URL and request defaults are set internally based on a bundled OpenAPI specification.

Troubleshooting

  • Empty or incomplete results: Check if the limit and offset parameters are set correctly; large offsets may result in no data if beyond available records.
  • Incorrect language display: Ensure the locale parameter matches one of the supported values (ru, en, zh).
  • Authentication errors: Verify that the API key credential is properly configured and has sufficient permissions.
  • Search not returning expected items: Confirm the name parameter is correctly specified and matches substrings in the target language.
  • Rate limiting or API errors: Monitor API usage limits and handle HTTP error responses gracefully.

Links and References

Discussion