Pohoda Node

Overview

The Pohoda Node integrates with the Stormware Pohoda accounting system, enabling users to perform various operations such as exporting data, creating entities, retrieving company information, and printing reports. Specifically, for the "Pohyby" resource with the "Company Info" operation, the node fetches detailed company status information from the Pohoda API.

This node is beneficial in scenarios where automated access to accounting data or company details is required within an n8n workflow. For example, a user might want to retrieve up-to-date company info to include in reports or trigger other processes based on company status changes.

Properties

Output

• When XML Output is enabled (true), the node outputs a JSON object with a data field containing the raw XML response as a UTF-8 string.
• When XML Output is disabled (false), the node outputs a JSON object representing the parsed XML response converted into a JavaScript object under the mServer property.
• The output is paired with the input item index for traceability.
• No binary data output is produced by the "Company Info" operation.

Example output when XML Output is false (simplified):

{
  "mServer": {
    // Parsed company info fields here
  }
}

Example output when XML Output is true:

{
  "data": "<?xml version=\"1.0\" encoding=\"utf-8\"?><rsp:responsePack>...</rsp:responsePack>"
}

Dependencies

• Requires an API authentication credential with username and password to access the Pohoda API.
• Uses HTTP requests with Basic Authentication headers.
• Converts character encoding from Windows-1250 to UTF-8 using the iconv-lite library.
• Parses XML responses using the xmlbuilder2 library.
• Requires configuration of the Pohoda API base URL and credentials in n8n.

Troubleshooting

• Encoding issues: If the response contains garbled characters, ensure that UTF8 Conversion is enabled to properly convert Windows-1250 encoded responses.
• Authentication errors: Errors related to authorization usually indicate incorrect or missing API credentials. Verify the API username and password are correctly configured.
• API errors: If the Pohoda API returns a state other than "ok", the node throws an error with the message provided by the API. Check the API request parameters and filters for correctness.
• Network issues: Ensure the Pohoda API base URL is reachable from the n8n environment and no firewall or proxy blocks the connection.

Links and References

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