WbAnalytics icon

WbAnalytics

n8n node to interact with WB API

Actions19

Overview

This node interacts with the "Воронка Продаж" (Sales Funnel) resource of a specific API to post detailed report history data for given product identifiers (Nm IDs) over a specified period. It is useful for users who want to retrieve or update sales analytics data filtered by product articles and time frames, aggregated by day or week.

Typical use cases include:

  • Uploading or syncing detailed sales report history for selected products.
  • Analyzing sales trends over custom periods.
  • Integrating sales funnel data into workflows for reporting or further processing.

Properties

Name Meaning
Nm I Ds List of product article numbers (WB articles), maximum 20 items. Example: [1234567]
Period Time period object specifying begin and end dates in YYYY-MM-DD format.
Timezone Time zone string for the period; defaults to Europe/Moscow if not specified.
Aggregation Level Aggregation type for the report data; possible values are day (default) or week.

Output

The node outputs JSON data representing the response from the API after posting the detailed report history. The structure typically includes the status of the operation and any relevant data returned by the API related to the posted report details.

No binary data output is indicated.

Dependencies

  • Requires an API key credential for authentication with the WB API (referred generically as an API key credential).
  • Uses a base URL configured from an imported Swagger/OpenAPI specification.
  • Depends on the @devlikeapro/n8n-openapi-node package for building request properties and handling API interaction.

Troubleshooting

  • Invalid Nm IDs: Ensure that the list of Nm IDs is valid JSON and contains no more than 20 items.
  • Incorrect Period Format: The period must be a JSON object with valid begin and end date strings in YYYY-MM-DD format.
  • Timezone Issues: If the timezone is invalid or omitted, the default Europe/Moscow will be used, which might affect data aggregation results.
  • Aggregation Level Errors: Only day or week are accepted; other values may cause errors.
  • Authentication Failures: Verify that the API key credential is correctly set up and has necessary permissions.
  • API Response Errors: Check the API response message for details; common issues include rate limits, invalid parameters, or server errors.

Links and References

Discussion