WbPromotion icon

WbPromotion

n8n node to interact with WB API

Actions28

Overview

This node is designed to interact with the Wildberries (WB) API, specifically for creating promotional campaigns. The operation "Post Adv Supplier Nms" under the resource "Создание Кампаний" (which translates as "Campaign Creation") allows users to send data to create or manage advertising supplier campaigns on the WB platform.

Typical use cases include automating campaign creation workflows, integrating campaign management into larger automation processes, or bulk uploading campaign data from other systems.

For example, a marketing team could use this node to programmatically create multiple advertising campaigns based on dynamic input data, streamlining their promotional efforts without manual intervention.

Properties

Name Meaning
Body JSON object representing the request body to be sent to the WB API for creating or managing an advertising supplier campaign. The property expects a string that will be parsed as JSON before sending.
  • The "Body" property is required to contain valid JSON data describing the campaign details.
  • This property is dynamically parsed (JSON.parse) before being sent in the HTTP request body.

Output

The node outputs the response from the WB API call in the json field of the output item. This typically contains the result of the campaign creation request, such as confirmation details, IDs of created campaigns, or error messages if the request failed.

No binary data output is indicated by the source code.

Dependencies

  • Requires access to the Wildberries API endpoint configured via the base URL extracted from the bundled swagger JSON.
  • Needs an API key or authentication token credential configured in n8n to authorize requests to the WB API.
  • The node uses standard HTTP headers including Accept: application/json and Content-Type: application/json.

Troubleshooting

  • Invalid JSON in Body: Since the "Body" property is parsed with JSON.parse, invalid JSON strings will cause errors. Ensure the input is correctly formatted JSON.
  • Authentication Errors: If the API key or credentials are missing or incorrect, the node will fail to authenticate with the WB API.
  • API Endpoint Issues: Network issues or changes in the WB API endpoint may cause failures. Verify connectivity and endpoint correctness.
  • Unexpected API Responses: If the WB API returns errors due to invalid campaign data or business logic constraints, review the API response in the node output for details.

Links and References

Discussion