Kommo

Kommo

This connector works with one Kommo CRM account through the API v4 (https://<subdomain>.kommo.com/api/v4): leads with pipelines and stages, contacts, companies, custom fields, tasks, notes, users and the account's event log. It can create and update leads, create contacts and tasks, and add notes. It authenticates with a long-lived token of a private integration in your own account.

amoCRM accounts: Kommo is the international edition of amoCRM. An account whose address ends in .amocrm.ru (or the old .amocrm.com, which forwards there) is not reachable through this connector: install the amoCRM connector instead.

Setup (account administrator, about 3 minutes)

1. In Kommo open Settings → Integrations and click Create integration (top right). Choose a private integration, leave Redirect URL empty, keep the access scopes you need and Save.
2. Open the integration's Keys and scopes tab and click Generate long-lived token. Pick an expiry date and copy the token right away: Kommo shows it only once.
3. Paste it into KOMMO_ACCESS_TOKEN, and your account's subdomain into KOMMO_SUBDOMAIN: for https://acme.kommo.com enter acme.
4. The token acts as the administrator who created it. Revoke it on the integration's Authorization tab; when it expires, generate a new one.

Read-only setup: Kommo tokens cannot be limited to reading, so switch off kommo_create_lead, kommo_update_lead, kommo_create_contact, kommo_create_task and kommo_add_note. Nothing in this connector deletes data.

Ids and values: every id is an integer. Lead stages are status_id values inside a pipeline_id from kommo_list_pipelines; 142 is Closed-won and 143 Closed-lost in every pipeline. Responsible users come from kommo_list_users. Phone, email and all other extra data live in custom_fields_values: [{"field_id": 123, "values": [{"value": "..."}]}], select options by enum_id, contact phone and email by field_code PHONE or EMAIL with enum_code such as WORK; kommo_list_custom_fields lists ids and options. Dates are Unix timestamps in seconds. Linked entities are in _embedded; add with=contacts (leads) or with=leads (contacts) to get them.

Notes and events: kommo_list_notes reads one record's timeline; kommo_list_notes_by_type reads the notes of all leads, contacts or companies at once, filtered by note type, record ids or update time (e.g. every call logged this week). kommo_list_events reads the account's event log: stage changes (lead_status_changed), new records, field and responsible-user changes, calls, chat messages, completed tasks. Its entity filter uses singular names (lead, contact, company, task), unlike the other tools.

Pagination: list tools take page (from 1) and limit (up to 250; 100 for kommo_list_events). The response's _links.next shows that more exists; an empty answer (HTTP 204, no body) means there are no results or no more pages.

Rate limits: at most 7 requests per second per account. Over it Kommo answers 429; repeated violations block the IP address with 403 for every call. Avoid paging through all leads when a filter or search does the job.

Errors: 401 means the token is wrong, expired or revoked: generate a new one. 402 means the account's subscription has lapsed. 403 can mean the token's user lacks rights or the IP was blocked after too many requests. 404 is a wrong id or subdomain. 400 lists the invalid fields under validation-errors, for example a stage that does not belong to the pipeline or a custom field value of the wrong type.

Out of scope here: deleting entities, unsorted (incoming) leads, chats and messages, lists (catalogs), webhooks and Salesbot.