Pohoda Node icon

Pohoda Node

Stormware Pohoda Integration Node

Actions76

Overview

This node integrates with the Pohoda accounting system, specifically allowing operations on various resources such as invoices, addresses, bank data, and more. For the Adresy resource with the Create Entity operation, it enables users to create a new address book entry (entity) in Pohoda by providing detailed contact and company information.

Common scenarios for this node include automating the creation of customer or supplier contacts in Pohoda from external systems, syncing CRM contacts, or programmatically managing address book entries during business workflows.

For example, you could use this node to:

  • Automatically add new client details collected from a web form into Pohoda’s address book.
  • Create supplier records when onboarding new vendors.
  • Update internal notes or contact information in bulk via automation.

Properties

Name Meaning
Entity Detail Collection of fields describing the entity to create. Includes:
- Company: Company name
- Name: Person's name
- City: City
- Street: Street
- ZIP Code: Postal code
- IČO: Company Registration ID
- DIČ: Tax Identification Number
- Phone: Telephone number
- Mobile: Mobile phone number
- Email: Email address
- Website: Website URL
- Message: Message
- Note: General note
- Internal Note: Internal note visible only inside the company
XML Output Boolean flag to output raw XML response instead of parsed JSON. Defaults to false.
UTF8 Conversion Boolean flag to convert response encoding from Windows-1250 to UTF-8. Defaults to true.

Output

The node outputs JSON data representing the response from the Pohoda API after creating the entity. The structure corresponds to the parsed XML response converted into a JavaScript object.

  • If XML Output is enabled, the raw XML string response is returned in the json.data field.
  • Otherwise, the response is parsed and returned as structured JSON reflecting the created entity or any status messages.
  • The node does not produce binary data for this operation.

Dependencies

  • Requires an API authentication credential with access to the Pohoda system.
  • The node makes HTTP POST requests to the Pohoda XML API endpoint.
  • Uses XML building and parsing utilities internally.
  • Encoding conversion from Windows-1250 to UTF-8 is optionally applied to handle character sets correctly.

Troubleshooting

  • Authentication errors: Ensure the provided API credentials are correct and have sufficient permissions.
  • Invalid input data: Missing or malformed fields in the "Entity Detail" collection may cause the API to reject the request.
  • Encoding issues: If special characters appear corrupted, try toggling the UTF8 Conversion property.
  • API errors: The node throws errors if the Pohoda API returns a non-ok state, including descriptive messages from the API response.
  • Not implemented errors: Attempting to create entities for unsupported resources will result in an error indicating lack of implementation.

Links and References

Discussion