Pohoda Node icon

Pohoda Node

Stormware Pohoda Integration Node

Actions76

Overview

This node integrates with the Pohoda accounting system, specifically supporting various operations such as exporting data, creating entities, retrieving company info, and printing reports. The "Print" operation for the "Zakázky" (Contracts) resource allows users to generate and print a specific report based on a record ID and report ID, saving the output as a PDF file.

Common scenarios include:

  • Automatically generating contract reports in PDF format for archival or distribution.
  • Printing specific documents from Pohoda directly within an automated workflow.
  • Exporting data or creating new records in Pohoda via other supported operations.

Example use case:
You have a contract record in Pohoda identified by its row ID and want to generate a printable report of that contract. You configure this node to "Print" the "Zakázky" resource, specify the record ID and report ID, and provide a filename. The node then requests the report from Pohoda, saves it as a PDF, and optionally deletes the file after printing.

Properties

Name Meaning
ID záznamu Item Row ID — the identifier of the specific record (contract) to print.
ID sestavy Report ID — identifier of the report template to use; found in the report's properties.
Název/cesta k souboru File name/path — where the generated PDF report will be saved (default: "n8n.pdf").
XML Output Boolean flag to return raw XML response instead of parsed data (false by default).
UTF8 Conversion Boolean flag to convert Windows-1250 encoded response to UTF-8 (true by default).
Delete File After Print Boolean flag indicating whether to delete the saved file after printing (true by default).

Output

The node outputs JSON and binary data depending on the configuration:

  • 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:
    • A JSON object containing print details metadata.
    • A binary field named data containing the PDF file content (application/pdf MIME type), including file extension and filename.

This allows subsequent nodes to access the PDF file directly for further processing, storage, or sending.

Dependencies

  • Requires an API authentication credential to connect to the Pohoda system.
  • Uses HTTP POST requests to Pohoda's XML API endpoint.
  • Handles character encoding conversion from Windows-1250 to UTF-8 if enabled.
  • Relies on internal utility functions to generate XML requests for printing.

Troubleshooting

  • Authentication errors: Ensure the API credentials are correct and have sufficient permissions.
  • Invalid report or record IDs: Verify that the provided record ID and report ID exist in Pohoda; otherwise, the node will throw an error with the message returned by Pohoda.
  • Encoding issues: If the output contains garbled characters, try toggling the UTF8 Conversion property.
  • File handling: If the file is deleted before you can use it, disable the "Delete File After Print" option.
  • Unexpected response structure: The node expects a specific XML response format; changes in Pohoda's API may cause parsing errors.

Links and References

Discussion