Resources · Zapier integration

Kommo Zapier integrationAutomate Kommo with Zapier.

The Kommo Zapier integration gives you 11 triggers, 12 actions and 6 searches on your leads, contacts, companies, tasks and notes. Every trigger is instant, the app is open on the free plan, and this page shows what each step costs and where it breaks.

See the 29 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Kommo Zapier integration actually does for your pipeline

Kommo is a CRM built around conversations with your customers, and Zapier is the tool that wires it to the rest of your software without code. The integration lets a change in Kommo (a lead, a contact, a task) start an automation, and lets other apps write back into Kommo: create a deal, update a contact, drop a note, assign a task.

Three results teams usually want first. No lead without a next step: New Lead starts the automation and Create Task hands the rep a follow-up, so nothing sits untouched in the first column. A clean record from a form: a sign-up in another tool goes through Find or Create Contact, then Create Lead attaches the deal to the right person instead of a duplicate. A pipeline that reports itself: Lead Status Changed fires when a deal moves to a new stage, and the next step can log it, alert a manager or push the figure into a sheet.

What Zapier does not do here matters just as much. It cannot delete a lead, a contact or a company: no action on this app removes anything. It does not read the history either. A Zap reacts to what happens after you switch it on, so the leads you already have stay where they are. And the editor only offers what the app exposes, so a pipeline setting with no action stays a manual job in Kommo.

If you are still weighing the tool itself, our Zapier review covers it in depth. The same CRM also has its own page on the other platform: Kommo Make integration.

Vocabulary

Zapier vocabulary in one minute

Seven words come back on every line of this page. Here they are in plain English, once.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run each time that trigger event happens.
Trigger
The event in an app that starts the Zap, like a new lead in Kommo. Once the Zap is on, Zapier waits for it.
Action
What the Zap does after it starts: the step that writes, sends or moves something for you, such as creating a task.
Task
The unit Zapier bills: one action your Zap completes successfully. The number on your plan counts exactly these.
Instant vs polling
An instant trigger is reported by the app the moment the event happens. A polling one is checked by Zapier on a timer.
Filter
A step that lets the Zap continue only when what arrived meets your condition, and quietly stops it otherwise.
Search step
A step that looks up something already in an app, like an existing contact, so later steps can reuse what it found.
Cost

What a Kommo Zap really costs

The trigger is free. Looking for new events is free. Only an action that works costs a task, and an action that fails is not counted.

  • TriggerCosts no task
  • Each successful action1 task
  • Free plan100 tasks a month, two-step Zaps only
  • Kommo on the free planAvailable

A Zap with three actions uses three tasks per run, so count your steps before you count your leads. The free plan gives 100 tasks a month and unlimited Zaps, but only two-step Zaps: one trigger, one action. Add a filter, a search or a second action and you need a paid plan. Kommo itself is not a paid-only app on Zapier. The interval grid below only concerns polling triggers; every Kommo trigger is instant, so it never slows you down.

Connect

Connect your Kommo account in three steps

  1. 01

    Open your connections

    In Zapier, go to the Apps page of your account and click + Add connection. A connection is your Kommo account linked to Zapier once, then reused by every step that touches Kommo.

  2. 02

    Pick Kommo

    Type Kommo in the search box of the dialog that opens, select it in the results, then click Add connection. A new browser tab opens on the Kommo side, where the sign-in happens.

  3. 03

    Sign in and grant access

    Log in to Kommo in that tab and allow Zapier to reach the account. You need read or write access on the leads, contacts and tasks you do not own yourself but want the Zap to touch.

First Zap

Your first Zap: a task when a deal changes stage

GoalWhen a lead moves to a new stage, create a call task for the owner, but only for the stages that matter.

  1. 01

    Build the trigger

    Create a Zap, choose Kommo and the Lead Status Changed event, then pick your connection. This trigger is instant, so the editor shows a lightning bolt next to it.

  2. 02

    Test it on a real deal

    Run the trigger test. Zapier brings back the three most recent items from your Kommo account, and you pick one to map the next steps on real data, not on placeholders.

  3. 03

    Add the filter

    Click the plus icon, add Filter, then set the field to watch, the rule and the value. Use a text rule on a stage name: the wrong rule type is why filters never pass.

  4. 04

    Add the action

    Add Kommo again with Create Task and map the lead from the trigger into it. The filter makes this a multi-step Zap, so this one needs a paid plan.

  5. 05

    Test, then publish

    Test the action once and check the task in Kommo. When it looks right, click Publish to switch the Zap on. It will react to the next stage change, not to past ones.

