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 "Nabídky" (Offers) 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 customer or supplier offers within Pohoda directly from workflows, streamlining data entry, and synchronizing external systems with Pohoda's offers agenda.
Example use case: Automatically create a new offer entity in Pohoda when a lead is qualified in a CRM system, using this node to send the relevant data.
Properties
| Name | Meaning |
|---|---|
| XML Output | If enabled, returns the raw XML response from Pohoda instead of parsed JSON data. |
| UTF8 Conversion | If enabled, converts the response encoding from Windows-1250 to UTF-8 for proper display. |
Additional properties relevant to the "Create Entity" operation on the "Nabídky" resource are not explicitly defined in the provided snippet, but generally, the node expects a collection of fields describing the entity details (e.g., company name, address, contact info) under a parameter like createEntity.
Output
The node outputs JSON data representing the response from the Pohoda API after performing the requested operation.
- If XML Output is enabled, the output contains a JSON object with a
datafield holding the raw XML string. - Otherwise, the XML response is parsed into a JSON object reflecting the structure of the Pohoda response.
- For print operations, the node can output binary PDF data with metadata such as filename and MIME type.
- In the case of errors, the node throws detailed error messages extracted from the Pohoda response.
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 Pohoda endpoints.
- Utilizes libraries for XML building and parsing (
xmlbuilder2), character encoding conversion (iconv-lite), and n8n workflow helpers. - The node expects the Pohoda API to be accessible and properly configured to accept requests from the node.
Troubleshooting
- Authentication Errors: Ensure that the API credentials (username, password, base URL) are correct and have sufficient permissions.
- Encoding Issues: If the response contains garbled characters, verify the UTF8 Conversion setting; disabling it may help if your environment handles Windows-1250 encoding differently.
- Unsupported Resource or Operation: The node throws errors if an unsupported resource or operation is selected. Confirm that "Nabídky" with "Create Entity" is supported.
- Malformed XML Requests: Input data must conform to expected formats; otherwise, Pohoda may reject the request with an error note.
- Network Issues: Check connectivity to the Pohoda API endpoint and firewall settings.
- Error Messages: The node surfaces error notes from Pohoda responses. Review these messages for clues about missing or invalid data.
Links and References
- Pohoda API Documentation (official API docs)
- n8n Documentation for general node usage and credential setup
- iconv-lite GitHub for encoding conversions
- xmlbuilder2 GitHub for XML manipulation
If you need further details on other operations or resources, please provide additional context.