Kommo + n8n: Sales Pipeline Automation Without Zapier

If your Zapier bill is growing faster than your deal count, pairing Kommo with self-hosted n8n fixes the problem at the root: you pay for a server, not for every single action. Kommo sends a webhook to n8n on any pipeline event, the workflow processes the data according to your logic, and writes the result back through the Kommo API. No per-operation billing, full control over your data, any custom logic without workaround hacks.

At Exceltic.dev we move clients off Zapier and Make onto self-hosted n8n once their automation volume crosses a couple of thousand tasks per month. At that mark, a tidy Zapier template turns into a cost line item that your CFO notices before you do. The difference is not cosmetic: on complex multi-step scenarios, self-hosted n8n costs 80-90% less at the same volume, because the billing model is fundamentally different.

The Operational Pain: Why Zapier Stops Paying Off

Three reasons teams at scale hit a wall with Zapier.

Pricing grows non-linearly. Zapier bills every step as a separate “task.” A 10-step pipeline run 10,000 times a month is 100,000 billable tasks. In the same situation, n8n counts 10,000 executions, because one workflow run equals one unit regardless of the number of steps. That is where the pricing gap comes from, reaching up to 90% at scale.

No control over your data. Leads, phone numbers, deal amounts all pass through Zapier’s infrastructure. For teams with data localization requirements or internal security policies, that is a blocker. Self-hosted n8n runs on your own VPS - your data never leaves your perimeter.

Plan limits and ceilings. Polling frequency, task counts, access to advanced steps - everything is capped by your plan. When a scenario gets more complex, you either pay for the next tier or break your logic against the connector’s limits.

Why Teams Move From Zapier to n8n

The main argument is the billing model. Zapier charges per task (step), n8n per execution (a full workflow run). The more steps in a scenario, the more n8n pays off.

The self-hosted Community Edition is free and gives you an unlimited number of executions. The real cost is the VPS, usually 4-7 dollars a month for a machine that handles dozens of pipelines. For comparison: a team hitting Pro-level volumes (around 10,000 executions a month) pays 300+ dollars a month on Zapier Professional for the equivalent.

The break-even point sits at roughly 15,000 tasks a month. Below it, Zapier wins on total cost of ownership - you do not need to run and maintain a server. Above it, self-hosted n8n wins decisively, and the more complex the scenarios, the wider the gap.

The second argument is openness. Self-hosted n8n is your server, your database, your logs. You can connect any HTTP API through the universal HTTP Request node, write arbitrary JavaScript right in the Code node, and version your workflows in git. Zapier does not give you that freedom by design.

What You Can Build With Kommo + n8n

The integration is built on three elements: the Kommo webhook, the n8n workflow, and write-back through the Kommo API.

Self-Hosted: Your Server, Your Data

n8n deploys on a VPS via Docker in a single evening. From there it is entirely your infrastructure: deal data does not go to a middleman, execution logs live with you, access is controlled by your own tools. For teams operating outside the CIS whose clients are in the US and Europe, this removes any question about whose jurisdiction lead personal data passes through.

Kommo Webhook -> n8n Workflow -> Write-Back

The scenario works like this. In n8n you create a Webhook node - it issues a unique URL. That URL goes into the Kommo settings (the webhooks section in your account settings). Now any tracked event in Kommo - a new deal, a stage change, a contact update - sends a POST request to your workflow.

An important detail about Kommo: the service waits for a webhook response within 2 seconds. If the response does not arrive in time, or the response code is outside the 100-299 range, the webhook is considered undelivered. If more than 100 invalid responses pile up within 2 hours, Kommo will disable the webhook. The architectural takeaway: n8n should respond to Kommo immediately (a Respond to Webhook node with a 200 code) and perform the heavy processing asynchronously, after the response. That way you do not run into the timeout on slow steps.

Write-back goes through the Kommo API. After processing, the workflow triggers an HTTP Request node that sends a PATCH or POST to Kommo’s endpoints - update a deal field, move a stage, create a task, append a note. Authorization uses a long-lived integration token.

Data Control, No Per-Task Billing, Custom Logic

What this gives you in practice:

• No per-operation billing. No matter how many steps are in the workflow, it counts as one execution. Enriching a lead from five sources costs the same as sending a single email.
• Any logic. Branching, loops, external API calls, parsing, LLM requests, writing to your own database - all in one workflow. The Code node accepts arbitrary JavaScript when the standard nodes are not enough.
• Data under control. Nothing leaks to a third-party SaaS. Logs and execution history are yours.

Kommo is not on n8n’s list of built-in connectors, but that is not a problem: the universal HTTP Request node works with the Kommo API directly. For those who prefer visual nodes, there is a third-party community package, n8n-nodes-kommo, with OAuth authorization through the Kommo widget.

How It Works, Step by Step

