Actions26
- Основные Отчёты Actions
- Отчёт Об Остатках На Складах Actions
- Отчёт О Товарах C Обязательной Маркировкой Actions
- Отчёты Об Удержаниях Actions
- Платная Приёмка Actions
- Платное Хранение Actions
- Продажи По Регионам Actions
- Доля Бренда В Продажах Actions
- Скрытые Товары Actions
- Отчёт О Возвратах И Перемещении Товаров Actions
- Динамика Оборачиваемости Actions
Overview
This node interacts with a reporting API to retrieve supplier income data filtered by a specified date and time. It is useful for automating the extraction of financial or supply chain reports related to supplier incomes within a given timeframe. For example, a user can fetch all supplier income records updated after a certain date to analyze recent transactions or generate periodic financial summaries.
Properties
| Name | Meaning |
|---|---|
| Date From | The starting date and time from which to retrieve supplier income data. This must be provided in RFC3339 format and represents the last modification date/time of the supply. Time can be specified with precision up to seconds or milliseconds and should be in the Moscow timezone (UTC+3). Examples include: 2019-06-20, 2019-06-20T23:59:59, or 2019-06-20T00:00:00.12345. |
Output
The node outputs JSON data containing supplier income information filtered by the specified "Date From" parameter. The exact structure depends on the API response but typically includes details such as supplier identifiers, income amounts, dates, and other relevant report fields. There is no indication that the node outputs binary data.
Dependencies
- Requires an API key credential for authentication with the external reporting API.
- The node uses a base URL defined in its configuration to send requests.
- The "Date From" property is sent as a query parameter in the API request.
- No additional environment variables or services are explicitly required beyond the API access.
Troubleshooting
- Invalid Date Format: If the "Date From" value is not in the correct RFC3339 format or does not respect the Moscow timezone, the API may reject the request or return no data. Ensure the date string matches the expected format.
- Missing Credentials: Without proper API authentication credentials, the node will fail to connect to the service. Verify that the API key or token is correctly configured.
- Empty Response: If no supplier incomes are returned, check that the "Date From" parameter is set correctly and that there is data available for that period.
- API Rate Limits: The API might enforce limits on request frequency; excessive calls could result in errors or throttling.
Links and References
- RFC3339 Date/Time Format
- API documentation section on date/time parameters and supplier income reports (referenced internally in the node's description)