WbReports icon

WbReports

n8n node to interact with WB API

Actions26

Overview

This node interacts with a reporting API to retrieve analytics data specifically about goods returns and movements. The "Get Analytics Goods Return" operation fetches detailed reports on product returns within a specified date range. This is useful for businesses that want to analyze return trends, identify problematic products, or monitor inventory adjustments due to returns.

Practical examples:

  • A retail manager wants to see how many items were returned between August 13 and August 27, 2024, to assess customer satisfaction.
  • An inventory analyst uses the report to track product movement and returns to optimize stock levels.

Properties

Name Meaning
Date From Start date of the reporting period (format: YYYY-MM-DD)
Date To End date of the reporting period (format: YYYY-MM-DD)

Both properties are required and define the time window for which the goods return analytics report will be generated.

Output

The node outputs JSON data containing the analytics report for goods returns within the specified date range. The structure typically includes details such as returned product identifiers, quantities, dates, and possibly reasons or categories of returns depending on the underlying API response.

If binary data output is supported by the node (not evident from the provided code), it would likely represent downloadable report files (e.g., CSV or Excel), but this is not explicitly indicated here.

Dependencies

  • Requires an API key credential to authenticate requests to the external reporting API.
  • The node depends on a base URL and OpenAPI specification loaded from bundled JSON (11-reports_modified.json).
  • Uses an internal helper library for building request properties and handling API calls.
  • No additional environment variables are explicitly required beyond standard API authentication.

Troubleshooting

  • Missing or invalid date parameters: Ensure both "Date From" and "Date To" are provided in the correct format (YYYY-MM-DD). Invalid dates may cause API errors.
  • Authentication failures: Verify that the API key credential is correctly configured and has sufficient permissions.
  • Empty or unexpected responses: Confirm that the date range actually contains data; some periods may have no returns.
  • Network or connectivity issues: Check internet connection and API endpoint availability.

Common error messages might include HTTP 401 Unauthorized (authentication issue), 400 Bad Request (invalid parameters), or 500 Internal Server Error (server-side problem). Resolving these involves checking credentials, input values, and retrying later if the server is down.

Links and References

Discussion