Every business eventually hits the same wall: the services the team uses don't talk to each other. Website leads are copied into the CRM by hand, bank payments are reconciled manually, shipping labels are typed into the courier's portal. n8n is the tool that stitches these gaps together. This guide explains what it is, who it fits, and what it really costs.
What n8n is, in plain words
n8n is a workflow automation platform: a visual builder where you connect services into scenarios following the "event happened → run actions" principle. A lead arrives from the website → create a deal in the CRM → message the manager in Telegram → set a follow-up task in 15 minutes. Configure it once — it runs on its own, around the clock.
The key difference from competitors: n8n is open source and can be deployed on your own server. Your data — leads, clients, payments — never passes through someone else's cloud, and the logic is not capped by an "up to N operations per month" plan.
How n8n differs from Zapier and Make
In short: Zapier is the simplest and most expensive, Make is the compromise, n8n is the most flexible and cheapest to own at scale. Three main differences:
1. Pricing model. Zapier and Make bill every operation. A scenario processing 10,000 events a month costs hundreds of dollars. Self-hosted n8n runs a million operations for the price of server rent (from ≈$10-20/mo).
2. Data. With cloud platforms your data flows through the vendor's infrastructure. With self-hosted n8n it never leaves your perimeter — often decisive for financial, personal and medical data.
3. Depth. When a ready integration doesn't exist, in n8n you write a few lines of JavaScript right inside the scenario or call any API via an HTTP request. The limits are set by the service's API, not the platform's catalogue.
A detailed comparison with pricing tables lives in n8n vs Make vs Zapier.
What n8n solves for Ukrainian business
The most valuable part of n8n in Ukraine: it connects local services missing from Western platform catalogues:
Nova Poshta: automatic waybill creation from a CRM order, delivery status tracking, client notifications.
Monobank / PrivatBank: payment webhook → invoice closed in the CRM, payment reconciliation, financial analytics.
Checkbox (fiscal receipts): receipts issued without re-typing order items.
Vchasno / Diia.Signature: documents sent for signature automatically on deal status change.
OpenDataBot: counterparty checks by registry code before the first proposal goes out.
Plus the classics: CRM (Planfix, KeyCRM, monday.com), Google Sheets, Telegram/Viber bots, email, social media, 1C/BAS via API or file exchange.
Real scenarios from our practice
We run dozens of production n8n scenarios — from simple notifications to AI agents that analyse communications and create tasks on their own. Five worked examples with architecture are in 5 Planfix automation scenarios with n8n. The most telling patterns:
Lead processing: a request from any source (website, Instagram, marketplace) → deduplication → scoring → CRM card → manager task with a deadline. No lead is lost; reaction time is seconds.
Accounting sync: two-way CRM ↔ accounting system exchange (BAS, 1C): products and stock into the CRM, sales back into accounting. Managers work in a convenient system, accountants in their usual one.
AI communication processing: call transcription, commitments extracted from correspondence, automatic executive summaries. What used to take an hour of reading arrives as a ready report.
Cost of ownership
Licence: the self-hosted version is free (fair-code licence). The vendor cloud starts at ≈$24/mo, but for business tasks we almost always recommend self-hosting.
Server: ≈$10-40/mo depending on load (Hetzner, DigitalOcean or a Ukrainian host).
Implementation: a typical integration scenario runs 5,000-15,000 UAH; a full exchange bus between systems — 20,000-40,000 UAH, depending on the number of systems and logic complexity.
Maintenance: scenarios need oversight — service APIs change. Budget a few hours a month or a support plan.
When n8n is not the best choice
Honesty requires saying this too:
A single simple link (form → spreadsheet) — Zapier's free tier or a built-in integration is enough; no server needed.
Nobody to maintain it: a self-hosted tool without an owner degrades. Either take a support plan or use n8n cloud.
Automation inside one system: if everything happens within the CRM (status change → task), use the CRM's built-in scenarios — simpler and one less point of failure.
Where to start
The right sequence is not "install n8n" but finding the process where automation pays back fastest — usually wherever a person moves data between two systems by hand every day. We start with a free process audit: a 30-minute call produces a map of manual operations and an estimate of what can be automated and for how much. Then see a typical project at n8n automation services.