Actions28
- Кампании Actions
- Создание Кампаний Actions
- Управление Кампаниями Actions
- Финансы Actions
- Параметры Кампаний Actions
- Медиа Actions
- Календарь Акций Actions
Overview
This node interacts with the Wildberries (WB) API to manage advertising campaigns. Specifically, the "Get Adv Stop" operation under the "Управление Кампаниями" (Campaign Management) resource retrieves information about a stopped advertising campaign by its ID. This is useful for users who want to programmatically check the status or details of campaigns that have been halted.
Practical examples include:
- Automatically fetching details of stopped campaigns to generate reports.
- Integrating campaign status checks into marketing automation workflows.
- Monitoring campaigns and triggering alerts or follow-up actions when campaigns stop.
Properties
| Name | Meaning |
|---|---|
| Id | The unique numeric identifier of the advertising campaign to retrieve. This is required to specify which campaign's stop information to fetch. |
Output
The node outputs JSON data containing the details of the stopped advertising campaign identified by the provided ID. The exact structure depends on the WB API response but typically includes campaign metadata such as status, stop reason, dates, and other relevant campaign attributes.
No binary data output is indicated.
Dependencies
- Requires an API key credential to authenticate requests to the Wildberries API.
- The node uses a base URL configured from an OpenAPI specification bundled within the node.
- Proper network access to the WB API endpoint is necessary.
Troubleshooting
- Missing or invalid campaign ID: Ensure the "Id" property is set and corresponds to an existing campaign.
- Authentication errors: Verify that the API key credential is correctly configured and has sufficient permissions.
- Network issues: Check connectivity to the WB API service.
- Unexpected API responses: Confirm that the WB API has not changed and that the node’s OpenAPI spec is up to date.
Common error messages will likely relate to HTTP status codes such as 401 Unauthorized, 404 Not Found (if campaign ID does not exist), or 500 Internal Server Error. Resolving these involves checking credentials, input parameters, and API availability.
Links and References
- Wildberries API documentation (official site, if available)
- n8n documentation on creating custom nodes and using API credentials