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, specifically enabling operations on various accounting and business resources. For the Účetní deník (PÚ) resource with the Create Entity operation, it allows users to create new entities in Pohoda by sending structured XML requests to the Pohoda API.
Typical use cases include automating the creation of accounting journal entries or related records directly from workflows, such as adding new accounting transactions or documents without manual data entry in Pohoda. This is beneficial for businesses that want to streamline their accounting processes by integrating Pohoda with other systems like CRMs, ERPs, or custom applications.
For example, a user can configure this node to create a new accounting journal entry based on incoming invoice data processed elsewhere in the workflow, ensuring consistent and timely bookkeeping.
Properties
Name | Meaning |
---|---|
XML Output | If enabled (true ), the node outputs 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 node handles the response data from Pohoda after creating an entity.
Output
The node outputs an array of items corresponding to each input item processed:
- If XML Output is enabled, the output contains a
json
field with adata
property holding the raw XML string returned by Pohoda. - Otherwise, the node parses the XML response into a JSON object representing the created entity or the response status.
- In case of print operations (not relevant here), it can output binary PDF data.
- Each output item is paired with its corresponding input item for traceability.
The main output structure for the Create Entity operation includes:
{
"json": {
// Parsed response object from Pohoda about the created entity,
// including status and any returned data fields.
},
"pairedItem": <index_of_input_item>
}
If an error occurs during the request, the node throws an error unless configured to continue on failure, in which case the error details are included in the output.
Dependencies
- Requires an API authentication credential for Pohoda with username, password, and base URL.
- Uses HTTP POST requests to Pohoda's XML API endpoint.
- Depends on external libraries for:
- XML building and parsing.
- Character encoding conversion (Windows-1250 to UTF-8).
- No additional environment variables are required beyond the configured credentials.
Troubleshooting
Common issues:
- Incorrect or missing API credentials will cause authentication failures.
- Malformed or incomplete entity data may result in Pohoda rejecting the request with an error message.
- Encoding issues if UTF8 Conversion is disabled but the response contains special characters.
- Unsupported resource types for creation will throw a "Not implemented" error.
Error messages:
- Errors returned from Pohoda are extracted from the XML response's
@note
attribute and thrown as node errors. - Network or HTTP errors during the request will also be surfaced.
- To resolve, verify credentials, ensure correct resource and entity data, and enable UTF8 Conversion if character issues occur.
- Errors returned from Pohoda are extracted from the XML response's
Links and References
- Stormware Pohoda API Documentation (official developer resources)
- n8n HTTP Request Node Documentation (for understanding HTTP calls)
- XMLBuilder2 Library (used internally for XML handling)
This summary focuses on the Účetní deník (PÚ) resource with the Create Entity operation, describing how the node constructs and sends XML requests to Pohoda and handles responses accordingly.