WbPromotion icon

WbPromotion

n8n node to interact with WB API

Actions28

Overview

This node interacts with the Wildberries (WB) API to manage advertising campaigns. Specifically, the "Get Adv Delete" operation retrieves information about a campaign identified by its ID, likely to confirm or review details before deletion or further processing. This node is useful in scenarios where users need to programmatically access campaign data for auditing, reporting, or conditional logic within an automation workflow.

Practical examples include:

  • Fetching campaign details before deciding to delete or modify them.
  • Integrating campaign status checks into marketing automation pipelines.
  • Automating cleanup of outdated or underperforming campaigns based on retrieved data.

Properties

Name Meaning
Id The unique identifier of the advertising campaign to retrieve. This is a required numeric value used to specify which campaign's data to fetch.

Output

The node outputs JSON data representing the details of the specified advertising campaign. The exact structure depends on the WB API response but typically includes fields such as campaign name, status, budget, targeting parameters, and performance metrics.

If the node supports binary data output, it would generally relate to attachments or reports associated with the campaign, but this is not indicated in the provided code.

Dependencies

  • Requires an API key credential for authenticating requests to the Wildberries API.
  • Depends on the WB API endpoint defined in the bundled Swagger JSON (07-promotion_modified.json).
  • Uses HTTP headers specifying JSON content type and acceptance.
  • The base URL for API requests is derived from the Swagger specification.

Troubleshooting

  • Common issues:

    • Invalid or missing campaign ID will result in errors or empty responses.
    • Authentication failures if the API key credential is not configured correctly.
    • Network or API downtime causing request failures.

  • Error messages:

    • "Unauthorized" or similar indicates problems with API credentials; verify and update the API key.
    • "Not Found" suggests the campaign ID does not exist; double-check the ID value.
    • Timeout or connection errors require checking network connectivity and API service status.

Links and References

  • Wildberries API documentation (refer to official WB developer resources for detailed API specs).
  • n8n documentation on creating and using custom nodes with API integrations.
  • Swagger/OpenAPI specification reference for understanding the API schema used.

Discussion