WbProducts icon

WbProducts

n8n node to interact with WB API

Actions41

Overview

This node interacts with the Wildberries (WB) API to retrieve a list of product cards. It is designed to fetch detailed information about product cards based on specified filtering and sorting criteria. This functionality is useful for e-commerce managers, data analysts, or developers who want to programmatically access product card data from WB for inventory management, analytics, or integration with other systems.

A practical example would be retrieving all product cards filtered by specific tags, brands, or object IDs, optionally sorted according to custom rules, and localized in a preferred language.

Properties

Name Meaning
Locale Language of the response fields name, value, and object. Possible values: ru (Russian), en (English), zh (Chinese). Not used in sandbox mode.
Settings JSON object containing request settings including sorting, filtering, and pagination cursor. The filter can include arrays of tag IDs, object IDs, and brands to narrow down the product cards returned. Example structure:
```json
{
"sort": {},
"filter": {
"tagIDs": [null],
"objectIDs": [null],
"brands": [null]
},
"cursor": {}
}
```

Output

The node outputs JSON data representing the list of product cards retrieved from the WB API. Each item in the output typically contains details such as product names, values, associated objects, and other metadata localized according to the selected locale.

If binary data were involved, it would represent files or media related to product cards, but this node focuses on JSON responses only.

Dependencies

  • Requires an API key credential for authenticating requests to the Wildberries API.
  • The node uses a base URL configured from an imported OpenAPI specification.
  • No additional external dependencies are indicated beyond standard HTTP request handling.

Troubleshooting

  • Common issues:
    • Incorrect or missing API authentication token may cause authorization errors.
    • Malformed JSON in the Settings property can lead to request failures.
    • Using unsupported locale values might result in unexpected or empty response fields.
  • Error messages:
    • Authorization errors typically indicate invalid or missing credentials; verify API key setup.
    • Validation errors on the Settings JSON suggest syntax issues; ensure valid JSON format.
    • Network or timeout errors may require checking connectivity or API availability.

Links and References

  • Wildberries API documentation (official site or developer portal) for detailed API usage and parameters.
  • n8n documentation on creating and configuring HTTP request nodes and using JSON input properties.

Discussion