Source connector

Kommo connector

Kommo integration for databases, warehouses and BI tools

Conversational CRM for WhatsApp, chat funnels, and sales automation. Datrise captures Kommo entities such as conversational CRM events, chats, leads, and sales automation triggers, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

The Kommo API v4 (REST) authenticates with OAuth 2.0, personal access token, incremental runs key on updated_at, and Kommo caps calls at Not more than 7 requests per second; HTTP 429 when exceeded, and repeated violations block the IP so every request answers HTTP 403.

Of the 4 objects, 3 sync as upserts keyed on the primary key and 1 as append-only streams, so each incremental run moves only what changed since the last watermark. Every object lands in its own table (for example `kommo_conversational_crm_events`) with a schema derived from the Kommo API rather than a flattened CSV, in any of the 43 supported destinations.

Datrise is in early access: pick a destination below to open the Kommo pipeline page, and join the waitlist to get the Kommo connector (CRM) with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What Kommo data Datrise extracts

Each object lands in its own typed table. Sync mode is derived from the object: history-style objects append, everything else upserts.

Object	Landing table	Sync mode
conversational CRM events	kommo_conversational_crm_events	Append-only, incremental by timestamp
chats	kommo_chats	Upsert by primary key, incremental on updated-at
leads	kommo_leads	Upsert by primary key, incremental on updated-at
sales automation triggers	kommo_sales_automation_triggers	Upsert by primary key, incremental on updated-at

Kommo API: setup facts for the connector

Verified against the vendor documentation on 2026-10-05. Unknown values are left blank rather than guessed.

API	Kommo API v4 (REST)
Authentication	OAuth 2.0, personal access token — Public integrations use OAuth 2.0 authorization code (20-minute code, 24-hour access token, 3-month refresh token that is revoked if unused and stays valid until the new one is first used); private integrations can instead use an admin-generated long-lived bearer token (1 day to 5 years, no `refresh_token`, shown once at generation).
Pagination	page — `page`/`limit` query parameters with `limit` capped at 250 entities, HAL-style `_links.self` / `_links.next` hrefs in the body, and an empty page answered with HTTP 204 and no body.
Rate limit	Not more than 7 requests per second; HTTP 429 when exceeded, and repeated violations block the IP so every request answers HTTP 403
Incremental cursor	updated_at — List endpoints for leads and contacts accept `filter[updated_at][from]` / `filter[updated_at][to]` as Unix timestamps plus `order[updated_at]=asc`, so a sync can page forward from the last seen `updated_at`.
Webhooks	Yes — Webhooks (add_/update_/delete_/restore_/status_/responsible_ events for leads, contacts, companies and tasks, max 100 per account)
Bulk export	No
Deletes detectable	Yes — GET /api/v4/leads?only_deleted=1 lists leads still in the recycle bin as `id` + modification date + `is_deleted: true`; `delete_lead` / `delete_contact` / `delete_company` webhooks and GET /api/v4/events with `filter[type]=lead_deleted` (also `contact_deleted`, `company_deleted`) report deletes as they happen.

Official API reference

What bites when replicating Kommo

Exceeding 7 requests per second returns HTTP 429, and repeated violations block the calling IP so every subsequent API request answers HTTP 403, so a connector must throttle below the cap instead of retrying 429s in a tight loop.
List endpoints cap `limit` at 250 and answer an exhausted page with HTTP 204 and an empty body instead of an empty `_embedded` array, so a paginator that parses JSON on every response fails at the end of the collection.
Deleted leads stay visible only through `only_deleted` while still restorable, and that response carries just `id`, the modification date and `is_deleted: true`, so the full record must be captured before deletion or taken from the `delete_lead` webhook / `lead_deleted` event.
A webhook endpoint must answer with a 100-299 code within 2 seconds; more than 100 invalid responses in the last 2 hours disables the webhook, and an account may hold at most 100 webhooks in total.

Compare this against every other documented API

Popular destinations for Kommo

Choose a destination below to open the ready pipeline page.

A
Airtable
Relational spreadsheet destination for ops and go-to-market teams.
View pipeline
A
Amazon Athena
Serverless SQL over S3 data lake tables.
View pipeline
A
Amazon DynamoDB
Serverless key-value and document store on AWS.
View pipeline
A
Amazon QuickSight
AWS serverless BI with SPICE and embedded analytics.
View pipeline
A
Amazon Redshift
AWS petabyte-scale warehouse with Spectrum.
View pipeline
A
Amazon S3 Data Lake
Object storage landing zone for parquet and snapshots.
View pipeline
A
Apache Superset
Open-source BI for SQL exploration, charts, and dashboard publishing.
View pipeline
A
Azure Data Lake Storage
ADLS Gen2 object storage for analytics workloads.
View pipeline
A
Azure Synapse
Microsoft analytics workspace with SQL pools.
View pipeline

Kommo connector FAQ

What Kommo data does the connector extract?: 4 objects: conversational CRM events, chats, leads and sales automation triggers. Each lands in its own table with types preserved; history-style objects (1: conversational CRM events) load as append-only streams.
Is the Kommo integration incremental?: Yes. After the initial full load, every run reads only records changed since the last watermark (updated-at or event timestamp) and applies an upsert or an append depending on the object.
Where can I load Kommo data?: Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each Kommo → destination pair has its own page with the object-to-table mapping.

Related CRM sources

Other sources in the same category, each with its own connector page.

Early access

Launch your Kommo pipeline with guided onboarding

Join the waitlist to get priority access for Kommo integrations with guided setup, schema-aware mapping, and production-grade incremental sync.