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 Nabídky (Offers) resource with the Company Info operation, the node fetches detailed information about the company associated with the authenticated Pohoda account.

Common scenarios where this node is beneficial include automating data retrieval from Pohoda for accounting, invoicing, or reporting purposes, integrating Pohoda data into workflows, or generating documents based on Pohoda data.

For example, a user might use this node to automatically retrieve company details before generating invoices or to export offer lists for further processing in other systems.

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.

Output

The output depends on the XML Output property:

  • If XML Output is false (default), the node parses the XML response into a JSON object and outputs the company information under the mServer key. This JSON contains structured company details as provided by Pohoda's API.

  • If XML Output is true, the node outputs the raw XML response as a string in the data field of the JSON output.

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

No binary data output is produced for the Company Info operation.

Dependencies

  • Requires an API authentication credential with username, password, and base URL for the Pohoda API.
  • Uses HTTP requests with Basic Authentication to communicate with the Pohoda API.
  • Utilizes external libraries for XML building and decoding:
    • iconv-lite for character encoding conversion (Windows-1250 to UTF-8).
    • xmlbuilder2 for XML parsing and conversion to JSON.
  • The node expects the Pohoda API endpoint /status?companyDetail to be accessible.

Troubleshooting

  • Encoding Issues: If the response contains incorrect characters, ensure that the UTF8 Conversion property is enabled to properly convert Windows-1250 encoded responses to UTF-8.

  • Authentication Errors: If the node throws errors related to authorization, verify that the API credentials (username, password, base URL) are correct and have sufficient permissions.

  • API Response Errors: The node checks the response state and will throw errors if the Pohoda API returns a non-ok status. The error message from the API is propagated to help diagnose issues.

  • Network Issues: Ensure that the Pohoda API server is reachable from the n8n environment.

  • Unexpected Response Structure: If the node fails to parse the response, confirm that the Pohoda API version and endpoint have not changed.

Links and References

Discussion