Actions26
- Основные Отчёты Actions
- Отчёт Об Остатках На Складах Actions
- Отчёт О Товарах C Обязательной Маркировкой Actions
- Отчёты Об Удержаниях Actions
- Платная Приёмка Actions
- Платное Хранение Actions
- Продажи По Регионам Actions
- Доля Бренда В Продажах Actions
- Скрытые Товары Actions
- Отчёт О Возвратах И Перемещении Товаров Actions
- Динамика Оборачиваемости Actions
Overview
This node interacts with a specific API to retrieve analytics data related to retention reports ("Отчёты Об Удержаниях"). The particular operation "Get Analytics Characteristics Change" fetches changes in analytic characteristics over a specified date range. This is useful for monitoring how key metrics or attributes evolve during a reporting period, helping businesses analyze trends and make informed decisions.
Practical examples include:
- Tracking changes in customer retention characteristics month-over-month.
- Analyzing shifts in product performance indicators within a given timeframe.
- Generating reports for management on how certain analytics have changed between two dates.
Properties
| Name | Meaning |
|---|---|
| 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. |
Both properties are required and define the time window for which the analytics characteristic changes will be retrieved.
Output
The node outputs JSON data containing the analytics characteristics changes for the specified date range. The exact structure depends on the API response but generally includes details about the changes in various analytic metrics or characteristics relevant to retention reports.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authentication with the external service (WB API).
- The node uses a base URL defined in an imported Swagger/OpenAPI specification.
- Proper configuration of the API credentials in n8n is necessary for successful requests.
Troubleshooting
Common issues:
- Invalid or missing API credentials can cause authentication failures.
- Incorrect date formats may lead to request errors; ensure dates follow
YYYY-MM-DD. - Network connectivity problems can prevent the node from reaching the API endpoint.
Error messages:
- Authentication errors typically indicate invalid or missing API keys; verify credentials.
- Validation errors on date parameters suggest incorrect formatting; double-check input values.
- Timeout or connection errors imply network issues; check internet access and API availability.
Links and References
- No direct links provided in the source code.
- For more information, consult the API documentation corresponding to the retention reports analytics endpoint used by this node.