Triggers

Kommo triggers: 11 events, all instant

11 events start a Zap when something happens in Kommo, and 11 of them are instant: the app calls Zapier straight away, whatever your plan.

1

New Company

Instant trigger

In Zapier“Triggers when a new company is created.”

Starts your Zap each time someone adds a company record in Kommo, whether a rep typed it by hand or another step created it. You get the fresh account to pass on to your billing tool, your shared drive or a welcome sequence.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a B2B agency opens a client folder the minute a new account appears in the CRM.
Watch out
if another Zap creates companies in Kommo, this one fires on those too, so check you are not building a loop.
2

New Contact

Instant trigger

In Zapier“Triggers when a new contact is created.”

Fires on every person added to Kommo, from a chat, an import or a form. That makes it the natural entry point for anything that should follow a new contact: a newsletter list, a support tool, a welcome email sent from another app.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
push each new contact into your email marketing tool so the list never lags behind the CRM.
Watch out
a bulk import of contacts sends a big batch at once, and Zapier can hold it back as a flood.
3

New Lead

Instant trigger

In Zapier“Triggers when a new lead is created.”

One of the triggers Zapier puts forward for Kommo, and the most used for a reason: every deal opened in the pipeline starts the Zap. You decide what a new lead deserves straight after, a task, a Slack ping, a row in a reporting sheet.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
make sure every inbound deal gets a first call task assigned before anyone forgets it.
Watch out
leads that existed before you published the Zap are not picked up, so clean up the backlog separately.
4

New Task

Instant trigger

In Zapier“Triggers when a new task is created.”

Reacts when a task is created in Kommo, by a person or by an automation. Useful when tasks live in the CRM but people actually work from a calendar, a to-do app or a team chat, and you want the task to show up where they look.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
copy each new CRM task into the shared calendar of a sales team that lives in its agenda.
Watch out
pair it with Create Task in the same Zap and each new task makes another one.
5

Task Deleted

Instant trigger

In Zapier“Triggers when a task is deleted.”

Fires when someone removes a task in Kommo. It is the only removal Zapier lets you react to on this app, which makes it handy to keep a mirrored to-do list honest instead of leaving ghost items behind.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
clear the matching entry in an external task board when a rep deletes the task in the CRM.
Watch out
Zapier has no Kommo action that deletes anything, so the cleanup has to happen in the other app.
6

Lead Responsible User Changed

Instant trigger

In Zapier“Triggers when lead responsible user is changed.”

Starts the Zap when a deal changes hands, meaning the user responsible for the lead is swapped. That moment is easy to miss in a busy pipeline, and it is often where a handoff between two reps goes wrong.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
warn the new owner in your team chat with a link to the deal as soon as it is reassigned.
Watch out
a mass reassignment, after someone leaves, fires once per lead and can use a lot of tasks in one go.
7

Lead Status Changed

Instant trigger

In Zapier“Triggers when lead status is changed.”

Fires each time a lead moves from one pipeline stage to another, and Zapier features it among the key Kommo events. It is the trigger to watch for wins, losses and every stage that should set something off.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
send won deals to your invoicing tool and nothing else, with a filter on the stage.
Watch out
without a filter, every stage move runs the actions and costs tasks, including the moves you do not care about.
8

Company Updated

Instant trigger

In Zapier“Triggers when company is updated.”

Runs when a company record is edited in Kommo. It keeps a second system aligned with the CRM, so a corrected address or a new account manager does not stay stuck in one tool while the other carries the old version.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
sync account changes into the accounting tool your finance team trusts.
Watch out
never pair it with Update Company on the same record, or the Zap edits, retriggers and edits again.
9

Contact Updated

Instant trigger

In Zapier“Triggers when contact is updated.”

Fires whenever a contact card changes in Kommo, a new phone number, a fresh email, a tag added by a rep. Handy when the CRM is the reference and several tools need to follow its version of the person.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
update the subscriber in your mailing tool when sales corrects an address.
Watch out
edits come often on a busy contact base, and each run that reaches an action costs a task.
10

Lead Updated

Instant trigger

In Zapier“Triggers when lead is updated.”

The broadest of the lead triggers, and one Zapier features: any edit on a deal starts the Zap, not only a stage move or a new owner. Use it when the change you care about is a value, a tag or a custom detail on the lead.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
refresh a forecast sheet each time a rep revises the amount of a deal.
Watch out
it fires on edits you did not have in mind, so add a filter or you will pay for noise.
11

