Actions19
- Статистика По Продвижению Actions
- Воронка Продаж Actions
- Поисковые Запросы Actions
- История Остатков Actions
- Аналитика Продавца CSV Actions
Overview
This node interacts with the Wildberries API to retrieve advertising statistics, specifically focusing on automatic advertising campaign word statistics. It is useful for marketers and analysts who want to monitor and analyze the performance of their automatic ad campaigns by fetching detailed word-level data. For example, a user can input a campaign ID to get insights into which keywords are driving traffic or conversions in that campaign.
Properties
| Name | Meaning |
|---|---|
| Id | The numeric ID of the advertising campaign for which to retrieve automatic advertising word statistics. This is a required field. |
Output
The node outputs JSON data containing statistics related to the specified advertising campaign's automatic words. The exact structure depends on the API response but typically includes metrics such as keyword performance, impressions, clicks, and other relevant advertising statistics. There is no indication that the node outputs binary data.
Dependencies
- Requires an API key credential to authenticate requests to the Wildberries API.
- Depends on the Wildberries analytics API endpoint configured via the base URL.
- Uses HTTP headers specifying JSON content type and acceptance.
- No additional external services beyond the Wildberries API are indicated.
Troubleshooting
- Missing or invalid campaign ID: Since the "Id" property is required, omitting it or providing an invalid value will likely cause errors. Ensure the campaign ID is correct and provided.
- Authentication errors: If the API key or authentication token is missing or invalid, the node will fail to fetch data. Verify that the API credentials are correctly set up in n8n.
- API rate limits or downtime: The Wildberries API may impose rate limits or experience outages. In such cases, retry after some time or check the API status.
- Unexpected API response structure: If the API changes its response format, the node might not parse the output correctly. Monitor for updates from Wildberries.
Links and References
- Wildberries API documentation (general reference): https://openapi.wildberries.ru/
- n8n documentation on creating custom nodes: https://docs.n8n.io/integrations/creating-nodes/