Kommo + ClickUp: how to connect tasks and leads without Zapier

Kommo manages the sales pipeline, ClickUp manages operational tasks and projects. The combination is logical: a deal is won — a project is launched, a lead moves to the “Contract” stage — a task is created for the lawyer, a client pays — an onboarding checklist appears in ClickUp automatically. But there is no native integration between Kommo and ClickUp. The only available options are Zapier and Make, which add cost, delays, and points of failure. We break down how this is solved through a custom integration.

Why there is no native integration

Kommo does not have ClickUp in its integration marketplace. The only options are third-party automation platforms: Zapier, Make, Integrately, Albato. These solutions only cover basic scenarios:

• ✅ Creating a task in ClickUp when a lead is created in Kommo
• ✅ Basic status update when a task changes
• ❌ No two-way synchronization of custom fields
• ❌ No conditional logic — you cannot create different tasks depending on the pipeline stage or field value
• ❌ No direct linking of ClickUp Tasks to the lead card in Kommo
• ❌ Each additional scenario is a separate Zap with a separate cost
• ❌ 1–15 minute delays in data transfer through an intermediary
• ❌ When a Zapier scenario breaks, tasks simply are not created — without notifying the team

Typical scenarios that break without integration

Operational onboarding after deal close. A manager closes a deal in Kommo — someone needs to create an onboarding project in ClickUp, assign team members, set deadlines. Without integration this is manual work: the manager writes in Slack, the operations manager creates tasks manually. At a high deal-closing pace, some onboardings start with a delay or get lost.

Legal and financial tasks on a trigger. A lead moves to the “Contract” stage — a task is needed for the lawyer to prepare a contract. A lead moves to the “Invoice sent” stage — a task for accounting to track payment. Without automation, the manager creates these tasks manually or writes in the messenger.

Reverse synchronization: task progress -> deal stage. The lawyer completes the contract in ClickUp — the deal in Kommo should automatically move to the next stage. Without integration, the manager monitors ClickUp and manually updates Kommo. This is double effort and a source of errors.

What the Exceltic.dev custom integration solves

• Automatic task creation on pipeline stage change — when a lead moves to a specific Kommo stage, a task (or set of tasks) is automatically created in the correct Space/Folder/List in ClickUp
• Lead data passed to the task — company name, contact name, deal amount, Kommo custom fields are mapped to ClickUp Task Custom Fields
• Conditional task creation logic — different pipeline stages create different tasks: “Contract” → task for lawyer, “Payment” → task for accounting, “Won” → full onboarding project from template
• Two-way synchronization — changing the task status in ClickUp updates the stage or field of the deal in Kommo; completing a task can automatically move the lead to the next stage
• Direct link in the lead card — the ClickUp task URL is written to a custom field in the Kommo card; the manager opens the task with one click directly from the CRM
• Full project creation — when a deal closes, not just one task but an entire project with a set of subtasks, assignees, and deadlines is created based on a template
• Automatic assignee selection by rules — based on deal data (region, product, client size) the task is automatically assigned to the right assignee or team in ClickUp
• Comments and updates — new comments on the ClickUp task create a note in the Kommo lead card; the manager sees production progress without switching to ClickUp

How the integration works — technical process

Connection architecture

The integration is built on a two-way link: Kommo Webhooks → Exceltic middleware → ClickUp API v2 and ClickUp Webhooks → Exceltic middleware → Kommo API v4. Kommo sends events on lead stage changes and field updates. ClickUp sends events on task status changes and comment additions. Authentication with Kommo via OAuth2 + Long-lived Token. Authentication with ClickUp via Personal Token or OAuth.

Step-by-step scenario: deal close -> onboarding project

1. Manager moves lead to the “Won” stage in Kommo — webhook lead.status_changed is sent
2. Middleware receives lead data: company name, contact, amount, custom fields
3. Condition checked: stage = “Won” → trigger onboarding project
4. Project folder created in ClickUp: POST /api/v2/folder/{folder_id}/list with name Onboarding: {company_name}
5. Task set created from template: contract, account setup, kick-off call, training
6. Each task receives custom fields from lead data: Client Name, Deal Value, Manager
7. Tasks are assigned to team members according to mapping rules
8. Deadlines are calculated relative to the deal close date
9. URL of the created project is written to the Kommo lead custom field: PATCH /api/v4/leads/{id}
10. Manager sees the project link directly in the lead card