Task Updated

Instant trigger

In Zapier“Triggers when task is updated.”

Watches existing Kommo tasks for edits, such as a new due date, a new assignee or a completed status. It closes the loop when the CRM tasks are mirrored somewhere else and need to stay in step with the original.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
tick off the matching card in a project board once the rep marks the task done.
Watch out
combined with Update Task on the same task, it feeds itself and burns your task count.
Actions

Kommo actions: what a Zap can write into your CRM

Kommo gives you 12 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Create Company

Action

In Zapier“Creates a new company.”

Adds a new company to Kommo from whatever started the Zap, so the account exists before anyone opens a deal on it.

When to use it
a signed contract in your e-signature tool opens the matching account in the CRM.
Watch out
it does not check for an existing company, so put Find or Create Company in front if duplicates scare you.
2

Update Company

Action

In Zapier“Updates a company.”

Edits an existing company record in Kommo, so another tool can correct or enrich the account without anyone retyping it.

When to use it
your billing tool writes the latest subscription tier back onto the account.
Watch out
the Zap must know which company to edit, which usually means a Find Company step first.
3

Create Contact

Action

In Zapier“Creates a new contact.”

Writes a new person into the CRM from a form, a webinar sign-up or a shop order. Zapier lists it among the featured Kommo actions.

When to use it
every attendee registered on your webinar tool lands in Kommo before the session starts.
Watch out
run twice on the same email, it creates two cards; the find-or-create variant avoids that.
4

Update Contact

Action

In Zapier“Updates a contact.”

Changes the details of a person already in Kommo, keeping the CRM version in line when the truth lives elsewhere.

When to use it
an unsubscribe in your mailing tool gets flagged on the contact so sales stops cold emails.
Watch out
triggered by Contact Updated on the same contact, it loops.
5

Create Lead

Action

In Zapier“Creates a new lead.”

Opens a deal in your Kommo pipeline, the most common way to turn an outside event into sales work. Zapier lists it among the featured actions.

When to use it
a quote request on your site becomes a lead in the first stage, ready for a rep.
Watch out
the lead arrives on its own; link it to a person with Create Link or use the next action instead.
6

Create Lead With Contact

Action

In Zapier“Creates a new lead with contact.”

Creates the deal and the person in one go, already tied together, which saves a step and a task compared to two separate actions.

When to use it
an inbound demo request where the contact is almost always new to your CRM.
Watch out
it always creates and never looks first. When the person may already be in Kommo, start with Find or Create Contact, then Create Lead.
7

Update Lead

Action

In Zapier“Updates a lead.”

Edits a deal that already sits in the pipeline: its stage, its owner or its details, depending on what you map.

When to use it
a paid invoice in your accounting app moves the matching lead forward without a rep touching it.
Watch out
point it at the right lead with Find Lead, or you edit the wrong deal.
9

Create Note

Action

In Zapier“Creates a new note.”

Drops a note on a Kommo record, which is how outside context reaches the people who read the CRM all day.

When to use it
paste the answers of a qualification survey on the lead so the rep reads them before the call.
Watch out
a note needs a record to sit on, so a search step often comes first to find it.
10

Update Note

Action

In Zapier“Updates a note.”

Rewrites a note that already exists, handy when a single running summary is better than a pile of small notes.

When to use it
keep one status note per lead refreshed from your project tool.
Watch out
finding the note to edit relies on Find Note, which only covers notes on contacts and leads.
11

Create Task

Action

In Zapier“Creates a new task.”

Puts a to-do in Kommo for a user, so the next human move is never left to memory. It is the action behind most follow-up Zaps.

When to use it
schedule a call back each time a trial user hits a usage milestone in your product.
Watch out
used after New Task, it can generate tasks endlessly.
12

Update Task

Action

In Zapier“Updates a task.”

Edits a task already in Kommo, for example its due date or the person in charge, so a change made elsewhere shows up in the CRM.

When to use it
a meeting moved in the calendar pushes the matching CRM task to the new day.
Watch out
do not combine it with Task Updated on the same task.
Searches

Kommo searches: find before you write

6 search steps look for data that already exists in Kommo, so a later step can use it.

