Pohoda Node icon

Pohoda Node

Stormware Pohoda Integration Node

Overview

This node integrates with the Pohoda accounting system, specifically supporting operations such as exporting data, creating entities, retrieving company info, and printing reports. For the "Pohyby" resource with the "Create Entity" operation, it allows users to create new records in the Pohoda address book agenda by sending structured XML requests to the Pohoda API.

Common scenarios include automating the creation of contact or movement records in Pohoda from external systems, streamlining bookkeeping workflows, or integrating Pohoda with other business tools.

Example use case: Automatically adding a new supplier or customer contact into Pohoda when a new entry is created in a CRM system.

Properties

Name Meaning
XML Output If enabled, returns the raw XML response from Pohoda instead of parsed JSON data.
UTF8 Conversion If enabled, converts the response encoding from Windows-1250 to UTF-8 for easier handling.

Output

The node outputs an array of items corresponding to each input item processed:

  • When XML Output is enabled, the output contains a json field with the raw XML response string under the key data.
  • Otherwise, the output contains parsed JSON objects representing the Pohoda API response.
  • In some cases (e.g., print operation), binary PDF data may be returned as a binary property named data with appropriate MIME type and file extension.
  • For the "Create Entity" operation on the Pohyby resource, the output will contain the result of the creation request parsed from the Pohoda response.

Dependencies

  • Requires an API authentication credential with username, password, and base URL for the Pohoda API.
  • Uses HTTP POST requests with XML payloads to communicate with Pohoda's XML endpoint.
  • Uses external libraries for XML building and decoding Windows-1250 encoded responses.
  • The node expects the Pohoda API to be accessible at the configured base URL.

Troubleshooting

  • Authentication errors: Ensure the provided API credentials are correct and have sufficient permissions.
  • Encoding issues: If response characters appear garbled, verify the UTF8 Conversion setting; enabling it converts Windows-1250 encoding to UTF-8.
  • Unsupported resource or operation: The node throws errors if the selected resource or operation is not implemented. Verify that "Pohyby" resource and "Create Entity" operation are supported.
  • API errors: If Pohoda returns an error state, the node surfaces the error message from the API response. Check the message for details and adjust the request accordingly.
  • Malformed XML: Ensure the entity data provided matches Pohoda's expected schema to avoid XML generation or validation errors.

Links and References

Discussion