Actions76
- Faktury Actions
- Příjemky Actions
- Prodejky Actions
- Objednávky Actions
- Výdejky Actions
- Pokladní doklady Actions
- Nabídky Actions
- Výroba Actions
- Interní doklady Actions
- Poptávky Actions
- Převod Actions
- Banka Actions
- Zakázky Actions
- Pohyby Actions
- Účetní deník (PÚ) Actions
- Adresy Actions
- Zásoby Actions
- Prodejní ceny Actions
Overview
This node integrates with the Stormware Pohoda accounting system, enabling users to export various types of data records, including sales prices ("Prodejní ceny"). The "Export" operation allows retrieving lists of records filtered by criteria such as record count and starting record ID. It supports output in XML format or parsed JSON, with optional UTF-8 conversion.
Typical use cases include:
- Exporting sales price lists for further processing or reporting.
- Automating data synchronization between Pohoda and other systems.
- Extracting filtered subsets of accounting or sales data based on date ranges or IDs.
For example, a user can export up to 1000 sales price records starting from a specific record ID, receiving either raw XML or structured JSON data for integration into their workflows.
Properties
Name | Meaning |
---|---|
Return Records Count (count ) |
Number of records to return in the export; valid range is 1 to 10,000. Default is 10. |
Start Record ID (idFrom ) |
Minimum record ID from which to start the export. Optional; if empty, export starts from the beginning. |
XML Output (xmlOutput ) |
Boolean flag indicating whether to output raw XML data (true ) or parsed JSON (false ). Default is false . |
UTF8 Conversion (utfConvert ) |
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 records:
- If XML Output is enabled, each item contains a
json
field with adata
property holding the raw XML string of the response. - Otherwise, the XML response is parsed into a JSON object representing the Pohoda response structure, and each record is output as a separate JSON item.
- In case of print operations (not relevant here), binary PDF data may be output.
- The output includes paired item indices to correlate responses with input items.
The JSON structure reflects the Pohoda API's response pack, containing metadata about the request state and the list of requested entities.
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 the Pohoda server.
- Depends on external libraries for XML building/parsing and character encoding conversion.
- No additional environment variables are required beyond the configured credentials.
Troubleshooting
- Authentication errors: Ensure the provided API credentials (username, password, base URL) are correct and have sufficient permissions.
- Encoding issues: If the output contains garbled characters, verify the UTF8 Conversion setting; disabling it will return raw Windows-1250 encoded data.
- Invalid filters or parameters: Check that filter dates are in ISO format and that numeric parameters like
count
andidFrom
are within valid ranges. - Unsupported resource error: Attempting to export a resource not implemented by the node will throw an error; confirm the resource name matches supported options.
- API errors: The node surfaces Pohoda API error messages; review these messages for details on invalid requests or server-side issues.
Links and References
- Stormware Pohoda API Documentation (official API docs)
- n8n HTTP Request Node Documentation (for understanding HTTP communication)
- iconv-lite npm package (character encoding conversion used internally)