Pohoda Node

Overview

This node integrates with the Stormware Pohoda accounting system, enabling users to interact with various Pohoda resources and operations. Specifically for the Banka resource with the Company Info operation, it 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 from Pohoda for use in workflows such as reporting, auditing, or synchronization with other systems.
• Automating data retrieval to keep external databases or CRMs aligned with the company's official records in Pohoda.
• Using the company info as part of a larger automation that requires verified company metadata.

Practical example:

• A workflow that triggers on a schedule to fetch the latest company info from Pohoda and updates a CRM or sends a summary email to stakeholders.

Properties

Output

The output depends on the XML Output property:

• If XML Output is false (default):

  • The node outputs a JSON object representing the parsed company information under the json field.
  • The structure corresponds to the mServer property extracted from the Pohoda XML response, containing detailed company data.

• If XML Output is true:

  • The node outputs the raw XML response as a UTF-8 string under the json.data field.
  • This allows users to handle or store the original XML if needed.

No binary data output is produced by this operation.

Dependencies

• Requires an API authentication credential with access to the Pohoda API (username and password).
• The node makes HTTP requests to the Pohoda API base URL configured in the credentials.
• Uses internal utilities for XML generation and parsing, including:
  • iconv-lite for character encoding conversion (Windows-1250 to UTF-8).
  • xmlbuilder2 for XML parsing into JavaScript objects.

Troubleshooting

• Encoding issues: If the response contains unexpected characters, ensure that the UTF8 Conversion option is enabled to properly convert from Windows-1250 encoding.
• Authentication errors: If the node throws authorization errors, verify that the provided API credentials are correct and have sufficient permissions.
• API errors: The node checks the response state and will throw errors if Pohoda reports any issues. The error message from Pohoda is included to help diagnose problems.
• Network issues: Ensure that the Pohoda API endpoint is reachable from the n8n environment and that no firewall or proxy blocks the connection.

Links and References

• Stormware Pohoda API Documentation (official developer resources)
• iconv-lite npm package — for character encoding conversions
• xmlbuilder2 npm package — for XML parsing and building