Pohoda Node

Overview

This node integrates with the Pohoda accounting system, specifically supporting operations on various resources including "Adresy" (Addresses). The Print operation for the "Adresy" resource allows users to generate and print reports based on specific address book records. This is useful in scenarios where you need to produce printable documents or reports from your address data stored in Pohoda, such as contact lists or address summaries.

Practical examples:

• Printing a detailed report of a single address book entry by specifying its record ID and a report template.
• Generating a PDF file of an address report and optionally deleting the file after printing.
• Exporting the report either as raw XML output or as a PDF binary file.

Properties

Output

The node outputs JSON data and may also output binary data depending on the operation and settings:

• For the Print operation on "Adresy":
  • If xmlOutput is enabled, the node returns the raw XML response as a string in the json.data field.
  • Otherwise, if the response contains printable PDF data, it outputs a binary file under binary.data with:
    • data: The PDF file content (base64 encoded).
    • mimeType: "application/pdf".
    • fileExtension: "pdf".
    • fileName: The original filename from the response.
  • Additionally, JSON fields contain print details metadata extracted from the response.

Dependencies

• Requires an API key credential for authenticating with the Pohoda API.
• Uses HTTP POST requests to Pohoda's /xml endpoint for sending XML requests.
• Uses external libraries for XML building/parsing and character encoding conversion.
• The node expects the Pohoda API base URL and credentials to be configured in n8n credentials.

Troubleshooting

• Common issues:

  • Incorrect or missing API credentials will cause authentication failures.
  • Invalid recordId or reportId values may result in errors from the Pohoda API indicating missing or invalid data.
  • File write permissions or invalid fileName paths can cause failures when saving the generated report.
  • Encoding issues if utfConvert is disabled but the response contains Windows-1250 encoded characters.

• Error messages:

  • Errors returned from the Pohoda API are surfaced with messages from the response's @note attribute.
  • Node API errors occur if the response state is not "ok".
  • To resolve, verify credentials, ensure correct IDs, and check file path validity.

Links and References

• Pohoda API Documentation (official developer resources)
• n8n HTTP Request Node Documentation (for understanding HTTP request usage)
• iconv-lite npm package (used for character encoding conversions)

This summary focuses on the "Adresy" resource and the "Print" operation as requested, describing the input parameters, output structure, dependencies, and potential troubleshooting points based on static analysis of the provided source code and property definitions.