{"id":71882,"date":"2026-07-15T09:00:00","date_gmt":"2026-07-15T07:00:00","guid":{"rendered":"https:\/\/symmy.com\/erpedie\/make-zapier-n8n-pohoda-2\/"},"modified":"2026-08-18T07:42:32","modified_gmt":"2026-08-18T05:42:32","slug":"make-zapier-n8n-pohoda","status":"publish","type":"erpedie","link":"https:\/\/symmy.com\/en\/erpedie\/make-zapier-n8n-pohoda\/","title":{"rendered":"Make, Zapier, n8n and POHODA: what DIY automation can handle and where it hits a wall"},"content":{"rendered":"<p>Automation platforms promise to connect anything to anything: a few clicks, no developer, the scenario runs. For cloud apps, that holds \u2014 so it is only a matter of time before someone at the company asks: \u201cWhat about hooking up POHODA?\u201d This article is the honest answer: what Make, Zapier and n8n can genuinely do with POHODA, where they hit a wall, and when a different tool is the better choice.<\/p>\n<h2>What Make, Zapier and n8n are great at<\/h2>\n<div class=\"ep-answer\">\n<p>Make, Zapier and n8n are excellent at automating cloud applications. POHODA, however, is not a cloud app \u2014 its machine interface is mServer, which runs on your premises. DIY automation therefore suits notifications and one-way tasks that can tolerate a failure; reliable synchronisation of agendas needs an integration layer with queues and monitoring.<\/p>\n<\/div>\n<ul class=\"ep-cards\">\n<li><strong>Make<\/strong>Visual scenarios with powerful data mapping. It started in the Czech Republic as Integromat, so it has a strong local community and good awareness of Czech applications.<\/li>\n<li><strong>Zapier<\/strong>The largest app catalogue and the lowest barrier to entry. At high volumes, though, paying per scenario step gets expensive fast.<\/li>\n<li><strong>n8n<\/strong>A self-hosted, open-code tool (fair-code licence), a favourite of developers and, lately, of AI agent builders too. \u201cn8n pohoda\u201d is already showing up in searches \u2014 the community is experimenting.<\/li>\n<\/ul>\n<h2>Where DIY hits a wall with POHODA<\/h2>\n<p>All three tools assume a counterparty with a cloud API. POHODA is a desktop application \u2014 and that brings five hard obstacles:<\/p>\n<ul>\n<li><strong>mServer runs on your premises, not in the cloud.<\/strong> POHODA&#8217;s official machine interface is a local service. For a cloud scenario to reach it, you have to expose it securely \u2014 a VPN, a tunnel or an authenticated gateway. \u201cOpening a port to the internet\u201d is not a solution, it is a security incident in the making.<\/li>\n<li><strong>XML is not drag &amp; drop.<\/strong> POHODA speaks its own XML document format. Building a correct invoice with VAT rates, cost centres and links means studying the documentation \u2014 exactly the work you hoped a no-code tool would save you.<\/li>\n<li><strong>Licences and capacity.<\/strong> mServer needs a dedicated POHODA instance and a licence (CAL). Details in <a href=\"\/en\/erpedie\/pohoda-mserver\/\">our article on mServer<\/a>.<\/li>\n<li><strong>No queues, no retries.<\/strong> When a scenario fails mid-transfer, you are left with half an order. DIY tools can rerun a scenario, but they don&#8217;t guard data consistency between systems \u2014 that is the job of an integration layer.<\/li>\n<li><strong>Code lists and matching.<\/strong> Customers, stock cards, VAT rates \u2014 mapping code lists is 80% of the work with accounting data, and scenarios are a poor place to maintain it.<\/li>\n<\/ul>\n<h2>When DIY automation is enough<\/h2>\n<p>The key question is: <strong>what happens if a transfer fails once?<\/strong> If the answer is \u201cnothing terrible\u201d, you are in the territory where Make, Zapier and n8n shine:<\/p>\n<ul class=\"ep-cards\">\n<li><strong>Notifications<\/strong>A new invoice over 100 thousand CZK \u2192 a message to Slack or Teams. A failure doesn&#8217;t hurt, the value is immediate.<\/li>\n<li><strong>One-way exports<\/strong>Orders into a Google sheet for reporting, an overview for the weekly meeting \u2014 data flows one way, nothing is written back.<\/li>\n<li><strong>Internal helpers<\/strong>Due-date reminders, e-mail summaries, watching for changes. Useful little things that don&#8217;t justify an integration project.<\/li>\n<li><strong>Prototypes<\/strong>Quickly verify that a process makes sense \u2014 and only then build it properly.<\/li>\n<\/ul>\n<h2>When DIY is no longer enough<\/h2>\n<div class=\"ep-note\">\n<h2>Automation is not integration<\/h2>\n<p>A workflow tool <strong>triggers tasks<\/strong>. An integration platform <strong>keeps data consistent<\/strong>: queues, retries on failure, monitoring, code list mapping, conflict resolution. Two-way synchronisation of orders and stock stitched together from scenarios is a ticking time bomb \u2014 it doesn&#8217;t crash spectacularly, it just quietly drifts apart, and you only find the differences at stocktaking. How to decide between a bridge, a scenario and a platform is covered in our <a href=\"\/en\/erpedie\/integrace-erp-systemu\/\">guide to ERP integrations<\/a> and our <a href=\"\/en\/erpedie\/propojeni-pohody-s-eshopem\/\">guide to connecting an e-shop<\/a>.<\/p>\n<\/div>\n<h2>And what about AI agents in n8n?<\/h2>\n<p>n8n has become a favourite tool for building AI agents \u2014 and this is where things come full circle. An agent is only as useful as its access to data. That is exactly what the <a href=\"\/en\/erpedie\/co-je-mcp-server\/\">MCP<\/a> standard solves: a unified connector between AI and business systems, gradually being adopted by automation tools as well. Instead of hand-assembling XML, the agent gets ready-made, secured tools like \u201cfind overdue invoices\u201d. Our <a href=\"\/en\/erp-mcp\/\">MCP servers for ERP<\/a> open up POHODA, Money, Helios and other systems this way \u2014 to assistants and agents alike.<\/p>\n<h2>Frequently asked questions<\/h2>\n<details class=\"ep-faq\">\n<summary>Does Zapier or Make have an official POHODA connector?<\/summary>\n<p>No. There are no official POHODA apps in their catalogues; community modules and HTTP templates exist, but their quality and maintenance vary. Always check who maintains a module and what happens when a new POHODA version comes out.<\/p>\n<\/details>\n<details class=\"ep-faq\">\n<summary>Is n8n free?<\/summary>\n<p>The self-hosted version has no licence fees (fair-code licence); you pay for running the server and your own time. n8n&#8217;s cloud version is paid. \u201cFree\u201d therefore only holds until you factor in the maintenance.<\/p>\n<\/details>\n<details class=\"ep-faq\">\n<summary>How do I expose mServer to the internet securely?<\/summary>\n<p>Never by opening a port directly. Use a VPN, an encrypted tunnel, or a gateway with authentication and IP whitelisting \u2014 and give mServer a dedicated account with minimal rights. Or leave the whole connection to an integration platform or a hosted solution.<\/p>\n<\/details>\n<details class=\"ep-faq\">\n<summary>When should I move from scenarios to an integration platform?<\/summary>\n<p>As soon as you need two-way sync, volumes grow, systems multiply, or there is no one left to maintain the scenarios. A good tell: a scenario that someone \u201cprefers to check by hand every morning\u201d is no longer automation.<\/p>\n<\/details>\n","protected":false},"excerpt":{"rendered":"<p>Make, Zapier and n8n will connect almost anything \u2014 but POHODA is not a cloud app. What DIY automation can handle, where it runs into mServer, and when it&#8217;s time for an integration platform.<\/p>\n","protected":false},"author":0,"featured_media":67178,"template":"","class_list":["post-71882","erpedie","type-erpedie","status-publish","has-post-thumbnail","hentry"],"acf":[],"_links":{"self":[{"href":"https:\/\/symmy.com\/en\/wp-json\/wp\/v2\/erpedie\/71882","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/symmy.com\/en\/wp-json\/wp\/v2\/erpedie"}],"about":[{"href":"https:\/\/symmy.com\/en\/wp-json\/wp\/v2\/types\/erpedie"}],"version-history":[{"count":1,"href":"https:\/\/symmy.com\/en\/wp-json\/wp\/v2\/erpedie\/71882\/revisions"}],"predecessor-version":[{"id":71952,"href":"https:\/\/symmy.com\/en\/wp-json\/wp\/v2\/erpedie\/71882\/revisions\/71952"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/symmy.com\/en\/wp-json\/wp\/v2\/media\/67178"}],"wp:attachment":[{"href":"https:\/\/symmy.com\/en\/wp-json\/wp\/v2\/media?parent=71882"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}