1. Deploy n8n on a VPS. Docker image, domain, SSL. A machine for 4-7 dollars a month is enough to start.
2. Create a Webhook node in n8n. Copy the generated URL. For production use the Production URL, not the Test one.
3. Register the webhook in Kommo. Account settings -> webhooks section -> paste the URL and select events (deal creation, stage change, contact update). Working with webhooks via the API is available on the Advanced, Pro, and Enterprise plans.
4. Respond with 200 immediately. Put a Respond to Webhook node at the start to stay within Kommo’s 2-second limit, and move processing further down the branch.
5. Build the processing logic. Filters, enrichment via external APIs, checks, branching - as many steps as you need. It does not affect the price.
6. Write the result back through the Kommo API. An HTTP Request node with a PATCH or POST method to the right endpoint - update a field, move a stage, create a task or a note. The integration token goes in the authorization header.
7. Enable and test. Run a test event, check the execution history in n8n, and make sure Kommo receives a valid response and does not flag the webhook as failing.

If you are still setting up the pipeline itself before automating it, start with the basics - we have a breakdown of how to set up a pipeline in Kommo CRM, and an overview of Kommo CRM features that come out of the box.

A Real Case With Numbers

A team on Zapier: a lead enrichment pipeline of 8 steps (receive webhook, check for duplicate, request to an enrichment service, normalize, write to Kommo, notify in Slack, log to Google Sheets, create a task). Run about 12,000 times a month.

On Zapier that is 8 steps times 12,000 runs = 96,000 tasks a month. That volume requires a Professional-level plan, in practice 300-500 dollars a month depending on the exact volume and plan.

On self-hosted n8n the same scenario is 12,000 executions. The Community Edition is free, and there is no per-step billing. The real expense is the VPS, say 10-20 dollars a month with headroom for several pipelines like this.

Rough arithmetic: the switch saves around 280-480 dollars a month on a single pipeline, or roughly 3,400-5,700 dollars a year. The one-time cost of deployment and migration pays for itself within the first or second month. The more steps in your scenarios and the higher the volume, the faster the payback.

An honest caveat: to the self-hosted cost you need to add maintenance time - n8n updates, server monitoring, backups. If there is no one on the team ready to handle that, count those hours into the cost of ownership.

Who It Fits, and Who Is Better Off With Zapier

Kommo + self-hosted n8n is your option if:

• Automation volume is above 15,000 tasks a month or is clearly trending that way.
• Scenarios are multi-step - 5+ steps per run, where the per-task model hits your wallet hardest.
• There are data control requirements: localization, security, avoiding third-party SaaS in the lead processing chain.
• The team has an engineer who can deploy Docker and keep an eye on the server.
• You need non-standard logic that runs into the limits of ready-made connectors.

Zapier (or n8n Cloud) is enough if:

• Volume is below the break-even point - roughly up to 15,000 tasks a month.
• Scenarios are simple, one or two steps.
• There is no resource to run infrastructure, and total cost of ownership including engineer time comes out higher than the subscription.
• Speed to launch matters more than savings: an off-the-shelf connector is up in minutes.

If you are only just considering Kommo as a CRM for your pipeline, start with the Kommo CRM overview - it covers who the system fits and where its limits are.

Term: execution in n8n is one full workflow run from trigger to finish, regardless of the number of steps inside. Load and (on paid plans) billing are counted by executions, not by steps. That is the key difference from Zapier, where the billing unit is a task - a single step in a scenario.

Frequently Asked Questions

Do you need a paid Kommo plan for webhooks? Yes. Working with webhooks via the API is available on the Advanced, Pro, and Enterprise plans. The basic plan does not have this capability.

What happens if n8n does not respond to Kommo within 2 seconds? Kommo will consider the webhook undelivered. If more than 100 invalid responses pile up within 2 hours and the last one is invalid too, Kommo will disable the webhook. That is why you should respond with 200 immediately and move processing into the asynchronous part of the workflow.

Can you manage without a custom node for Kommo? Yes. The universal HTTP Request node works with the Kommo API directly - both for receiving events and for write-back. The n8n-nodes-kommo community package is a convenience, not a necessity.

How much does self-hosted n8n really cost? n8n Community Edition itself is free with an unlimited number of executions. You pay for the VPS - usually from 4-7 dollars a month for a basic machine, more for high load. Plus budget engineer time for maintenance.

How reliable is it compared to Zapier? Self-hosted reliability depends on your server and maintenance. Zapier takes infrastructure off your hands, but charges you money and data control for it. For high-volume teams with an engineer on board, self-hosted n8n is stable and predictable in cost.

Bottom Line

Kommo + self-hosted n8n is a shift from paying per action to paying for a server. At volumes above 15,000 tasks a month and on multi-step scenarios, savings reach 80-90%, and your data stays within your perimeter. The price of admission is having an engineer who can deploy Docker and keep an eye on the server. Below that volume, on simple scenarios, Zapier or n8n Cloud remain a reasonable choice on total cost of ownership.

If automation volume in Kommo has grown to the point where Zapier has become a noticeable expense, at Exceltic.dev we design and deploy the Kommo + n8n integration for your pipeline - from webhook architecture to write-back through the API. Reach out, and we will go through your scenario and calculate the savings on your own numbers.

Useful links: n8n Webhook node documentation, Kommo webhooks documentation.