Pohoda Node icon

Pohoda Node

Stormware Pohoda Integration Node

Overview

This node integrates with the Stormware Pohoda accounting system, enabling users to export various types of financial and inventory documents. Specifically for the "Příjemky" (Receipts) resource with the "Export" operation, it allows exporting receipt records from Pohoda based on customizable filters such as document ID, date ranges, company name, and other criteria.

Common scenarios include:

  • Automating data extraction of receipts for reporting or further processing.
  • Synchronizing receipt data with other systems or databases.
  • Filtering receipts by date or company to generate targeted exports.

For example, a user might export all receipts from a specific date range or those related to a particular company to analyze incoming goods or inventory intake.

Properties

Name Meaning
Filter Collection of filter options to narrow down exported receipts. Options include:
- ID: Filter by document ID
- External ID: Filter by external ID
- Date From: Filter receipts from this date (inclusive)
- Date Till: Filter receipts 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 in the export (range 1 to 10000). Default is 10.
Start Record ID Minimum record ID from which to start the export (used for pagination or incremental export).
XML Output Boolean flag indicating if the output should be raw XML string instead of parsed JSON object.
UTF8 Conversion Boolean flag to convert response encoding from Windows-1250 to UTF-8 (default true).

Output

The node outputs an array of items corresponding to the exported receipt records.

  • If XML Output is enabled, each item contains a json field with a data property holding the raw XML string response from Pohoda.
  • Otherwise, the XML response is decoded and parsed into a JSON object representing the receipt data structure.
  • Each output item corresponds to one receipt record or a batch of records depending on the request.
  • The node supports paired items, maintaining input-output mapping.
  • No binary output is produced for this export operation.

Dependencies

  • Requires an API key credential for authenticating with the Pohoda API.
  • Uses HTTP POST requests to Pohoda's XML endpoint.
  • Handles Windows-1250 encoded responses and converts them to UTF-8 if configured.
  • Depends on internal utility functions for generating XML requests (generateListRequest) and parsing XML responses.
  • Requires n8n environment to have the Pohoda API credentials configured with base URL, username, and password.

Troubleshooting

  • Authentication errors: Ensure the API key credential is correctly set with valid username and password for Pohoda.
  • Encoding issues: If the output appears garbled, verify the UTF8 Conversion option is enabled to properly decode Windows-1250 encoded responses.
  • Filter misconfiguration: Incorrect filter values (e.g., invalid dates or IDs) may result in empty exports or errors. Double-check filter inputs.
  • API limits: The Return Records Count should be within 1 to 10000; exceeding this may cause errors or truncated results.
  • Unhandled resource error: Exporting unsupported resources will throw an error stating "Not implemented for [resource]".
  • Node API errors: If Pohoda returns an error state, the node throws an error with the message from Pohoda's response note.

Links and References


This summary focuses on the "Příjemky" resource with the "Export" operation as requested, describing how to configure filters, interpret outputs, and handle common issues.

Discussion