Pohoda Node icon

Pohoda Node

Stormware Pohoda Integration Node

Overview

This node integrates with the Stormware Pohoda accounting system, specifically enabling export operations for various document types including offers ("Nabídky"). The Export operation allows users to retrieve filtered lists of documents from Pohoda in XML or JSON format. This is useful for automating data extraction workflows such as syncing offers data with other systems, generating reports, or archiving records.

For the "Nabídky" (Offers) resource, the node exports offer documents based on user-defined filters like date ranges, company name, or document IDs. It supports pagination and can return results either as raw XML or parsed JSON objects.

Practical examples:

  • Export all offers created after a certain date to update a CRM system.
  • Retrieve a specific offer by its ID for detailed processing.
  • Export offers in XML format for archival or integration with other accounting tools.

Properties

Name Meaning
Filter Collection of filter criteria to narrow down exported offers. Options include:
- ID: Filter by document ID
- External ID: Filter by external ID
- Date From: Filter offers from this date
- Date Till: Filter offers until this date
- Last Changes: Filter by last modification 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 of records to return (range 1 to 10000). Default is 10.
Start Record ID Minimum record ID from which to start exporting.
XML Output Boolean flag to output raw XML instead of parsed JSON. Default is false.
UTF8 Conversion Boolean flag to convert response encoding from Windows-1250 to UTF-8. Default is true.

Output

The node outputs an array of items corresponding to the exported offers matching the filter criteria.

  • If XML Output is enabled, each item contains a json field with a single property data holding the raw XML string response.
  • Otherwise, the XML response is decoded and parsed into a JSON object representing the response pack from Pohoda. Each offer is extracted and output as a separate JSON item.
  • The output items are paired with their input items for traceability.

No binary data output is produced for the export operation on offers.

Dependencies

  • Requires an API authentication credential with access to the Pohoda API.
  • Uses HTTP POST requests to Pohoda's /xml endpoint with Basic Authentication.
  • Converts character encoding from Windows-1250 to UTF-8 if enabled.
  • Utilizes XML builder and parser libraries internally to generate requests and parse responses.

Troubleshooting

  • Common issues:

    • Incorrect or missing API credentials will cause authentication failures.
    • Filters with invalid date formats may result in errors or empty results.
    • Requesting unsupported resources or operations will throw a "Not implemented" error.
    • Large counts without proper pagination might lead to timeouts or partial data.
  • Error messages:

    • Errors returned from Pohoda API are surfaced with the message from the response's @note attribute.
    • Node API errors indicate issues with request construction or response parsing.
    • To resolve, verify credentials, ensure correct filter parameters, and check network connectivity.

Links and References

Discussion