Pohoda Node icon

Pohoda Node

Stormware Pohoda Integration Node

Actions76

Overview

This node integrates with the Pohoda accounting system, specifically enabling export operations for various data resources including "Poptávky" (Enquiries). The Export operation allows users to retrieve records from Pohoda based on filters and pagination parameters. It supports output in XML format or as parsed JSON objects.

Typical use cases include:

  • Exporting enquiry records ("Poptávky") from Pohoda for reporting or further processing.
  • Automating data synchronization between Pohoda and other systems by exporting filtered datasets.
  • Retrieving a specific range of records starting from a given record ID.

For example, a user might export the last 100 enquiries created after a certain date to analyze customer interest trends.

Properties

Name Meaning
Return Records Count (count) Number of records to return in the export; valid range is 1 to 10,000. Defaults to 10.
Start Record ID (idFrom) Minimum record ID from which to start the export. Allows partial exports starting at a specific record.
XML Output (xmlOutput) Boolean flag indicating whether to output raw XML data (true) or parsed JSON (false). Defaults to false.
UTF8 Conversion (utfConvert) 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 records:

  • If XML Output is enabled, each item contains a json field with a data property holding the raw XML string response.
  • Otherwise, the XML response is parsed into JSON objects representing the records, which are output under the json field.
  • The output items are paired with their input items for traceability.
  • No binary data output is produced for the Export operation.

Dependencies

  • Requires an API authentication credential with access 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 for generating XML requests tailored to each resource type.

Troubleshooting

  • Common issues:

    • Incorrect or missing API credentials will cause authentication failures.
    • Requesting unsupported resources or operations will throw errors.
    • Invalid filter parameters or date formats may result in empty or error responses.
    • Encoding issues if UTF8 conversion is disabled but response contains Windows-1250 characters.

  • Error messages:

    • Errors returned from Pohoda API are surfaced with the message from the response's @note attribute.
    • Node API errors indicate problems such as unsupported resource types or malformed requests.

  • Resolutions:

    • Verify API credentials and permissions.
    • Ensure filters and parameters conform to expected formats.
    • Enable UTF8 conversion unless you specifically need raw Windows-1250 encoded XML.
    • Check that the selected resource and operation combination is supported.

Links and References

Discussion