Pohoda Node icon

Pohoda Node

Stormware Pohoda Integration Node

Actions76

Overview

This node integrates with the Stormware Pohoda accounting system, specifically enabling operations on various financial and business entities. For the "Faktury" (Invoices) resource with the "Create Entity" operation, it allows users to create new invoice-related entities in Pohoda by sending structured XML requests to the Pohoda API.

Common scenarios include automating invoice creation workflows, integrating external systems with Pohoda for seamless invoice management, or batch-creating invoices based on external data sources.

For example, a user can automate the creation of issued invoices or received advance invoices directly from their CRM or ERP system into Pohoda without manual entry.

Properties

Name Meaning
Invoice Type The type of invoice entity to create. Options: Issued Invoice, Issued Advance Invoice, Received Invoice, Received Advance Invoice
XML Output Boolean flag indicating whether the response should be returned as raw XML string (true) or parsed JSON object (false).
UTF8 Conversion Boolean flag to convert the response encoding from Windows-1250 to UTF-8 (true by default).

Output

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

  • If XML Output is enabled, the output contains a JSON field data with the raw XML response string from Pohoda.
  • Otherwise, the XML response is parsed into a JSON object representing the Pohoda response structure.
  • In case of print operations (not relevant here), binary PDF data may be output.
  • On success, the output JSON reflects the created entity's details or confirmation from Pohoda.
  • On failure, errors are thrown or included in the output if "Continue On Fail" is enabled.

Dependencies

  • Requires valid credentials for Pohoda API access, including base URL, username, and password.
  • Uses HTTP POST requests with Basic Authentication to communicate with Pohoda's XML API endpoint.
  • Relies on XML building and parsing libraries internally to generate and interpret Pohoda-specific XML requests and responses.
  • Encoding conversion from Windows-1250 to UTF-8 is optionally applied using an encoding library.

Troubleshooting

  • Authentication Errors: Ensure that the provided API credentials (username and password) are correct and have sufficient permissions.
  • Invalid XML or Request Format: The node constructs XML requests based on input parameters; incorrect or incomplete input data may cause Pohoda to reject the request with error messages.
  • Encoding Issues: If response data appears garbled, verify the UTF8 Conversion setting; disabling it may help if your environment expects Windows-1250 encoding.
  • Unsupported Resource or Operation: Attempting to create entities for unsupported resources will throw an error indicating "Not implemented for [resource]".
  • API Response Errors: Pohoda responses with state not equal to "ok" will cause the node to throw errors with the message from Pohoda's note field.

Links and References

Discussion