WbCommunication icon

WbCommunication

n8n node to interact with WB API

Actions20

Overview

This node interacts with the Wildberries (WB) API to retrieve customer return claims. Specifically, the "Get Claims" operation under the "Возвраты Покупателями" (Customer Returns) resource fetches information about product return requests made by customers. This is useful for e-commerce sellers or warehouse managers who want to monitor and manage return claims efficiently.

Practical examples include:

  • Automatically fetching recent return claims to update internal order management systems.
  • Filtering claims based on their status (archived or under review).
  • Paginating through large sets of claims using limit and offset parameters.

Properties

Name Meaning
Is Archive The state of the claim: false means the claim is under review; true means it is archived.
Id The unique identifier (UUID) of a specific claim to retrieve.
Limit Number of claims to return in the response. Default is 50.
Offset The starting point after which to return claims (for pagination). Default is 0.
Nm Id The WB article number (product SKU) to filter claims related to a specific product.

Output

The node outputs JSON data representing the claims retrieved from the WB API. Each item in the output corresponds to a customer return claim, including details such as claim ID, status, product information, and timestamps.

If binary data were involved (e.g., documents or images related to claims), it would be summarized here, but this node focuses on JSON claim data only.

Dependencies

  • Requires an API key credential for authenticating with the Wildberries API.
  • The node uses a base URL and OpenAPI specification bundled internally to construct requests.
  • No additional external dependencies are indicated beyond standard HTTP request capabilities.

Troubleshooting

  • Common issues:
    • Incorrect or missing API authentication token may cause authorization errors.
    • Providing invalid UUIDs or non-existent claim IDs will result in empty or error responses.
    • Pagination parameters (limit and offset) must be within valid ranges; otherwise, the API might return errors or no data.
  • Error messages:
    • Authorization failures typically indicate problems with the API key setup.
    • Validation errors may occur if required parameters like is_archive are omitted.
    • Network or timeout errors could happen if the WB API is unreachable.

To resolve these:

  • Ensure the API key credential is correctly configured in n8n.
  • Validate input parameters before execution.
  • Check network connectivity and WB API status.

Links and References

  • Wildberries API documentation (official, if available)
  • n8n documentation on creating and configuring API nodes
  • General REST API best practices for pagination and filtering

Discussion