A search step looks for something already in Kommo and hands it to the steps that follow. In the editor, searches sit at the bottom of the event list under SEARCH, and some fields offer a + Add search step button that wires one in for you. A search makes the Zap multi-step, so it needs a paid plan. Three settings decide what happens when the result is not the clean single match you hoped for.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap there. Switch it on and the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    Ticking it turns the search into a find-or-create: it asks for the fields needed to create the missing record and drops the previous setting.
  3. If multiple search results are found?
    Keep the first match (the default), stop the Zap, or hand every match on at once.
When it breaks

When a Kommo Zap breaks

Most failures on this app are not errors on screen. They are Zaps that do too much, or not what you expected.

Kommo has no app-specific limit published on its Zapier page, so the traps below come from how Zapier behaves with any CRM. When a Zap misbehaves anyway, our Zapier troubleshooting page walks through the usual suspects.

  • Your old leads are not picked up

    A Zap only reacts to what happens after you publish it. Leads, contacts and tasks already in Kommo stay untouched; moving that backlog is a separate job.

  • The Zap that feeds itself

    Lead Updated plus Update Lead on the same deal edits, retriggers and edits again. The loop eats your task count fast, so keep the trigger and action on different records.

  • A bulk import held back

    Importing hundreds of contacts or reassigning a whole pipeline sends a huge batch at once. Zapier's flood protection can hold it back.

  • A search that stops everything

    If Find Contact or Find Lead returns nothing and the setting is left on its default, the Zap stops there and the steps after it are skipped.
Need help

Need help automating Kommo with Zapier?

A person reads every message.

FAQ

Kommo Zapier integration: questions people ask

01Is the Kommo Zapier integration free?
Yes, on a simple scale. Kommo is not reserved to paid plans on Zapier, so a free account can connect it and run Zaps. The free plan includes 100 tasks a month and unlimited Zaps, but every Zap must stay at two steps: one trigger and one action. As soon as you add a filter, a search such as Find Contact, or a second action, the Zap becomes multi-step and needs a paid plan. Most useful Kommo setups end up there, because a search before writing is what keeps duplicates out of the CRM.
02How many tasks does a Kommo Zap use?
One task per action that succeeds, and nothing for the trigger. A Zap that turns a new lead into a Kommo task uses one task per lead. Add a note and a message to the same Zap and that becomes three tasks per lead. An action that fails is not counted. The real risk on this app is volume: triggers like Lead Updated or Contact Updated fire on every edit, so without a filter you pay for changes that did not need any action at all.
03Is the Kommo Zapier integration real time?
Yes. All 11 Kommo triggers are instant: Kommo tells Zapier the moment the event happens, and the Zap starts right away. The interval grid of the plans (15 minutes on Free, 2 on Professional, 1 on Team and Enterprise) only applies to polling triggers, and Kommo has none. That makes this one of the rare cases where a free plan reacts as fast as a paid one. In the editor, the lightning bolt next to the trigger confirms it.
04What does it take to connect Kommo to Zapier?
A Kommo account and a Zapier account. From the Apps page in Zapier, you add a connection, pick Kommo, sign in on the tab that opens and grant access. The account you connect also needs read or write access on any records you do not own but want the Zap to touch. A rep account with limited rights will connect fine, then fail on leads it cannot see, which is a common surprise in teams where pipelines are split by person.
05Why does Find Note skip notes on companies?
Because the search only covers contacts and leads. Find Note requires an Element Type, and Kommo only offers those two for it. Notes attached to a company or a task cannot be found from Zapier, so any Zap built on them needs another route. If your team stores account history on companies, write new notes on the lead instead, where both Find Note and Update Note can reach them later.
06What if the Kommo operation you need is not listed?
Then Zapier cannot do it on this app today. The editor only offers the 11 triggers, 12 actions and 6 searches that Kommo exposes, and none of them deletes a lead, a contact or a company. The usual way around a gap is to combine what exists: a search plus an update often replaces a missing action. When nothing combines, the step stays manual in Kommo, or you look at another automation platform that may expose a different set of operations.
07Zapier, Make or n8n for Kommo?
It depends on criteria, not on a winner. Check first that the exact Kommo operations you need exist on the platform. Then compare how each one bills a run, since Zapier counts one task per successful action. Weigh who will maintain the automation and how often it will change. Finally look at volume, because a busy CRM with many edit triggers changes the bill fast. On Zapier, also keep in mind that a filter or a search makes the Zap multi-step, which already means a paid plan.
Same platform

Other docs you might need on this stack.

Browse all integrations