Pohoda Node

Overview

This node integrates with the Stormware Pohoda accounting system, specifically supporting operations such as exporting data, creating entities, retrieving company info, and printing reports or documents. The "Print" operation for the "Banka" resource allows users to generate and print bank-related reports or documents from Pohoda, saving them as files (e.g., PDF) and optionally deleting the file after printing.

Common scenarios include:

• Automatically generating bank transaction reports or statements for accounting purposes.
• Printing specific bank documents identified by record and report IDs.
• Exporting bank data for further processing or archival.

Practical example:
A user wants to print a bank statement report for a particular transaction record. They provide the record ID, report ID, and specify the output filename. The node sends a request to Pohoda, receives the generated PDF, outputs it as binary data, and optionally deletes the temporary file after printing.

Properties

Output

The node outputs JSON and/or binary data depending on the settings:

• If XML Output is enabled, the node returns the raw XML response from Pohoda in the json.data field.
• Otherwise, for the "print" operation, the node returns the print details in JSON format under json, and includes the generated document as binary data under binary.data. This binary data contains:
  • data: The PDF file content.
  • mimeType: "application/pdf".
  • fileExtension: "pdf".
  • fileName: The original filename of the attachment.

This allows downstream nodes to access the printed document directly for storage, emailing, or further processing.

Dependencies

• Requires an API authentication credential with Pohoda (Stormware) that provides:
  • Base URL for the Pohoda API.
  • Username and password for Basic Authentication.
• Uses HTTP POST requests to Pohoda's /xml endpoint for commands.
• Uses external libraries for XML building/parsing and character encoding conversion.
• n8n environment must have this credential configured and accessible.

Troubleshooting

• Authentication errors: Ensure the API credentials are correct and have sufficient permissions.
• Invalid report or record IDs: Verify that the provided recordId and reportId exist in Pohoda and are valid for the selected resource.
• Encoding issues: If the output appears garbled, try toggling the UTF8 Conversion property.
• File handling errors: If the file cannot be deleted after printing, check file system permissions or disable the delete option.
• API errors: The node throws errors if Pohoda responds with a non-"ok" state, including messages from Pohoda's response note. Review these messages for hints on misconfiguration or invalid parameters.

Links and References

• Stormware Pohoda API Documentation
• n8n HTTP Request Node Documentation
• XMLBuilder2 Library