Pohoda Node icon

Pohoda Node

Stormware Pohoda Integration Node

Actions76

Overview

This node integrates with the Stormware Pohoda accounting system, enabling users to perform various operations such as exporting data, creating entities, printing reports, and retrieving company information. Specifically, for the Zásoby (Stock) resource with the Company Info operation, the node fetches detailed company information from the Pohoda system.

Common scenarios where this node is beneficial include automating data synchronization between Pohoda and other systems, generating reports, or extracting company metadata for further processing or display in workflows.

For example, a user might use this node to:

  • Retrieve up-to-date company details to populate CRM records.
  • Export stock or invoice data for external analysis.
  • Automate printing of documents based on Pohoda data.

Properties

Name Meaning
XML Output If enabled (true), the node returns the raw XML response from Pohoda instead of parsed JSON.
UTF8 Conversion If enabled (true), converts the response encoding from Windows-1250 to UTF-8 for proper character representation.

These properties control the format and encoding of the output when fetching company info.

Output

The node outputs data in the following ways depending on the XML Output property:

  • If XML Output is false (default), the node parses the XML response into a JSON object representing the company details under the mServer key. This JSON contains structured company information such as name, address, identification numbers, and other metadata.

  • If XML Output is true, the node outputs the raw XML string received from the Pohoda API in the data field of the JSON output.

The output is paired with the input item index for traceability.

No binary data is produced for the Company Info operation.

Dependencies

  • Requires an API authentication credential with username, password, and base URL for the Pohoda API.
  • Uses HTTP requests with Basic Authentication to communicate with the Pohoda server.
  • Depends on external libraries for XML parsing and encoding conversion:
    • iconv-lite for character encoding conversion.
    • xmlbuilder2 for XML to JSON conversion.
  • The node expects the Pohoda API to be accessible at the configured base URL.

Troubleshooting

  • Encoding issues: If the response contains garbled characters, ensure that the UTF8 Conversion property is enabled to convert from Windows-1250 encoding properly.

  • Authentication errors: If the node throws authorization errors, verify that the API credentials are correct and have sufficient permissions.

  • Unexpected response state: The node checks the response state flags; if the Pohoda API returns a non-"ok" state, the node throws an error with the message from the API note. This usually indicates invalid requests or server-side issues.

  • Network errors: Ensure the Pohoda API endpoint is reachable from the n8n environment.

  • Not implemented errors: For resources or operations not supported by the node, it will throw a "Not implemented" error. Confirm that the selected resource and operation are valid.

Links and References

Discussion