Pohoda Node icon

Pohoda Node

Stormware Pohoda Integration Node

Výdejky → Export

AI-generated

Overview

This node integrates with the Stormware Pohoda accounting system, specifically enabling export operations for various document types and agendas. For the "Výdejky" (Issues) resource with the "Export" operation, it allows users to retrieve records related to goods issues from Pohoda, filtered by multiple criteria such as date ranges, company name, or document IDs.

Common scenarios include:

  • Exporting issue documents for inventory or warehouse management.
  • Retrieving filtered lists of issued goods for reporting or synchronization with other systems.
  • Automating data extraction workflows involving Pohoda's Issues agenda.

Example: A user wants to export all "Výdejky" records issued after a certain date to update their external inventory system daily.

Properties

Name Meaning
Filter Collection of filters 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 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 (IČO)
Return Records Count Number of records to return in one export batch (range 1 to 10000). Defaults to 10.
Start Record ID Minimum record ID from which to start the export (used for pagination or incremental exports).
XML Output Boolean flag indicating if the output should be raw XML string instead of parsed JSON objects.
UTF8 Conversion Boolean flag to convert response encoding from Windows-1250 to UTF-8. Defaults to true.

Output

The node outputs an array of items corresponding to the exported "Výdejky" records:

  • If XML Output is enabled, each item contains a json field with a single property data holding the raw XML string response from Pohoda.
  • Otherwise, the XML response is parsed into JSON objects representing individual records, each returned as a separate item under the json field.
  • The node supports paired input-output mapping, preserving the association between input items and their respective outputs.
  • No binary data output is produced for this export operation.

Dependencies

  • Requires an API key credential for authenticating with the Pohoda API.
  • Uses HTTP POST requests to Pohoda's XML endpoint (/xml) with Basic Authentication.
  • Converts character encoding from Windows-1250 to UTF-8 if enabled.
  • Relies on internal utility functions to generate XML request bodies based on filters and resource type.
  • Requires n8n environment configured with the appropriate Pohoda API credentials.

Troubleshooting

  • Authentication errors: Ensure the provided API credentials are correct and have sufficient permissions.
  • Invalid filter parameters: Dates must be valid ISO strings; invalid or unsupported filters may cause API errors.
  • Encoding issues: If the output appears garbled, verify the UTF8 Conversion setting matches your use case.
  • API response errors: The node throws errors if Pohoda returns a non-"ok" state with an explanatory note. Check the note message for details.
  • Not implemented resource error: Using resources not supported by the export operation will throw an error indicating lack of implementation.

Links and References


If you need further details about other operations or resources, please provide their names.

Discussion