Actions26
- Основные Отчёты Actions
- Отчёт Об Остатках На Складах Actions
- Отчёт О Товарах C Обязательной Маркировкой Actions
- Отчёты Об Удержаниях Actions
- Платная Приёмка Actions
- Платное Хранение Actions
- Продажи По Регионам Actions
- Доля Бренда В Продажах Actions
- Скрытые Товары Actions
- Отчёт О Возвратах И Перемещении Товаров Actions
- Динамика Оборачиваемости Actions
Overview
This node interacts with a marketplace API to retrieve analytics data about banned (blocked) products. Specifically, it fetches a list of hidden or banned products along with details such as the reason for blocking. This is useful for sellers or analysts who want to monitor which products have been blocked and understand the reasons behind these restrictions.
Common scenarios include:
- Monitoring product compliance and identifying issues causing blocks.
- Sorting and filtering banned products by various attributes to prioritize actions.
- Generating reports on blocked items for internal review or external communication.
Example: A seller wants to get all their banned products sorted by brand name in ascending order to quickly identify which brands are most affected.
Properties
| Name | Meaning |
|---|---|
| Sort | The attribute by which to sort the results. Options: brand (by brand), nmId (by marketplace article number), title (by product name), vendorCode (by vendor article number), reason (by block reason). |
| Order | The sorting order direction. Options: desc (descending: from highest numeric or last alphabetically to lowest/first), asc (ascending: from lowest numeric or first alphabetically to highest/last). |
Output
The node outputs JSON data containing the list of banned products with their associated details. Each item typically includes fields such as brand, product ID, title, vendor code, and the reason for blocking.
If binary data were involved (e.g., images or documents), it would be summarized here, but this node focuses on JSON analytics data only.
Dependencies
- Requires an API key credential to authenticate requests to the marketplace API.
- Depends on the marketplace's reports API endpoint for fetching banned product analytics.
- No additional environment variables or external services beyond the configured API authentication are needed.
Troubleshooting
Common Issues:
- Invalid or missing API credentials will cause authentication failures.
- Incorrect property values for sorting or ordering may result in API errors or unexpected output.
- Network connectivity problems can prevent data retrieval.
Error Messages:
- Authentication errors: Check that the API key credential is correctly set up and has necessary permissions.
- Validation errors on parameters: Ensure "Sort" and "Order" properties use allowed values.
- Timeout or connection errors: Verify network access to the API endpoint.
Links and References
- Marketplace API documentation for banned products analytics (refer to your marketplace provider’s official docs).
- n8n documentation on creating and using API key credentials.
- General best practices for handling API pagination and sorting in n8n nodes.