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, the "Company Info" operation fetches detailed information about the connected company from the Pohoda system.

Common scenarios for this node include automating data retrieval from Pohoda for accounting or reporting purposes, synchronizing company data with other systems, or generating printable documents based on Pohoda data.

For example, a user might use the "Company Info" operation to automatically pull the latest company details into a CRM system or to verify company settings before processing invoices.

Properties

Name Meaning
XML Output If enabled (true), the output will be raw XML data as a string. If disabled (false), the output will be parsed JSON object representation of the company info.
UTF8 Conversion If enabled (true), converts the response encoding from Windows-1250 to UTF-8 for proper character display. If disabled (false), returns the original encoding.

Output

The node outputs data in the json field with two possible formats depending on the "XML Output" property:

  • If XML Output is enabled:

    • The output contains a single field data holding the full raw XML response as a string.

  • If XML Output is disabled:

    • The output contains a parsed JSON object representing the company details under the mServer key from the response structure.

No binary data is produced by the "Company Info" operation.

Dependencies

  • Requires an API authentication credential (username and password) for the Pohoda API.
  • Uses HTTP requests to communicate with the Pohoda server's /status?companyDetail endpoint.
  • Converts character encoding from Windows-1250 to UTF-8 using the iconv-lite library if UTF8 conversion is enabled.
  • Parses XML responses into JSON objects using the xmlbuilder2 library.

Troubleshooting

  • Encoding issues: If the company info contains special characters that appear garbled, ensure that "UTF8 Conversion" is enabled to properly convert Windows-1250 encoded responses.
  • Authentication errors: If the node throws authorization errors, verify that the provided API credentials are correct and have sufficient permissions.
  • API errors: If the Pohoda API returns an error state, the node will throw an error with the message from the API response note. Check the Pohoda server logs or API documentation for details on the error cause.
  • Network issues: Ensure the base URL configured in the credentials is reachable from the n8n instance and that no firewall or proxy blocks the connection.

Links and References

Discussion