Pohoda Node icon

Pohoda Node

Stormware Pohoda Integration Node

Actions76

Overview

This node integrates with the Pohoda accounting system, specifically supporting operations such as exporting data, creating entities, retrieving company info, and printing reports. The "Print" operation for the "Nabídky" (Offers) resource allows users to generate and print offer reports from Pohoda by specifying the record ID and report template. This is useful in scenarios where automated generation and printing of official offer documents are needed, such as sending offers to customers or archiving printed copies.

Practical examples:

  • Automatically print an offer document for a specific offer record stored in Pohoda.
  • Generate PDF files of offer reports and optionally delete them after printing.
  • Retrieve the printed report as XML output for further processing or storage.

Properties

Name Meaning
ID záznamu Item Row ID — the identifier of the specific offer record to print.
ID sestavy Report ID — identifier of the report template to use for printing; found in report properties.
Název/cesta k souboru File name/path — path and filename where the generated print file (e.g., PDF) will be saved.
XML Output Boolean flag to return the raw XML response instead of parsed data or PDF binary.
UTF8 Conversion Boolean flag to convert the response encoding from Windows-1250 to UTF-8.
Delete File After Print Boolean flag indicating whether to delete the generated file after printing.

Output

The node outputs JSON and optionally 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, if the print response contains PDF attachments, it outputs:
    • JSON metadata about the print details.
    • Binary data containing the PDF file (data), with MIME type application/pdf, file extension .pdf, and the original file name.
  • If no PDF attachment is present, it outputs parsed JSON objects representing the print response details.

Dependencies

  • Requires connection credentials to Pohoda API (an API key credential with username, password, and base URL).
  • Uses HTTP requests with Basic Authentication to communicate with Pohoda's XML API endpoint.
  • Uses external libraries for XML building/parsing and character encoding conversion.
  • No additional environment variables are required beyond the configured credentials.

Troubleshooting

  • Common issues:

    • Incorrect or missing report ID may cause the print request to fail.
    • Invalid record ID or non-existent offer record will result in errors from Pohoda.
    • Encoding issues if UTF8 conversion is disabled but the response contains Windows-1250 encoded characters.
    • Network or authentication failures due to incorrect credentials or unreachable Pohoda API endpoint.

  • Error messages:

    • Errors returned from Pohoda API are surfaced with messages from the response's @note attribute.
    • Node API errors indicate problems with the request or response validation.
    • To resolve, verify credentials, ensure correct report and record IDs, and check network connectivity.

Links and References

Discussion