Step-by-step scenario: task completion -> lead update

1. Lawyer completes the “Contract preparation” task in ClickUp — status changes to Complete
2. ClickUp sends webhook taskStatusUpdated
3. Middleware identifies the linked lead by task_id from the mapping table
4. Rule checked: “Contract” task completed → move lead to “Contract signed” stage
5. Kommo API updates the lead stage: PATCH /api/v4/leads/{id}
6. Note created in the lead card: “Contract prepared by lawyer [name] — [date]”
7. If all required project tasks are completed — lead automatically moves to the next stage

What happens on error

Both Kommo and ClickUp support retry logic for webhook delivery. The middleware uses idempotency keys based on lead_id + stage_id combination for Kommo and task_id + status for ClickUp — repeated events do not create duplicate tasks or updates. When the ClickUp API is unavailable, events are saved to a queue with exponential backoff.

Real case

Web studio, 8 people, ~15 new projects per month, Kommo for sales, ClickUp for production.

The studio closed deals in Kommo, after which the project manager manually created a project in ClickUp: copied client data, laid out tasks from a template, assigned the designer and developer. This took 20–30 minutes per new project. At 15 projects per month — that is 5–7 hours of operational work just at the start.

An additional problem: the sales manager could not see production progress without switching to ClickUp. A client asked “how are things going?” — the manager went to ClickUp, checked the status, came back to Kommo. Double context switching for every client question.

After connecting the custom integration: closing a deal in Kommo automatically creates a full project in ClickUp with tasks, assignees, and deadlines. The project URL appears in the lead card. Completion of key tasks updates the deal stage. The manager sees production status without leaving Kommo.

Result: 6 hours per month returned to the project manager, the sales manager answers client questions without switching to ClickUp, 0 lost onboardings.

Which businesses benefit most

The integration is most relevant for service companies and agencies where sales are managed in a CRM and production or operations are managed in ClickUp: web studios, marketing agencies, IT teams, consulting companies. The transition of a deal from “Sales” to “Production” is the key moment that should automatically trigger operational processes.

It is critically important for teams with clear separation of roles between sales and operations — when the sales manager should not touch ClickUp and the operational team does not work in Kommo. The integration ensures visibility of progress for both sides without needing to switch between systems.

Frequently asked questions

Why is there no native Kommo and ClickUp integration? Kommo supports native integrations with a limited list of task management tools — mainly through its own built-in task manager. ClickUp is not in the list of Kommo’s native integrations. The official recommendation is to use Zapier, which adds cost and limitations.

Why is a custom integration better than Zapier for the Kommo and ClickUp connection? Zapier only supports linear triggers without conditional logic and custom field mapping. A custom integration supports: conditional task creation based on stage and field values, two-way synchronization, project creation from templates, writing the task URL to the lead card. Plus: no additional monthly Zapier cost and no synchronization delays.

Can different tasks be created for different pipeline stages? Yes. For each Kommo pipeline stage, its own rule is configured: which tasks to create, in which ClickUp List, who to assign, with what deadline. For example: “Contract” stage → lawyer task for 2 days, “Invoice sent” stage → accounting task for 3 days, “Won” stage → full onboarding project from template.

Does the integration support multiple Kommo pipelines? Yes. Each Kommo pipeline can have its own task creation rules in ClickUp — different Lists, different task templates, different assignee routing rules.

How long does it take to develop the Kommo and ClickUp integration? Basic integration with task creation on stage change and field transfer — 3–4 business days. Version with two-way synchronization, project creation from templates, and conditional routing — 6–8 business days. Exceltic.dev determines exact timelines after a technical brief.

If you want to connect Kommo and ClickUp without Zapier and unnecessary intermediaries — describe your task to the Exceltic.dev team. We will analyze your pipeline structure and task templates for your operational process.