WbProducts icon

WbProducts

n8n node to interact with WB API

Actions41

Overview

This node interacts with the "Карточки Товаров" (Product Cards) resource of an API, specifically performing the "Post Get Cards Trash" operation. It sends a POST request to retrieve product cards that are in the trash or deleted state, allowing users to query and filter these trashed product cards.

Common scenarios for this node include:

  • Retrieving a list of deleted product cards for review or auditing.
  • Implementing workflows that handle restoration or permanent deletion of trashed product cards.
  • Synchronizing trashed product data with other systems or databases.

For example, a user might want to fetch all trashed product cards sorted by deletion date or filtered by certain criteria, then process them further in n8n.

Properties

Name Meaning
Locale Language of the response fields name, value, and object. Options: ru (Russian), en (English), zh (Chinese). Not used in sandbox mode.
Settings JSON object containing settings for the request body. Includes options for sorting (sort), pagination cursor (cursor), and filtering (filter).

Output

The node outputs JSON data representing the trashed product cards retrieved from the API. The structure of the JSON output corresponds to the API's response format for trashed product cards, including details such as card names, values, and associated metadata localized according to the selected locale.

No binary data output is indicated.

Dependencies

  • Requires an API key credential for authentication with the external API.
  • The node uses a base URL defined in a bundled Swagger/OpenAPI specification.
  • The node expects JSON-formatted input for the Settings property, which it parses and sends as the POST request body.
  • Proper configuration of the API credentials and network access to the API endpoint is necessary.

Troubleshooting

  • Invalid JSON in Settings: If the Settings property contains malformed JSON, the node will fail to parse it. Ensure valid JSON syntax.
  • Authentication Errors: Missing or invalid API credentials will cause authorization failures. Verify that the API key or token is correctly configured.
  • Locale Not Supported: Using a locale value outside the provided options (ru, en, zh) may result in unexpected responses or errors.
  • Empty or Incorrect Filters: Improperly structured filters in the Settings JSON may lead to no results or API errors. Validate filter syntax against API documentation.
  • Network Issues: Connectivity problems to the API endpoint will cause request failures. Check network settings and firewall rules.

Links and References

Discussion