WbProducts icon

WbProducts

n8n node to interact with WB API

Actions41

Overview

This node allows uploading media files (images or videos) to a product on the Wildberries platform by interacting with its API. It is useful for managing product media assets programmatically, such as adding new images or videos to product listings.

Typical use cases include:

  • Automating the upload of product photos during bulk product creation or updates.
  • Adding additional media files to existing products without manual intervention.
  • Ensuring consistent media management workflows integrated into larger automation pipelines.

For example, you can upload the first video file for a product or add subsequent images by specifying their order number.

Properties

Name Meaning
X Nm Id The Wildberries article number (product identifier). This is required to specify which product the media file belongs to.
X Photo Number The sequence number of the media file being uploaded, starting at 1. For videos, this must always be 1. To add images after existing ones, use a number greater than the current count of uploaded media files.

Output

The node outputs JSON data representing the response from the Wildberries API after attempting to upload the media file. This typically includes status information about the upload operation.

If the node supports binary data output (e.g., the actual media file or processed content), it would be summarized here; however, based on the provided code and properties, the main output is JSON metadata related to the upload result.

Dependencies

  • Requires an API key credential for authenticating requests to the Wildberries API.
  • The node uses HTTP headers X-Nm-Id and X-Photo-Number to pass necessary parameters in the request.
  • No other external dependencies are explicitly indicated.

Troubleshooting

  • Common issues:

    • Incorrect or missing X Nm Id will cause the API to reject the upload because the product cannot be identified.
    • Using an invalid or duplicate X Photo Number (e.g., reusing a number already assigned to an existing media file) may lead to errors or overwriting.
    • Network or authentication failures if the API key is invalid or not configured properly.

  • Error messages:

    • Errors indicating missing headers usually mean required properties were not set.
    • API error responses might indicate invalid product IDs or media numbers; verify these values carefully.
    • Authentication errors suggest checking the API key credential setup.

Links and References

Discussion