WbCommunication icon

WbCommunication

n8n node to interact with WB API

Overview

This node interacts with the Wildberries (WB) API to retrieve supplier valuations, specifically fetching reviews or feedback related to suppliers. It is useful for scenarios where users want to analyze supplier performance, customer satisfaction, or product feedback aggregated from the WB platform. For example, a user might use this node to gather supplier ratings in different languages to monitor reputation or to integrate supplier review data into their own dashboards.

Properties

Name Meaning
X Locale Selects the language of the response field values. Options: ru (Russian), en (English), zh (Chinese)

Output

The node outputs JSON data containing supplier valuation details as returned by the WB API. The structure includes fields representing supplier reviews and ratings, localized according to the selected X Locale. If the API supports binary data (e.g., images or documents related to reviews), it would be included accordingly, but based on the provided code, the output focuses on JSON responses.

Dependencies

  • Requires an API key credential for authenticating requests to the WB API.
  • Depends on the WB API endpoint defined in the bundled swagger JSON (08-communications_modified.json).
  • Uses HTTP headers including Accept: application/json, Content-Type: application/json, and a custom header X-Locale to specify response language.
  • No additional external services are indicated beyond the WB API.

Troubleshooting

  • Common issues:
    • Incorrect or missing API authentication token may cause authorization errors.
    • Using an unsupported locale value in X Locale could result in unexpected or default language responses.
    • Network connectivity problems can prevent successful API calls.
  • Error messages:
    • Authorization failures typically indicate invalid or missing credentials; verify API key setup.
    • HTTP 4xx or 5xx errors suggest issues with request parameters or server availability; check the X Locale value and API status.
    • JSON parsing errors may occur if the API response format changes unexpectedly.

Links and References

Discussion