WbCommunication icon

WbCommunication

n8n node to interact with WB API

Overview

This node operation retrieves the count of feedback entries within a specified date range from a service (likely Wildberries, based on context). It allows filtering feedback by whether they have been answered or not. This is useful for monitoring customer feedback volume over time and managing response workflows.

Practical examples:

  • A customer support manager wants to see how many new feedbacks arrived last week to allocate resources accordingly.
  • An analyst tracks the number of unanswered feedbacks daily to ensure timely responses.

Properties

Name Meaning
Date From Start date of the period as a Unix timestamp to filter feedbacks from this date onward.
Date To End date of the period as a Unix timestamp to filter feedbacks up to this date.
Is Answered Filter feedbacks by their answered status: true for processed feedbacks, false for unprocessed. Defaults to false.

Output

The node outputs JSON data containing the count of feedbacks matching the specified criteria (date range and answered status). The exact structure is not shown in the source, but typically it would be an object with a numeric field representing the count.

No binary data output is indicated.

Dependencies

  • Requires an API key credential to authenticate requests to the external feedback service.
  • Uses a base URL configured from an imported Swagger/OpenAPI specification.
  • The node sends query parameters (dateFrom, dateTo, isAnswered) to the API endpoint.

Troubleshooting

  • Common issues:

    • Incorrect date format: Ensure Date From and Date To are valid Unix timestamps.
    • Missing or invalid API credentials can cause authentication errors.
    • If no feedbacks match the filters, the count may be zero; verify filter values if unexpected.
  • Error messages:

    • Authentication failures usually indicate missing or incorrect API keys.
    • Validation errors may occur if date parameters are out of expected range or improperly formatted.
    • Network or server errors should be checked by verifying connectivity and API availability.

Links and References

Discussion