Self-hosted
Server on your infrastructure. Data never leaves the company.
UNIQUE ON UA MARKET
n8n automation: connect Planfix to anything
Our own company runs on n8n — over 60 production scenarios. We build the same setup for you, with no monthly Make/Zapier fees.
- Self-hosted n8n: no monthly licence fee
- 500+ ready integrations in catalogue
- Ukrainian services: Nova Poshta, Monobank, Checkbox
- AI scenarios: GPT lead-scoring, auto-reports
Free consultation
What is n8n in 1 minute
n8n (read «en-eight-en») is an open-source automation platform, similar to Make.com and Zapier. The key difference: you run it on your own server and don't pay $20-50/month per scenario.
No-code
Visual scenario builder. No developer needed for most tasks.
No limits
Run a million operations a day — no extra fees.
500+ integrations
Ready connectors for CRM, messengers, accounting, AI, databases.
10 working scenarios we have already shipped
Planfix → Telegram: auto-reminders to managers
Card stuck for 24 hours without activity — Planfix calls n8n via webhook, which messages the manager on Telegram with a link and deadline.
Planfix → Google Sheets: daily report to CEO
Once a day at 9 AM n8n pulls all open deals from Planfix, aggregates by manager and sends to Google Sheets + a copy to a leadership Telegram channel.
Planfix + Nova Poshta: shipment status in client card
TTN created → n8n polls Nova Poshta API every 30 min → updates field in Planfix. Client sees the status without manager involvement.
Planfix + ChatGPT: auto lead classification
New lead from website → n8n sends description to ChatGPT → gets category (hot/warm/cold) → tags Planfix card → pushes only hot leads to manager.
Planfix + Monobank: auto-record payments
Monobank webhook → n8n finds the deal in Planfix by payment comment → changes status to «Paid» → triggers shipment script. Saves 5-10 min per payment.
Inbox → task: triaging incoming mail
n8n pulls new emails, AI classifies them (request, invoice, spam, client reply), creates a task with a short summary and a draft reply. The manager opens an inbox that is already sorted.
CRM mirror in a database for reporting
Every CRM change flows into a separate database via webhook. From there — any report or dashboard, without loading the CRM itself or fighting its built-in analytics.
Meeting recording → summary and tasks
Audio from a meeting or call goes into n8n, AI transcribes it, extracts commitments and deadlines, and creates tasks for the owners. Nothing is lost between "we agreed" and "we did it".
Daily brief for the manager
Every morning n8n collects data from the CRM, mail and finances, and AI writes a short brief: what is burning, what is stuck, which deadlines slipped. One message instead of touring five systems.
Content plan and scheduled publishing
The scenario generates posts from the plan, assembles images, publishes to social networks and writes analytics back into a sheet. It has run for months without human involvement — it is our own production flow.
n8n vs Make vs Zapier
| Parameter | n8n (self-hosted) | Make.com | Zapier |
|---|---|---|---|
| Starter cost | Setup + server ~$5/mo | $10-30/mo | $20-50/mo |
| At scale cost | $5/mo (unlimited) | $300+/mo | $600+/mo |
| Data security | Your server | EU cloud | US cloud |
| Number of scenarios | Unlimited | Limited by plan | Limited by plan |
| Integration complexity | Any | High | High |
| Ukrainian services | Yes (via HTTP) | Limited | Limited |
| Open-source | Yes | No | No |
For Ukrainian SMB n8n wins on at-scale price and data security. Make/Zapier — faster start, but more expensive after 3-6 months.
We do not sell what we do not run ourselves
The entire operations of Integro run on n8n: over 60 production scenarios — from CRM and finance synchronisation to AI agents that prepare daily briefs and triage mail. So we speak from daily operation, not from documentation.
We know where it breaks
API limits, third-party outages, queues, retries, duplicates — we hit all of it on our own flows, not for the first time on your project.
Monitoring by default
Every scenario we hand over reports its failures to Telegram. A silent failure is the worst kind of automation.
Versions and recovery
Workflows are stored as code in git. Broke it — roll back; changed platform — move it.
Real volumes
Our scenarios process tens of thousands of events a month. This is not a demo on three records.
n8n automation packages
Basic
3-5 days
- 1 working scenario
- Setup on our server
- 1-h training
- 14 days of support
Standard
7-14 days
- Basic scenario package
- Self-hosted on your server
- PDF docs
- 2-h team training
- 30 days of support
- Monitoring Telegram channel
Custom
14+ days
- Extended scenario package
- AI agents (GPT, Claude, Gemini)
- CI/CD for workflows
- Highly-available infrastructure
- SLA 99.9%
- 90 days of support
Frequently asked questions
Who watches that a scenario has not broken?
Every scenario ships with error handling: if a step fails, a Telegram notification arrives with the flow name and the reason. Silent failures are unacceptable in automation that touches money and clients.
What happens to our data if the server dies?
Workflows are stored as code in a repository and the n8n database is backed up daily. Recovery means restoring a server and a backup, not rebuilding the automation from scratch.
We already have scenarios in Make or Zapier. Can they be moved?
Yes. We port the logic to n8n by hand — there is no automatic converter between platforms. It is usually faster than starting over because the process is already thought through, and we drop the steps that existed only to work around plan limits.
How much does a server for n8n cost?
For most small and mid-size workloads a VPS costing a few dollars a month is enough — that is the hosting bill, not ours. For large volumes or high-availability requirements we size it separately.
Can we start with a single scenario?
Yes, and we usually recommend exactly that: take one painful routine, automate it, measure the effect on real data. Then expand, already knowing where the biggest win is for you.
How is n8n better than Make.com or Zapier?
Self-hosted: data never leaves your control. At scale — 50-100x cheaper: $5/mo server vs $300-600/mo on Make/Zapier. Open-source — no vendor lock-in.
What if you stop supporting us?
n8n is open-source. Your workflows stay with you (export to JSON). Any other integrator can continue.
Who hosts n8n — you or us?
Depends on package. «Basic» — our server. «Standard» and «Custom» — yours (VPS from $5/mo or own infra). We set everything up and hand over access.
How long does one scenario take?
Simple (Telegram alert, field update) — 2-4 hours. Medium (logic, multiple steps) — 1-2 days. Complex (AI, custom code) — 3-7 days.
Can any service be connected?
Yes. If a service has API or webhook (95% of modern services do) — we connect it. We verify compatibility during audit.
Do we need an in-house IT specialist?
For launch — no, we deliver turnkey. For workflow modifications — handy to have someone with logical thinking. We train your employee as an «n8n operator».