Actions26
- Основные Отчёты Actions
- Отчёт Об Остатках На Складах Actions
- Отчёт О Товарах C Обязательной Маркировкой Actions
- Отчёты Об Удержаниях Actions
- Платная Приёмка Actions
- Платное Хранение Actions
- Продажи По Регионам Actions
- Доля Бренда В Продажах Actions
- Скрытые Товары Actions
- Отчёт О Возвратах И Перемещении Товаров Actions
- Динамика Оборачиваемости Actions
Overview
This node interacts with the Wildberries API to retrieve acceptance reports for a specified date range. It is designed to fetch detailed data about paid acceptance activities within a given period, which can be useful for financial reconciliation, auditing, or operational analysis.
Typical use cases include:
- Generating acceptance reports for accounting purposes.
- Monitoring paid acceptance transactions over time.
- Integrating acceptance data into dashboards or other reporting tools.
For example, a user might set the "Date From" and "Date To" properties to cover the last month and then retrieve all acceptance report entries for that period.
Properties
| Name | Meaning |
|---|---|
| Date From | The start date of the reporting period in YYYY-MM-DD format. |
| Date To | The end date of the reporting period in YYYY-MM-DD format. |
Both properties are required and define the date range for which the acceptance report will be fetched.
Output
The node outputs JSON data containing the acceptance report details for the specified date range. The structure corresponds to the response from the Wildberries API's acceptance report endpoint. This typically includes records of paid acceptance transactions, dates, quantities, and related metadata.
No binary data output is indicated by the source code.
Dependencies
- Requires an API key credential for authenticating requests to the Wildberries API.
- The node uses a base URL defined in its configuration, pointing to the Wildberries reports API.
- No additional external dependencies are indicated beyond the API access.
Troubleshooting
- Invalid Date Format: Ensure that "Date From" and "Date To" are provided in the correct
YYYY-MM-DDformat. Incorrect formats may cause request failures. - Authentication Errors: If the API key is missing or invalid, the node will fail to authenticate. Verify that the API key credential is correctly configured.
- Empty or Unexpected Responses: Confirm that the date range actually contains data. Some date ranges may return empty results if no acceptance activity occurred.
- API Rate Limits: Excessive requests may trigger rate limiting by the Wildberries API. Implement retries or backoff as needed.
Links and References
- Wildberries API Documentation (general reference for API endpoints)
- n8n Documentation on Creating Custom Nodes