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
Převod → Export
AI-generatedOverview
This node integrates with the Pohoda accounting system to perform various operations such as exporting data, creating entities, retrieving company information, and printing reports. Specifically for the "Převod" resource with the "Export" operation, it exports transfer records from Pohoda based on specified filters and parameters.
Common scenarios where this node is beneficial include:
- Automating the extraction of transfer records for reporting or further processing.
- Integrating Pohoda transfer data into other systems or workflows.
- Exporting filtered subsets of transfer data by record ID or count limits.
For example, a user might export the last 100 transfer records starting from a specific record ID to synchronize with an external database or generate custom reports.
Properties
| Name | Meaning |
|---|---|
Return Records Count (count) |
Number of records to export; valid range is 1 to 10,000. Limits how many transfer records are retrieved in one execution. |
Start Record ID (idFrom) |
Minimum record ID from which to start the export. Allows exporting records starting from a specific ID. |
XML Output (xmlOutput) |
Boolean flag indicating whether the output should be raw XML data (true) or parsed JSON (false). |
UTF8 Conversion (utfConvert) |
Boolean flag to convert response encoding from Windows-1250 to UTF-8. Useful for proper character encoding in outputs. |
Output
The node outputs data in the following ways depending on the xmlOutput property:
- If
xmlOutputistrue, the output contains a single fielddatawith the raw XML string returned from the Pohoda API, optionally converted to UTF-8 encoding. - If
xmlOutputisfalse, the XML response is parsed into a JSON object representing the Pohoda response structure. The relevant data items (e.g., transfer records) are extracted and output as individual JSON objects, each corresponding to a record. - In case of print operations (not applicable here), binary PDF data may be output, but for the "Export" operation on "Převod", only JSON or XML data is produced.
Each output item is paired with the input item index for traceability.
Dependencies
- Requires an API authentication credential with username, password, and base URL for the Pohoda API.
- Uses HTTP POST requests to Pohoda's
/xmlendpoint with XML payloads. - Depends on external libraries for XML building and parsing, and for character encoding conversion.
- The node expects the Pohoda API to support versioned XML requests for the "prevodka" (transfer) resource.
Troubleshooting
- Authentication errors: Ensure the provided API credentials (username, password, base URL) are correct and have sufficient permissions.
- Encoding issues: If special characters appear garbled, verify the
UTF8 Conversionsetting matches the expected encoding of the Pohoda server response. - Invalid filter or parameters: Check that the
Start Record IDandReturn Records Countare within valid ranges and correctly formatted. - Unsupported resource or operation: The node throws errors if the resource or operation is not implemented; confirm you are using supported values.
- API errors: If the Pohoda API returns an error state, the node surfaces the error message from the API response. Review the message for details and adjust request parameters accordingly.
Links and References
- Pohoda API Documentation (official API docs for integration)
- n8n Documentation (for general usage of n8n nodes and credentials)
- XMLBuilder2 Library (used internally for XML handling)
- iconv-lite Library (used for character encoding conversions)
