Actions29
- Объявление Actions
- Автозагрузка Actions
- Продвижение Actions
- Рейтинги и Отзывы Actions
Overview
This node integrates with the Avito API to retrieve data related to "Автозагрузка" (Autoload) reports, specifically focusing on fetching lists of ads from a given report. It is useful for automating the extraction and processing of advertisement data from Avito's autoload reports, which can be beneficial for monitoring ad statuses, analyzing performance, or syncing data with other systems.
A practical example would be retrieving all ads from a specific autoload report to check which ads were successfully published, which had problems, or which failed, enabling automated workflows for ad management or reporting.
Properties
| Name | Meaning |
|---|---|
| ID Отчета | Unique numeric ID of the autoload report to fetch data from. Required. |
| Номер Страницы | Page number to retrieve, starting from 1. Used for paginated requests when fetching ads. Required for the operation that lists ads. |
| Количество На Странице | Number of ads per page to retrieve, between 1 and 200. Controls pagination size. Required for listing ads. |
| Дополнительные Фильтры | Collection of filters to narrow down ads in the report: • ID Объявлений — filter by ad IDs from the file, separated by comma or pipe. • Avito ID — filter by Avito site ad IDs, separated by comma or pipe. |
| Включить Автоматическую Пагинацию | Boolean flag to enable automatic pagination to fetch all ads across multiple pages. |
| Тип Пагинации | Pagination type when automatic pagination is enabled: • Получить Все Объявления — fetch all available ads until the end. • Лимит Страниц — limit the number of pages fetched. |
| Максимум Страниц | Maximum number of pages to fetch when pagination type is limited. Each page can contain up to 200 ads. |
| 📝 Информация об объявлениях в выгрузке | Informational notice describing: • Pagination details (max 200 ads per request, page starts at 1). • Ad structure fields like ad_id, avito_id, status, status_detail, processing_time, errors. • Status meanings (success, problem, error, not_publish). • Filtering options and delimiters. |
Output
The node outputs JSON objects representing ads from the specified autoload report. Each ad object includes:
ad_id: The ad ID from the source file.avito_id: The ad ID on the Avito platform.status: Processing status of the ad (success,problem,error,not_publish).status_detail: Detailed status information.processing_time: Time taken to process the ad.errors: An array of error messages if any issues occurred during processing.
If automatic pagination is enabled, the output will include ads aggregated from multiple pages according to the pagination settings.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for authenticating with the Avito API.
- The node depends on internal routing utilities to handle the autoload resource operations.
- No additional external services beyond Avito API are required.
- Proper configuration of the API authentication credentials in n8n is necessary.
Troubleshooting
Common Issues:
- Providing an invalid or non-existent report ID will likely result in errors or empty results.
- Pagination parameters out of range (e.g., page number less than 1, items per page outside 1-200) may cause request failures.
- Filters with incorrect formatting (wrong delimiters or invalid IDs) might lead to no matching ads returned.
- Enabling pagination without setting limits properly could result in long-running executions or hitting API rate limits.
Error Messages:
- Errors related to unknown resources or operations indicate misconfiguration of the resource or operation parameters.
- API authentication errors suggest missing or invalid API credentials.
- Network or API errors should be checked by verifying connectivity and Avito API status.
To resolve these, ensure correct input values, valid credentials, and adherence to API usage guidelines.
Links and References
- Avito API Documentation (general reference for API capabilities)
- Pagination and filtering best practices as described in the node's informational notice property.