WbProducts icon

WbProducts

n8n node to interact with WB API

Actions41

Overview

This node is designed to interact with a product card management API, specifically to merge multiple product cards under a single existing product identifier (imtID). The operation "Post Cards Movenm" allows users to consolidate several product cards identified by their nmIDs into one target product card identified by targetIMT. This can be useful in scenarios where duplicate or related product entries need to be unified for inventory management, reporting, or sales tracking.

Practical examples include:

  • A seller wants to merge multiple listings of the same product that were created separately.
  • Consolidating product data after importing from different sources to maintain a clean catalog.

Properties

Name Meaning
Target IMT An existing product identifier (imtID) under which the specified product cards will be merged. Must be a number.
Nm I Ds A JSON array of product card identifiers (nmIDs) to be merged into the target IMT. Maximum 30 IDs allowed.

Output

The node outputs JSON data representing the response from the API after attempting to merge the product cards. This typically includes confirmation of the merge operation, status messages, or error details if the operation failed.

No binary data output is indicated.

Dependencies

  • Requires an API key credential for authentication with the external product card management API.
  • The base URL and request headers are configured based on a bundled OpenAPI specification.
  • No additional environment variables are explicitly required beyond the API authentication setup.

Troubleshooting

  • Common issues:

    • Providing more than 30 nmIDs in the Nm I Ds property may cause the API to reject the request.
    • Using a non-existent or invalid targetIMT could result in errors indicating the target product card does not exist.
    • Malformed JSON in the Nm I Ds input could lead to parsing errors before the request is sent.

  • Error messages:

    • Errors related to authentication failure suggest checking the API key credential configuration.
    • Validation errors from the API about input parameters indicate verifying the correctness and format of targetIMT and nmIDs.
    • Network or timeout errors require ensuring connectivity to the API endpoint.

Links and References

Discussion