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 "Pokladní doklady" (Cash register documents). The Export operation allows users to retrieve filtered lists of documents from Pohoda based on criteria such as date ranges, IDs, company names, and custom filters.

Typical use cases include:

  • Automating data extraction of cash register documents for reporting or further processing.
  • Synchronizing Pohoda financial records with other systems.
  • Filtering and exporting specific subsets of documents by date or company details.

For example, a user can export all cash register documents created after a certain date or filter by a specific external ID to retrieve targeted records.

Properties

Name Meaning
Filter Collection of optional filters 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 documents changed since this 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 specifying how many records to return (range 1 to 10000). Defaults to 10.
Start Record ID Minimum record ID from which to start the export (used for pagination or incremental exports).
XML Output Boolean flag indicating if the output should be raw XML instead of parsed JSON. Defaults to false.
UTF8 Conversion Boolean flag to convert response encoding from Windows-1250 to UTF-8. Defaults to true.

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 JSON field data with the raw XML string returned by Pohoda.
  • Otherwise, the XML response is parsed into JSON objects representing the documents.
  • Each item in the output corresponds to one document or entity retrieved.
  • The node supports paired item output, preserving input-output mapping.
  • Binary output is not used for this export operation.

Dependencies

  • Requires connection credentials to the Pohoda API, including base URL, username, and password.
  • Uses HTTP POST requests with Basic Authentication to communicate with Pohoda's XML API endpoint.
  • Depends on internal utilities for generating XML requests and parsing XML responses.
  • Uses character encoding conversion from Windows-1250 to UTF-8 when needed.

Troubleshooting

  • Authentication errors: Ensure valid API credentials are configured; invalid username/password will cause authorization failures.
  • Invalid filter parameters: Incorrect date formats or unsupported filter fields may cause API errors.
  • Response state not OK: The node checks the response status and throws errors if Pohoda returns a non-ok state with a message.
  • Encoding issues: If UTF8 conversion is disabled but the response contains Windows-1250 encoding, output may be garbled.
  • Not implemented resource: Using resources or operations not supported by the node will throw an error indicating lack of implementation.

To resolve errors:

  • Verify credentials and network connectivity.
  • Use correct filter formats (dates in ISO format).
  • Enable UTF8 conversion unless you specifically need raw Windows-1250 encoded XML.
  • Check the Pohoda API documentation for valid request parameters.

Links and References

Discussion