WbCommunication

Overview

This node interacts with the Wildberries (WB) API to retrieve a specific seller download file by its unique identifier. It is useful in scenarios where you need to programmatically access files related to chat communications with customers, such as downloading reports or data exports linked to seller interactions.

A practical example would be automating the retrieval of chat-related files for further processing or archival without manual intervention.

Properties

Output

The node outputs JSON data representing the content or metadata of the requested seller download file. The exact structure depends on the file retrieved but generally includes details about the downloaded resource.

If the file contains binary data (e.g., documents or media), the node will provide this in a binary format suitable for further use within n8n workflows.

Dependencies

• Requires an API key credential for authenticating with the Wildberries API.
• The node uses the WB API base URL configured internally based on the bundled OpenAPI specification.
• No additional external dependencies are needed beyond the API authentication.

Troubleshooting

• Missing or invalid Id: If the Id property is empty or incorrect, the node will fail to retrieve the file. Ensure the Id matches a valid downloadID from the chat events.
• Authentication errors: Without proper API credentials, requests will be rejected. Verify that the API key is correctly set up and has sufficient permissions.
• Network issues: Connectivity problems can cause request failures. Check network access to the WB API endpoint.
• File not found: If the specified Id does not correspond to any available download, the node may return an error or empty response.

Links and References

• Wildberries API Documentation (general reference)
• Related method for obtaining downloadID: "Chat Events" endpoint in the Wildberries API documentation.