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, for the "Pokladní doklady" (Cash Register Documents) resource and the "Company Info" operation, the node fetches detailed company information from the Pohoda system.

Common scenarios where this node is beneficial include automating data synchronization between Pohoda and other systems, generating financial reports, or retrieving up-to-date company details for use in workflows. For example, a user might automate fetching company info to verify business details before processing invoices or payments.

Properties

Name Meaning
XML Output If true, returns the raw XML response as a string; if false, returns parsed JSON object.
UTF8 Conversion If true, converts the response encoding from Windows-1250 to UTF-8 for proper text display.

Output

The output depends on the "XML Output" property:

  • If XML Output is true, the node outputs a JSON object with a single field data containing the raw XML response as a UTF-8 string.
  • If XML Output is false, the node outputs a JSON object representing the parsed company information extracted from the XML response under the mServer property of the response pack.

The output is paired with the input item index for traceability.

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

Dependencies

  • Requires an API authentication credential with username and password to access the Pohoda API.
  • The node makes HTTP requests to the Pohoda API base URL provided in credentials.
  • Uses external libraries for XML building/parsing and character encoding conversion.
  • Requires n8n environment configured with the appropriate API credentials.

Troubleshooting

  • Authentication errors: Ensure the API credentials (username and password) are correct and have sufficient permissions.
  • Encoding issues: If the response contains garbled characters, try toggling the "UTF8 Conversion" property.
  • API endpoint errors: Verify the Pohoda API base URL is reachable and correct.
  • Unexpected response structure: If the node throws errors about response state not being "ok," check the Pohoda server status and request parameters.
  • NodeApiError with message from Pohoda: This indicates the Pohoda API returned an error note; review the note for details and adjust the request accordingly.

Links and References

Discussion