Pohoda Node icon

Pohoda Node

Stormware Pohoda Integration Node

Overview

This node integrates with the Stormware Pohoda accounting system, enabling users to perform various operations such as exporting data, creating entities, printing documents, and retrieving company information. Specifically, for the Prodejky resource under the Company Info operation, the node fetches detailed information about the company associated with the connected Pohoda account.

Typical use cases include:

  • Retrieving up-to-date company details for reporting or verification.
  • Automating workflows that require company metadata from Pohoda.
  • Integrating company info into other systems or processes without manual lookup.

For example, a user might use this node to automatically pull their company's registered address, tax ID, and contact details from Pohoda to populate an internal CRM or generate compliance reports.

Properties

Name Meaning
XML Output When enabled (true), returns the raw XML response from Pohoda as a string in the output. When disabled (false), returns parsed JSON object representation of the company info.
UTF8 Conversion When enabled (true), converts the response encoding from Windows-1250 to UTF-8 for proper character display. Disable if you want the original encoding preserved.

Output

The node outputs data in the json field with the following structure depending on the XML Output property:

  • If XML Output is true:

    • The output contains a single field data holding the full raw XML response as a UTF-8 string (if UTF8 Conversion is enabled) or as originally encoded otherwise.
  • If XML Output is false:

    • The output contains a parsed JSON object representing the company information under the key mServer. This object includes all relevant company details returned by Pohoda's API in a structured format.

No binary data is produced for the Company Info operation.

Dependencies

  • Requires valid credentials for the Pohoda API, including base URL, username, and password.
  • Uses HTTP Basic Authentication to communicate with the Pohoda API endpoints.
  • 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

  • Authentication errors:
    If the node fails with authorization errors, verify that the provided API credentials (username and password) are correct and have sufficient permissions.

  • Encoding issues:
    If special characters appear garbled, ensure the UTF8 Conversion option is enabled to convert from Windows-1250 encoding to UTF-8.

  • API response errors:
    The node throws errors if the Pohoda API response indicates failure (e.g., state not "ok"). Check the error message returned by the API for details.

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

  • Unexpected output format:
    If the output JSON structure does not match expectations, try toggling the XML Output option to get either raw XML or parsed JSON.

Links and References

Discussion