Pohoda Node icon

Pohoda Node

Stormware Pohoda Integration Node

Overview

The 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 Zakázky (Contracts) resource with the Company Info operation, the node fetches detailed information about the company associated with the authenticated Pohoda account.

This node is beneficial in scenarios where automated access to accounting or contract-related data is needed within workflows, such as synchronizing company details into CRM systems, generating reports, or validating company information before processing contracts.

Example use cases:

  • Automatically retrieve and update company info from Pohoda in a business management system.
  • Use company details to enrich contract records or invoices.
  • Validate company status or metadata before proceeding with further automation steps.

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 and outputs a JSON object under the json field containing the mServer property, which holds the structured company information extracted from the Pohoda API response.

  • If XML Output is true, the node outputs the raw XML response string under the json.data field without parsing.

No binary data output is produced by this operation.

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 XML parsing libraries internally to convert responses from XML to JSON.
  • Handles character encoding conversion from Windows-1250 to UTF-8 if enabled.

Troubleshooting

  • Common issues:

    • Authentication failures due to incorrect or missing API credentials.
    • Encoding problems if UTF8 conversion is disabled but the response contains Windows-1250 encoded characters.
    • API errors returned by Pohoda indicated by non-"ok" states in the response, causing the node to throw errors with messages from the API.
  • Error messages:

    • Errors with messages derived from the Pohoda API's @note attribute indicate specific issues reported by the service (e.g., invalid request, permission denied).
    • Network or HTTP errors during the request will be surfaced by the node's error handling.
  • Resolutions:

    • Verify API credentials and permissions.
    • Enable UTF8 conversion if you see garbled characters in the output.
    • Check the Pohoda API documentation or support for error message meanings.

Links and References

Discussion