Pohoda Node icon

Pohoda Node

Stormware Pohoda Integration Node

Actions76

Overview

This node integrates with the Stormware Pohoda accounting system, specifically enabling export operations for various accounting and business data resources. For the "Účetní deník (PÚ)" resource with the "Export" operation, it allows users to export accounting journal entries from Pohoda based on customizable filters and pagination options.

Typical use cases include:

  • Exporting accounting journal entries for reporting or auditing purposes.
  • Extracting filtered subsets of accounting data by date range, company, or document ID.
  • Automating data synchronization between Pohoda and other financial or ERP systems.

For example, a user might export all accounting journal entries from the start of the fiscal year until today, or retrieve entries related to a specific company identified by its registration number (IČO).

Properties

Name Meaning
Filter Collection of filter criteria to narrow down exported records. Options include:
- ID: Filter by document ID
- External ID: Filter by external document ID
- Date From: Filter records from this date (inclusive)
- Date Till: Filter records up to this date (inclusive)
- Last Changes: Filter records changed since this date
- Company Name: Filter by company name
- User Custom Filter Name: Apply a custom Pohoda filter
- IČO: Filter by company registration number
Return Records Count Number specifying how many records to return in one export call (range 1 to 10000). Default is 10.
Start Record ID Minimum record ID from which to start exporting (pagination support).
XML Output Boolean flag indicating whether to output raw XML response instead of parsed JSON.
UTF8 Conversion Boolean flag to convert response encoding from Windows-1250 to UTF-8 (default true).

Output

The node outputs an array of items corresponding to the exported accounting journal entries matching the specified filters.

  • If XML Output is enabled, the output contains a single item with a json field holding the raw XML string data returned by Pohoda.
  • Otherwise, the XML response is parsed into JSON objects representing the accounting journal entries.
  • Each output item’s json field contains one or more accounting journal entry objects extracted from the response.
  • The node supports paired item output, preserving input-output mapping.
  • No binary data output is produced for this resource-operation combination.

Dependencies

  • Requires connection credentials to the Pohoda API, including base URL and authentication (username and password).
  • Uses HTTP POST requests with XML payloads to communicate with Pohoda's XML API endpoint.
  • Converts character encoding from Windows-1250 to UTF-8 if enabled.
  • Utilizes helper functions to generate XML requests and parse XML responses.
  • Requires n8n environment configured with appropriate Pohoda API credentials.

Troubleshooting

  • Common issues:

    • Authentication failures due to incorrect or missing API credentials.
    • Invalid filter parameters causing Pohoda API errors.
    • Encoding issues if UTF8 conversion is disabled but response contains Windows-1250 characters.
    • Request limits exceeded if Return Records Count is set too high.

  • Error messages:

    • Errors returned by Pohoda API are surfaced as node errors with messages from the API response note.
    • If the response state is not "ok", the node throws an error with the provided message.
    • Network or HTTP errors during request execution will cause node failure unless "Continue On Fail" is enabled.

  • Resolutions:

    • Verify API credentials and permissions.
    • Check and adjust filter values for correctness.
    • Enable UTF8 conversion to avoid character encoding problems.
    • Use reasonable pagination settings to avoid large payloads.

Links and References

Discussion