WbCommunication icon

WbCommunication

n8n node to interact with WB API

Actions20

Overview

This node is designed to retrieve product feedback (Отзывы) from a marketplace or e-commerce platform. Specifically, the "Get Feedbacks" operation fetches customer reviews based on various filtering and sorting criteria such as whether the feedback has been answered, product identifier, date range, and pagination controls.

Common scenarios where this node is useful include:

  • Monitoring customer satisfaction by fetching recent or historical product reviews.
  • Automating responses or analysis of answered vs unanswered feedback.
  • Integrating feedback data into dashboards or CRM systems for further processing.

For example, a user might configure the node to get the latest 100 unanswered reviews for a specific product to prioritize customer support efforts.

Properties

Name Meaning
Is Answered Filter feedback by whether it has been processed (true) or not (false).
Nm Id The product article number (SKU) to filter feedback for a specific item.
Take Number of feedback entries to retrieve (maximum 5,000).
Skip Number of feedback entries to skip (for pagination, max 199,990).
Order Sort order of feedback by date: either ascending (dateAsc) or descending (dateDesc).
Date From Start date of the period to fetch feedback, specified as a Unix timestamp.
Date To End date of the period to fetch feedback, specified as a Unix timestamp.

Output

The node outputs JSON data containing the retrieved feedback entries. Each entry typically includes details such as the feedback content, date, whether it was answered, and associated product information.

If the node supports binary data output (not indicated in the provided code), it would be summarized as representing any attached media or files related to the feedback.

Dependencies

  • Requires an API key credential to authenticate requests to the external service providing the feedback data.
  • The node uses a base URL configured from an imported Swagger/OpenAPI specification.
  • No additional environment variables are explicitly required beyond standard API authentication.

Troubleshooting

  • Common issues:

    • Exceeding the maximum allowed take or skip values may cause errors or truncated results.
    • Incorrect Unix timestamps for dateFrom or dateTo can result in empty or unexpected data sets.
    • Missing or invalid API credentials will prevent successful data retrieval.

  • Error messages:

    • Authentication failures usually indicate missing or incorrect API keys; verify credentials.
    • Validation errors may occur if required parameters like isAnswered, take, or skip are omitted or out of range.
    • Network or timeout errors suggest connectivity issues with the external API endpoint.

Links and References

  • Unix Timestamp Converter – Useful for converting human-readable dates to Unix timestamps.
  • Documentation for the external API (not provided here) should be consulted for detailed parameter descriptions and limits.

Discussion