Kommo automations without a developer (2026)
Most day-to-day automation in Kommo needs no programmer: in Digital Pipeline you attach a trigger to a stage (task, tag, stage change, email, webhook), and in Salesbot you assemble a flow from ready-made blocks. The three most common scenarios — a task on stage change, a reminder when a client goes quiet, and a Telegram notification for a won lead — take 10–30 minutes each with built-in tools. If you would rather not learn the builder, describe the rule in plain words and Kai will configure it through the official Kommo API.
TL;DR
- Digital Pipeline lives under Leads → Automate; each stage offers 12 trigger types and 5 delays: Immediately, End of the day, In 1 day, In 3 days, End of the week.
- Salesbot: flow builder, no step limit, Pause timer up to 8,760 hours; starts on a new message, a lead entering a stage, a change of owner, or a schedule. Not in the Base plan.
- No native "post to a Telegram group" action: internal message to a colleague, a webhook, or a Marketplace widget.
- An integrator typically takes 3–5 weeks. Kai: one chat message, from €29/month, 3 days free, no card.
What Digital Pipeline and Salesbot are
Digital Pipeline is automation tied to pipeline stages. Under every stage on the board you hang a rule: "when a lead lands here, do X". A rule can wait, check a condition (tag, owner, field value) and run one action.
Salesbot is a builder for multi-step flows. It does everything triggers do and also talks to the client in chats: messages with buttons, waiting for a reply, branching, tasks, webhooks. It starts as a Digital Pipeline trigger or on chat events. Menu labels below follow the official Kommo help.
What you can set up yourself
Digital Pipeline triggers per the official help: Salesbot, Add task, Create lead, Send email, Send webhook, Change lead stage, Add tags, Complete tasks, Generate form, Change lead's user, Change field, Delete files. Each trigger accepts conditions on responsible user, tags and fields; tick Apply the trigger to all leads already in this stage or the rule affects new leads only.
Salesbot blocks split into conversation steps (Message, Condition, Pause, Validation, Send internal message) and actions (Add task, Change lead status, Manage tags, Set field, Change responsible user, Send email, Send webhook, Widget, Round Robin). Templates make an easier start.
Scenario 1. A task for the manager when the stage changes
Manually in Kommo
- Open Leads → Automate.
- Under the stage you need, click "+" → Add trigger → Add task.
- Fill in the task text, type, responsible user and deadline (Immediately, End of the day, In 1 day, In 3 days, End of the week).
- Add a condition if needed (for example, only leads tagged "Hot") and save. Test on one lead first.
Same thing in amoCRM: Leads (Сделки) → Setup (Настроить) → "Add trigger" under the stage → "Create task".
With Kai
Kai asks back if the stage is named differently, shows the plan and creates the trigger via the API; the report stays in the chat history.
Scenario 2. A reminder when the client goes quiet
Manually in Kommo
Kommo has no dedicated "client did not reply" trigger, so there are two routes.
- Simple, no Salesbot. On the "Quote sent" stage add an Add task trigger due In 1 day: "No reply — call the client". If the client answers earlier, the manager closes the task.
- Precise, with Salesbot. Settings → Communication tools → Salesbots → Create a new bot. Chain: Message (follow-up text) → Pause waiting for an incoming message with a timer (say, 24 hours) → Add task for the manager. Then add a Salesbot trigger on the stage in Digital Pipeline and test the branching on a test chat.
With Kai
Kai sets up the task and the notification, and it watches the pipeline 24/7, flagging stalled leads in the daily report. A conversation flow with the client is still Salesbot territory: Kai drafts the steps, you assemble the blocks.
Scenario 3. A Telegram notification when a lead is won
Manually in Kommo
- Inside Kommo. A Salesbot launched when the lead enters Closed – won, with a Send internal message step. Only the selected user or team sees it inside Kommo, not an external Telegram chat.
- Via webhook. Add trigger → Send webhook on the won stage; your own Telegram bot or a connector (Albato, ApiX-Drive, Make, n8n, Zapier) formats the group message.
- Via a widget. Kommo Marketplace lists third-party Telegram notification widgets; pricing is set by each developer.
With Kai
Kai connects lead-to-Telegram, Slack, Google Sheets and webhook integrations without an intermediate connector and does not store lead data.
Limits you discover later
- Salesbot is not on the Base plan (per Kommo's pricing page at the time of writing); Digital Pipeline is in every plan.
- Trigger delays come from a fixed set; "in 2 hours" needs a Salesbot pause.
- Triggers react to stage events, not client behaviour. Conditions cover only responsible user, tags and fields.
- Without the "apply to leads already in this stage" checkbox the rule ignores current leads — the usual reason for "nothing happens".
- After 5–7 triggers nobody remembers what hangs where. Kai's pipeline audit exists to find those overlaps.
Comparison: yourself, integrator, connector, Kai
| Yourself in Kommo | Integrator | No-code connector | Kai | |
|---|---|---|---|---|
| Time | 10–30 min per scenario | Typically 3–5 weeks | Hours per link | Minutes per scenario |
| Cost | Included in the Kommo plan | Project fee, varies by market | Connector subscription | From €29/month |
| Skills needed | Learn the builder | Write a brief | Understand webhooks and fields | Describe the business in words |
| Who maintains it | You | Integrator under contract | You | Kai monitors 24/7, reports in chat |
| Best for | 1–3 simple rules | Complex logic, many systems | Links between services | Standard rules and integrations |
FAQ
Do I need a developer to set up Digital Pipeline in Kommo?
No. Digital Pipeline triggers and Salesbot flows are built by clicking in the Kommo interface. A developer is only needed for custom widgets or complex webhooks into external systems.
What is the difference between Salesbot and Digital Pipeline triggers?
A trigger is one action fired by a stage event: task, tag, email, webhook. Salesbot is a multi-step flow with client messages, pauses, conditions and the same actions inside. Salesbot is not included in the Base plan.
Does Kommo have a "client did not reply" trigger?
Not as a separate trigger. Silence is handled with a Pause step in Salesbot (wait for a message with a timer up to 8,760 hours) or a delayed Digital Pipeline task: In 1 day, In 3 days, End of the week.
How do I send a Telegram notification when a lead is won?
Natively: Send internal message (Kommo users only), Send webhook to your own bot or a connector, or a widget from Kommo Marketplace. Kai connects a lead-to-Telegram channel from a description in chat.
Does the same work in amoCRM?
Yes, Kommo is the international version of amoCRM. In amoCRM the path is Leads (Сделки) → Setup (Настроить) → "Add trigger" under the stage → "Create task". Kai works with both CRMs, plus Bitrix24 and custom CRMs with API documentation.
Does Kai replace an integrator?
For standard rules such as tasks, tags, stage moves, notifications and Telegram, Slack or Google Sheets integrations, yes. For complex logic with custom widgets and many external systems an integrator is still the right call; Kai will at least produce the brief as a PDF.
What next
Connect Kommo to Kai in one click via OAuth (widget listed in Kommo Marketplace, no API keys) and describe your first rule in your own words. Three days free, no card.