Pohoda Node

Overview

This node integrates with the Pohoda accounting system API, enabling users to perform various operations such as exporting data, creating entities, printing reports, and retrieving company information. Specifically, for the Převod 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 retrieval of company details for reporting or verification purposes.
• Integrating Pohoda company data into other workflows or systems.
• Exporting or manipulating various accounting documents and records from Pohoda.

For example, a user might use this node to automatically fetch their company's current status and details before generating financial reports or syncing data with CRM systems.

Properties

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 string of the company info response.

  Example:

  {
    "data": "<rsp:responsePack ...>...</rsp:responsePack>"
  }
  

• If XML Output is false, the node parses the XML response into a JSON object and outputs the mServer property of the parsed response, which contains structured company information.

  Example (simplified):

  {
    "mServer": {
      "companyName": "Example Company",
      "ico": "12345678",
      "address": { ... },
      ...
    }
  }
  

No binary data output is produced by this operation.

Dependencies

• Requires an API authentication credential with username, password, and base URL for the Pohoda API.
• The node uses HTTP requests with Basic Authentication to communicate with the Pohoda API endpoints.
• Uses external libraries for XML building and parsing, and for character encoding conversion (Windows-1250 to UTF-8).

Troubleshooting

• Encoding issues: If the company info contains special characters and appears garbled, ensure that the UTF8 Conversion property is enabled to properly convert from Windows-1250 encoding.
• Authentication errors: If the node fails with authorization errors, verify that the provided API credentials are correct and have sufficient permissions.
• API errors: The node throws errors if the Pohoda API response indicates failure (e.g., invalid request, missing parameters). The error message from the API is propagated to help diagnose the issue.
• Network issues: Ensure that the base URL is reachable from the n8n environment and that no firewall or proxy blocks the connection.

Links and References

• Pohoda API Documentation (official developer resources)
• n8n HTTP Request Node Documentation (for understanding HTTP request usage)
• iconv-lite npm package (used for encoding conversions)