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 Pohoda accounting system, enabling users to perform various operations such as exporting data, creating entities, retrieving company information, and printing reports. Specifically for the Banka resource with the Create Entity operation, it allows creating new address book entries (entities) in Pohoda by sending structured XML requests.
Common scenarios include automating the creation of bank-related entities or contacts within Pohoda from external systems, streamlining bookkeeping workflows, or integrating Pohoda with other business applications.
Example use case: Automatically adding a new bank contact or entity into Pohoda when a new client is onboarded in a CRM system.
Properties
| Name | Meaning |
|---|---|
| XML Output | If enabled (true), the node returns the raw XML response from Pohoda instead of parsed JSON. |
| UTF8 Conversion | If enabled (true), converts the response encoding from Windows-1250 to UTF-8 for proper character display. |
These properties control how the response from Pohoda is returned and encoded.
Output
The node outputs an array of items corresponding to each input item processed. Each output item contains:
json: Parsed JSON object representing the response from Pohoda after the create entity request.- If
XML Outputis enabled, the raw XML string is returned insidejson.data. - In some cases (e.g., print operation), binary data such as PDF files may be returned under the
binaryproperty with appropriate metadata (mimeType,fileExtension,fileName).
For the Create Entity operation on the Banka resource, the output will primarily be the JSON representation of the created entity confirmation or error details if the operation fails.
Dependencies
- Requires valid credentials for Pohoda API authentication (an API key or username/password).
- The node uses HTTP POST requests to Pohoda's XML API endpoint.
- Uses external libraries for XML building and encoding conversion.
- Requires n8n environment configured with the necessary Pohoda API credentials.
Troubleshooting
Common issues:
- Authentication failures due to incorrect or missing API credentials.
- Encoding problems if UTF8 conversion is disabled but the response contains special characters.
- Errors returned from Pohoda API indicating invalid request structure or missing required fields.
Error messages:
- If the Pohoda API response state is not "ok", the node throws an error with the message from the API's note field.
- Network or HTTP errors during the request will also cause the node to fail unless "Continue On Fail" is enabled.
Resolutions:
- Verify API credentials and permissions.
- Enable UTF8 conversion if you see garbled characters.
- Ensure all required entity fields are provided correctly in the input.
- Check the Pohoda API documentation for correct XML request formats.
Links and References
- Pohoda API Documentation
- n8n HTTP Request Node Documentation
- iconv-lite Encoding Library
- xmlbuilder2 Library
If you need further details about other operations or resources, feel free to ask!