Actions26
- Основные Отчёты Actions
- Отчёт Об Остатках На Складах Actions
- Отчёт О Товарах C Обязательной Маркировкой Actions
- Отчёты Об Удержаниях Actions
- Платная Приёмка Actions
- Платное Хранение Actions
- Продажи По Регионам Actions
- Доля Бренда В Продажах Actions
- Скрытые Товары Actions
- Отчёт О Возвратах И Перемещении Товаров Actions
- Динамика Оборачиваемости Actions
Overview
This node interacts with a specific API to retrieve daily turnover dynamics data for a given reporting period. It is designed to fetch time-series data reflecting how turnover changes day by day within the specified date range. This functionality is useful for financial analysts, inventory managers, or business intelligence professionals who need to monitor sales or stock turnover trends over time.
Practical examples include:
- Analyzing daily sales performance between two dates.
- Monitoring product turnover rates to optimize inventory management.
- Generating reports on daily revenue fluctuations for decision-making.
Properties
| Name | Meaning |
|---|---|
| Date From | Start date of the reporting period (format: YYYY-MM-DD). Specifies the first day from which turnover data will be retrieved. |
| Date To | End date of the reporting period (format: YYYY-MM-DD). Specifies the last day up to which turnover data will be retrieved. |
Output
The node outputs JSON data containing daily turnover dynamics for the specified date range. Each item in the output typically represents turnover metrics for a single day within the period. The exact structure depends on the API response but generally includes date keys and corresponding turnover values.
If the node supports binary data output, it would likely represent downloadable reports or files related to turnover data, but this is not indicated in the provided code snippet.
Dependencies
- Requires an API key credential for authentication with the external service providing turnover data.
- The node uses a base URL and OpenAPI specification bundled internally to construct requests.
- No additional environment variables are explicitly required beyond standard API authentication setup.
Troubleshooting
Common issues:
- Invalid or missing date parameters may cause the API to reject the request.
- Authentication failures if the API key is incorrect or missing.
- Network connectivity problems preventing access to the external API.
Error messages:
- "Invalid date range" — Ensure that "Date From" is before or equal to "Date To" and both are in the correct format.
- "Unauthorized" or "Authentication failed" — Verify that the API key credential is correctly configured.
- "Request timeout" or "Network error" — Check internet connection and API endpoint availability.
Links and References
- [API Documentation for Turnover Dynamics] (Not provided; refer to your API provider's official docs)
- n8n documentation on Creating Custom Nodes
- General best practices for date handling in APIs: https://www.iso.org/iso-8601-date-and-time-format.html