WbAnalytics icon

WbAnalytics

n8n node to interact with WB API

Overview

This node interacts with the Wildberries (WB) API to retrieve advertising statistics related to specific campaigns. The "Get Adv Stat Words" operation under the resource "Статистика По Продвижению" (Promotion Statistics) fetches keyword-level advertising data for a given campaign ID. This is useful for marketers and analysts who want to analyze the performance of keywords in their WB advertising campaigns, optimize bids, or evaluate which keywords drive the most traffic or conversions.

Practical examples include:

  • Retrieving keyword statistics to identify high-performing search terms.
  • Monitoring campaign effectiveness by analyzing keyword-level data.
  • Exporting advertising data for further analysis or reporting.

Properties

Name Meaning
Id The numeric ID of the advertising campaign for which keyword statistics are requested. This is a required field.

Output

The node outputs JSON data containing the advertising statistics for keywords associated with the specified campaign ID. The exact structure depends on the WB API response but typically includes fields such as keyword text, impressions, clicks, cost, and other relevant metrics.

If the node supports binary data output, it would represent any files or media returned by the API; however, based on the provided code and operation, the output is primarily JSON-formatted statistical data.

Dependencies

  • Requires access to the Wildberries API.
  • Needs an API key credential configured in n8n to authenticate requests to the WB API.
  • The node uses a base URL and request defaults defined from a bundled OpenAPI specification.
  • No additional external dependencies beyond the WB API and standard HTTP request handling.

Troubleshooting

  • Missing or invalid campaign ID: Ensure the "Id" property is set correctly and corresponds to an existing campaign.
  • Authentication errors: Verify that the API key credential is properly configured and has sufficient permissions.
  • Network or API errors: Check connectivity to the WB API endpoint and confirm the service is operational.
  • Unexpected API responses: Confirm that the API version matches the node's expectations and that the campaign ID is valid.

Common error messages might include authentication failures, 404 not found if the campaign ID does not exist, or 400 bad request if parameters are malformed.

Links and References

  • Wildberries API documentation (official site, if available)
  • n8n documentation on creating and using custom nodes
  • General REST API usage and troubleshooting guides

Discussion