WbReports icon

WbReports

n8n node to interact with WB API

Actions26

Overview

This node interacts with the "Основные Отчёты" (Main Reports) resource of an API to retrieve supplier order data. Specifically, the "Get Supplier Orders" operation fetches orders based on their last modification date or by exact order date. This is useful for automating workflows that require up-to-date supplier order information, such as inventory management, order reconciliation, or sales analysis.

Practical examples include:

  • Automatically pulling all supplier orders updated since a certain date/time to sync with an internal database.
  • Extracting all orders made on a specific day for daily reporting or auditing purposes.

Properties

Name Meaning
Date From The starting point date and time for filtering orders by their last change date. Accepts RFC3339 format dates or date-times in Moscow timezone (UTC+3). Time precision can be up to seconds or milliseconds. Examples: 2019-06-20, 2019-06-20T23:59:59, 2019-06-20T00:00:00.12345. This property is required.
Flag Controls how the date filter is applied:
- 0 (default or omitted): Returns orders whose last change date is greater than or equal to the Date From value. The number of returned records can vary widely (up to ~100,000).
- 1: Returns all orders exactly matching the date part of Date From (time ignored). The number of returned records equals all orders on that date.

Output

The node outputs JSON data representing supplier orders retrieved from the API. Each item in the output corresponds to a single supplier order with its associated details as provided by the API response.

If binary data were involved (e.g., files or attachments), it would be summarized here, but this node focuses on JSON data only.

Dependencies

  • Requires an API key credential for authentication with the external service providing the "Основные Отчёты" data.
  • The node uses a base URL configured from an imported OpenAPI specification.
  • No additional environment variables are explicitly required beyond standard API authentication setup.

Troubleshooting

  • Invalid Date Format: If the Date From property is not in valid RFC3339 format or does not respect the Moscow timezone requirement, the API may reject the request or return no data. Ensure correct formatting.
  • Large Data Volumes: Using flag=0 with a very old Date From might result in large datasets (~100,000 records), which could cause performance issues or timeouts. Consider narrowing the date range or using flag=1 for exact date queries.
  • Authentication Errors: Missing or invalid API credentials will prevent successful data retrieval. Verify that the API key or token is correctly configured.
  • Empty Results: If no orders match the criteria, the output will be empty. Double-check the date filters and flag settings.

Links and References

  • RFC3339 Date/Time Format
  • API documentation section on date filtering and flags (referenced internally in the node's description but not linked externally here)

Discussion