Pohoda Node icon

Pohoda Node

Stormware Pohoda Integration Node

Overview

This node integrates with the Stormware Pohoda accounting system, enabling users to interact with various Pohoda resources and operations. Specifically, for the Výroba (Production) resource and the Company Info operation, it fetches detailed information about the company registered in the Pohoda system.

Common scenarios where this node is beneficial include:

  • Retrieving up-to-date company details for reporting or automation workflows.
  • Integrating Pohoda company data into other systems or dashboards.
  • Automating checks or validations based on company metadata.

For example, a user might use this node to automatically pull company info before generating invoices or reports, ensuring that all documents reflect the latest company data.

Properties

Name Meaning
XML Output If enabled (true), the node returns the raw XML response from Pohoda as a string.
UTF8 Conversion If enabled (true), converts the response encoding from Windows-1250 to UTF-8 format.

Output

The output depends on the XML Output property:

  • If XML Output is false (default), the node parses the XML response into a JSON object and outputs the company information under the mServer key of the parsed response. This JSON contains structured company details as provided by Pohoda.

  • If XML Output is true, the node outputs the raw XML response as a UTF-8 string in the data field inside the json output.

No binary data output is produced for the Company Info operation.

Example JSON output when XML Output is false (simplified):

{
  "mServer": {
    "companyName": "Example Company",
    "ico": "12345678",
    "address": {
      "city": "Prague",
      "street": "Main Street 1"
    },
    ...
  }
}

Example JSON output when XML Output is true:

{
  "data": "<?xml version=\"1.0\" encoding=\"utf-8\"?><rsp:responsePack ... >...</rsp:responsePack>"
}

Dependencies

  • Requires an API authentication credential with access to the Pohoda API.
  • The node makes HTTP requests to the Pohoda API base URL configured in the credentials.
  • Uses external libraries for XML building/parsing and character encoding conversion.
  • The node expects the Pohoda API to respond with XML encoded in Windows-1250 charset, which it optionally converts to UTF-8.

Troubleshooting

  • Encoding issues: If the output appears garbled, ensure the UTF8 Conversion property is enabled to convert Windows-1250 encoded responses properly.
  • Authentication errors: If the node throws authorization errors, verify that the API credentials (username and password) are correct and have sufficient permissions.
  • API errors: The node throws errors if the Pohoda API response state is not "ok". Check the error message returned by the API for details.
  • Network issues: Ensure the Pohoda API base URL is reachable from the n8n environment.
  • Unexpected response structure: If the node fails parsing the response, confirm that the Pohoda API version and endpoint have not changed.

Links and References

Discussion