WbFinances icon

WbFinances

n8n node to interact with WB API

Actions5

Overview

This node fetches detailed supplier financial reports for a specified period from an external API. It is designed to retrieve data in chunks, allowing users to paginate through large reports by specifying a unique row ID (rrdid). This functionality is useful for financial analysis, auditing, or integrating supplier transaction data into other systems.

Typical use cases include:

  • Downloading supplier transaction details within a given date range.
  • Incrementally loading large financial reports by repeatedly calling the node with updated rrdid.
  • Automating financial reconciliation processes by integrating supplier report data.

Properties

Name Meaning
Date From The start date of the report period. Must be in RFC3339 format and can include time with precision up to milliseconds. Time is expected in Moscow timezone (UTC+3). Examples: 2019-06-20, 2019-06-20T23:59:59, 2019-06-20T00:00:00.12345.
Date To The end date of the report period. Same format requirements as "Date From".
Limit Maximum number of rows to return in one response. Cannot exceed 100,000. Defaults to 100,000.
Rrdid Unique ID of the report row used for pagination. Start with 0 to get the first chunk of the report. For subsequent calls, pass the last received rrd_id to continue fetching the next part. Continue until the response returns an empty array [], indicating no more data.

Output

The node outputs JSON data representing rows of the supplier financial report for the requested period. Each item corresponds to a detailed record from the report.

  • The output JSON array contains report rows fetched according to the specified parameters.
  • Pagination is supported via the rrdid property to fetch the report in parts.
  • No binary data output is indicated.

Dependencies

  • Requires an API key credential for authentication with the external WB API service.
  • The node uses a base URL configured from an imported OpenAPI specification.
  • Proper network access to the WB API endpoint is necessary.

Troubleshooting

  • Empty Response Early: If the response is empty on the first call, verify that the date range is correct and that there is data available for that period.
  • Pagination Issues: Ensure that rrdid starts at 0 and is updated correctly with the last received row ID to avoid missing data or infinite loops.
  • Limit Exceeded: Setting limit above 100,000 may cause errors; keep it within allowed bounds.
  • Date Format Errors: Incorrectly formatted dates may lead to request failures. Use valid RFC3339 format and Moscow timezone as specified.
  • Authentication Failures: Missing or invalid API credentials will prevent data retrieval.

Links and References

  • RFC 3339 Date/Time Format
  • Documentation for the external WB API (not provided here) should be consulted for detailed report schema and authentication setup.

Discussion