Pohoda Node icon

Pohoda Node

Stormware Pohoda Integration Node

Actions76

Overview

This node integrates with the Stormware Pohoda accounting system, enabling users to interact with various Pohoda resources and operations. Specifically, for the Prodejní ceny (Selling Prices) resource with the Company Info operation, the node fetches detailed information about the company associated with the authenticated Pohoda account.

Common scenarios where this node is beneficial include:

  • Retrieving up-to-date company details for reporting or display purposes.
  • Automating workflows that require company metadata from Pohoda.
  • Integrating Pohoda company info into other systems or dashboards.

For example, a user might use this node to automatically pull their company's contact and registration details before generating invoices or reports in an external system.

Properties

Name Meaning
XML Output If enabled (true), the node returns the raw XML response as a UTF-8 string. Otherwise, it returns parsed JSON data representing the company info.
UTF8 Conversion If enabled (true), converts the response encoding from Windows-1250 to UTF-8 for proper character representation.

Output

The output depends on the XML Output property:

  • If XML Output is true, the node outputs a single item with a json field containing:

    {
  "data": "<raw XML string of company info>"
}

    This XML string is optionally converted to UTF-8 encoding based on the UTF8 Conversion setting.

  • If XML Output is false, the node outputs a parsed JSON object under the json field representing the company information extracted from the Pohoda API response. The structure corresponds to the mServer property inside the parsed XML response pack, which typically includes company details such as name, address, identification numbers, and other metadata.

No binary data is produced by this operation.

Dependencies

  • Requires valid credentials for the Pohoda API, including:

    • Base URL of the Pohoda API endpoint.
    • Username and password for basic HTTP authentication.

  • The node uses HTTP requests with Basic Authentication headers to communicate with the Pohoda API.

  • The node depends on:

    • iconv-lite library for character encoding conversion (Windows-1250 to UTF-8).
    • xmlbuilder2 for XML parsing and conversion to JSON objects.

  • No additional environment variables are required beyond the configured Pohoda API credentials.

Troubleshooting

  • Common Issues:

    • Incorrect or missing Pohoda API credentials will cause authentication failures.
    • Network connectivity issues to the Pohoda API endpoint can result in request timeouts or errors.
    • Improper handling of character encoding may lead to garbled text if UTF8 Conversion is disabled but the response contains Windows-1250 encoded characters.

  • Error Messages:

    • If the Pohoda API response indicates a failure state (e.g., @state not "ok"), the node throws an error with the message provided by the API in the @note attribute.
    • Errors during HTTP requests or XML parsing will be surfaced as node execution errors.

  • Resolutions:

    • Verify and update the Pohoda API credentials in the node configuration.
    • Ensure network access to the Pohoda API base URL.
    • Enable UTF8 Conversion if you notice encoding issues in the output.
    • Use the XML Output option to debug raw responses when troubleshooting.

Links and References

Discussion