Pohoda Node icon

Pohoda Node

Stormware Pohoda Integration Node

Actions76

Overview

This node integrates with the Stormware Pohoda accounting system, specifically enabling export operations for various document types including internal documents ("Interní doklady"). It allows users to query and retrieve filtered lists of documents from Pohoda, supporting detailed filtering criteria such as date ranges, company names, IDs, and custom filters. The node can output data either as parsed JSON or raw XML, optionally converting character encoding.

Typical use cases include:

  • Exporting internal company documents for reporting or further processing.
  • Automating data synchronization between Pohoda and other systems.
  • Extracting filtered subsets of accounting or inventory documents based on specific criteria.

For example, a user might export all internal documents modified since a certain date or belonging to a particular company, then process this data downstream in an n8n workflow.

Properties

Name Meaning
Filter Collection of filter options to narrow down exported documents. Options include:
- ID: Filter by document ID
- External ID: Filter by external document ID
- Date From: Filter documents from this date (inclusive)
- Date Till: Filter documents up to this date (inclusive)
- Last Changes: Filter by last modification date
- Company Name: Filter by company name
- User Custom Filter Name: Apply a custom Pohoda filter
- IČO: Filter by company registration number
Return Records Count Number of records to return, range 1 to 10000 (default 10)
Start Record ID Minimum record ID from which to start exporting
XML Output Boolean flag to output raw XML response instead of parsed JSON
UTF8 Conversion Boolean flag to convert Windows-1250 encoded response to UTF-8

Output

The node outputs an array of items corresponding to the exported documents matching the filter criteria.

  • If XML Output is enabled, the output contains a single item with a json field holding the raw XML string under data.
  • Otherwise, the XML response is parsed into JSON objects representing the documents, each emitted as a separate item.
  • In case of print operations (not relevant here), binary PDF data may be output, but for export operation on internal documents, output is JSON or XML only.

Each JSON item corresponds to one document or a list of documents depending on the response structure.

Dependencies

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

Troubleshooting

  • Authentication errors: Ensure valid Pohoda API credentials are provided; incorrect username/password will cause authorization failures.
  • Invalid filter parameters: Dates must be in ISO format; invalid or unsupported filter fields may cause API errors.
  • Encoding issues: If response characters appear garbled, verify UTF8 Conversion setting; disable if your environment expects Windows-1250 encoding.
  • API errors: The node throws errors if Pohoda responds with non-"ok" states; check the error message returned by Pohoda for details.
  • Not implemented resource: Using resources not supported by the export operation will throw an error indicating "Not implemented for [resource]".

Links and References

Discussion