Actions26
- Основные Отчёты Actions
- Отчёт Об Остатках На Складах Actions
- Отчёт О Товарах C Обязательной Маркировкой Actions
- Отчёты Об Удержаниях Actions
- Платная Приёмка Actions
- Платное Хранение Actions
- Продажи По Регионам Actions
- Доля Бренда В Продажах Actions
- Скрытые Товары Actions
- Отчёт О Возвратах И Перемещении Товаров Actions
- Динамика Оборачиваемости Actions
Overview
This node interacts with a specific API to retrieve retention reports, focusing on the "Get Analytics Storage Coefficient" operation within the "Отчёты Об Удержаниях" (Retention Reports) resource. It is designed to fetch analytics data related to storage coefficients for a given date, which falls within the reporting period.
Typical use cases include:
- Automating the retrieval of retention analytics for inventory or product storage.
- Integrating retention coefficient data into dashboards or further processing workflows.
- Scheduling regular data pulls for historical analysis or reporting.
For example, a user might set the date property to "2023-12-01" to get the storage coefficient analytics for December 1st, 2023.
Properties
| Name | Meaning |
|---|---|
| Date | The date included in the reporting period, formatted as YYYY-MM-DD. This specifies the day for which the analytics storage coefficient report is requested. |
Output
The node outputs JSON data containing the analytics storage coefficient information corresponding to the specified date. The exact structure depends on the API response but generally includes metrics and values related to storage coefficients in the retention reports.
No binary data output is indicated by the source code.
Dependencies
- Requires an API key credential for authentication with the external service providing the retention reports.
- The node uses a base URL derived from an imported Swagger/OpenAPI specification.
- The node expects the API to accept query parameters, specifically the
dateparameter. - No additional environment variables are explicitly required beyond standard API authentication setup.
Troubleshooting
- Invalid Date Format: If the date is not in
YYYY-MM-DDformat, the API may reject the request or return errors. Ensure the date string matches the expected format. - Authentication Errors: Missing or invalid API credentials will cause authorization failures. Verify that the API key or token is correctly configured.
- API Endpoint Issues: Changes in the external API or network connectivity problems can lead to failed requests. Check the base URL and network access.
- Empty or Unexpected Response: If the API returns no data or unexpected fields, verify that the date corresponds to a valid reporting period and that the API supports the requested operation.
Links and References
- Date Format Reference
- Documentation for the external API (not provided here) should be consulted for detailed response schema and authentication setup.