WbFinances icon

WbFinances

n8n node to interact with WB API

Actions5

Overview

This node operation "Get Documents Download" under the resource "Документы" is designed to retrieve downloadable documents from a service by specifying a unique document ID and desired file format. It is useful in scenarios where users need to programmatically fetch archived or generated documents, such as reports, notifications, or data exports, directly into their workflows.

For example, a user might want to download a zipped notification document identified by a unique service name ID for further processing or storage.

Properties

Name Meaning
Service Name Unique identifier of the document to be downloaded. Example: redeem-notification-44841941
Extension Format of the document to download. Supported value example: zip

Output

The node outputs the downloaded document content. Since the document is requested with a specified extension (e.g., zip), the output will typically be binary data representing the file content. This allows subsequent nodes to save, process, or transmit the document as needed.

The JSON output field will contain metadata about the request or response, but the main payload is expected to be binary data corresponding to the downloaded document.

Dependencies

  • Requires an API key credential or authentication token configured in n8n to access the external document service.
  • The base URL and endpoint details are derived from an OpenAPI specification bundled with the node.
  • The node sends HTTP requests with query parameters serviceName and extension to fetch the document.

Troubleshooting

  • Common issues:
    • Invalid or missing Service Name may result in errors or empty responses.
    • Unsupported or incorrect Extension values could cause the service to reject the request or return unexpected formats.
    • Authentication failures if the API key or credentials are not properly set up.
  • Error messages:
    • "Document not found" or similar indicates the Service Name does not match any available document.
    • "Unauthorized" or "Authentication failed" suggests issues with API credentials.
  • Resolutions:
    • Verify the exact document ID and ensure it exists.
    • Confirm supported file extensions with the service documentation.
    • Check that API credentials are correctly configured in n8n.

Links and References

  • Refer to the external document service API documentation for details on valid document IDs and supported formats.
  • n8n documentation on managing credentials and HTTP request nodes for additional context on authentication setup.

Discussion