Actions26
- Основные Отчёты Actions
- Отчёт Об Остатках На Складах Actions
- Отчёт О Товарах C Обязательной Маркировкой Actions
- Отчёты Об Удержаниях Actions
- Платная Приёмка Actions
- Платное Хранение Actions
- Продажи По Регионам Actions
- Доля Бренда В Продажах Actions
- Скрытые Товары Actions
- Отчёт О Возвратах И Перемещении Товаров Actions
- Динамика Оборачиваемости Actions
Overview
This node interacts with an analytics API to retrieve data about the brand share within sales, specifically focusing on "Parent Subjects" related to a given brand. It is useful for marketing analysts or sales strategists who want to understand how a particular brand performs in terms of market share across different parent categories or subjects over a specified time period.
Typical use cases include:
- Tracking brand performance trends over time.
- Comparing brand presence in various product categories.
- Supporting decision-making for marketing campaigns based on brand share insights.
For example, a user might query the brand share of "H&M" from February 28, 2025, to March 21, 2025, and receive analytics data showing how H&M's products are distributed among parent subjects/categories in that timeframe.
Properties
| Name | Meaning |
|---|---|
| Locale | Language of the parentName field in the response. Options: ru (Russian), en (English), zh (Chinese) |
| Brand | The brand name to analyze. Example: H&M. |
| Date From | Start date of the reporting period in YYYY-MM-DD format. |
| Date To | End date of the reporting period in YYYY-MM-DD format. |
Output
The node outputs JSON data containing analytics information about the brand share in parent subjects/categories. The key output field is expected to include:
parentName: The name of the parent subject/category, localized according to the selectedLocale.- Metrics related to the brand's share in sales within each parent subject for the specified date range.
No binary data output is indicated by the source code or properties.
Dependencies
- Requires access to an external analytics API endpoint (likely Wildberries or similar) that provides brand share data.
- Needs an API authentication token or API key credential configured in n8n to authorize requests.
- The node uses HTTP query parameters to send inputs (
locale,brand,dateFrom,dateTo) to the API.
Troubleshooting
Common issues:
- Invalid date formats for
Date FromorDate Tomay cause request failures. - Missing or incorrect brand names could result in empty or error responses.
- Network or authentication errors if API credentials are not properly set up.
- Invalid date formats for
Error messages:
- Errors related to authorization typically indicate missing or invalid API keys.
- Validation errors may occur if required parameters are omitted or malformed.
Resolutions:
- Ensure dates follow the
YYYY-MM-DDformat. - Verify the brand name exists in the analytics system.
- Confirm API credentials are correctly configured in n8n.
- Ensure dates follow the
Links and References
- No direct links provided in the source code.
- For more details, consult the API documentation of the analytics service providing brand share data.
- Refer to n8n documentation on setting up API credentials and HTTP request nodes for general guidance.