WbAnalytics icon

WbAnalytics

n8n node to interact with WB API

Actions19

Overview

This node interacts with a sales funnel analytics API to post and retrieve grouped historical reports. Specifically, the "Post Nm Report Grouped History" operation under the "Воронка Продаж" (Sales Funnel) resource allows users to send parameters such as object IDs, brand names, tag IDs, a time period, timezone, and aggregation level to generate aggregated sales data over a specified timeframe.

Typical use cases include:

  • Analyzing sales performance trends for specific products or brands over days or weeks.
  • Generating reports filtered by tags or categories to understand segment behavior.
  • Adjusting report granularity by choosing daily or weekly aggregation.
  • Integrating sales funnel insights into automated workflows for business intelligence.

For example, a user might want to track how certain product IDs performed in terms of sales between June 21 and June 23, aggregated daily, within the Moscow timezone.

Properties

Name Meaning
Object I Ds IDs of the items/products to include in the report (JSON array of numbers).
Brand Names List of brand names to filter the report by (JSON array of strings).
Tag I Ds IDs of tags/labels to filter the report by (JSON array of numbers).
Period Time period for the report, including begin and end dates in ISO format (JSON object).
Timezone Timezone string to interpret the period; defaults to "Europe/Moscow" if not specified.
Aggregation Level Level of data aggregation: either day or week. Defaults to day if not specified.

Output

The node outputs JSON data representing the grouped historical sales report based on the input filters and aggregation level. The structure typically includes aggregated metrics per day or week for the specified objects, brands, and tags within the given period and timezone.

If binary data were involved, it would represent downloadable report files or similar, but this node focuses on JSON responses.

Dependencies

  • Requires access to an external sales analytics API endpoint (likely Wildberries or similar).
  • Needs an API key or authentication token configured in n8n credentials to authorize requests.
  • Uses JSON parsing for input properties to correctly format request bodies.
  • The base URL and API schema are loaded from bundled swagger/openapi JSON definitions.

Troubleshooting

  • Invalid JSON Input: If the JSON arrays or objects for properties like objectIDs, brandNames, tagIDs, or period are malformed, the node will fail to parse them. Ensure valid JSON syntax.
  • Missing Required Fields: The period property is required. Omitting it will cause errors.
  • Timezone Issues: Using an invalid timezone string may lead to incorrect data aggregation or API errors.
  • API Authentication Errors: If the API key or token is missing or invalid, the node will return authorization errors.
  • Aggregation Level: Providing unsupported aggregation levels other than day or week may cause the API to reject the request.

To resolve these issues:

  • Validate all JSON inputs before running the node.
  • Confirm that the API credentials are properly set up in n8n.
  • Use supported values for timezone and aggregation level.
  • Check API documentation for any additional constraints.

Links and References

Discussion