Actions26
- Основные Отчёты Actions
- Отчёт Об Остатках На Складах Actions
- Отчёт О Товарах C Обязательной Маркировкой Actions
- Отчёты Об Удержаниях Actions
- Платная Приёмка Actions
- Платное Хранение Actions
- Продажи По Регионам Actions
- Доля Бренда В Продажах Actions
- Скрытые Товары Actions
- Отчёт О Возвратах И Перемещении Товаров Actions
- Динамика Оборачиваемости Actions
Overview
This node interacts with a specific API to retrieve acceptance report tasks filtered by their Task Id and status. It is designed for scenarios where users need to fetch detailed information about particular acceptance tasks, such as tracking the progress or status of quality control or inspection tasks in a paid acceptance process.
Practical examples include:
- Monitoring the status of a specific acceptance task by its unique identifier.
- Integrating acceptance task data into workflows for reporting or further processing.
- Automating notifications or actions based on the status of acceptance tasks.
Properties
| Name | Meaning |
|---|---|
| Task Id | The unique identifier of the acceptance report task to retrieve. This is a required string input. |
Output
The node outputs JSON data representing the acceptance report tasks corresponding to the provided Task Id and their statuses. The exact structure depends on the API response but typically includes details such as task identifiers, status, timestamps, and related metadata.
If the node supports binary data output (not evident from the provided code), it would represent associated files or documents related to the acceptance reports.
Dependencies
- Requires an API key credential for authentication with the external service.
- Depends on the base URL and API schema defined in an imported JSON swagger file.
- Utilizes an OpenAPI helper library to build properties and handle requests.
- No additional environment variables are explicitly required beyond standard API credentials.
Troubleshooting
Common issues:
- Invalid or missing Task Id will result in errors or empty responses.
- Authentication failures if the API key credential is not configured correctly.
- Network or connectivity issues when reaching the external API endpoint.
Error messages:
- "Unauthorized" or similar indicates problems with API credentials; verify and update them.
- "Not Found" may indicate that the Task Id does not exist or is incorrect.
- Timeout or network errors suggest connectivity problems; check network settings.
Links and References
- Refer to the external API documentation for detailed information on acceptance report tasks and their statuses.
- n8n documentation on creating custom nodes and using API credentials.
- Swagger/OpenAPI specification used for this node is located in the bundled resource
../swagger/json/11-reports_modified.json.