amoCRM

amoCRM

This connector works with one amoCRM account on amocrm.ru through the API v4 (https://<subdomain>.amocrm.ru/api/v4): deals (leads) with pipelines and stages, contacts, companies, custom fields, tasks, notes, users and the account's event log. It can create and update deals, create contacts and tasks, and add notes. It authenticates with a long-lived token (долгосрочный токен) of an integration in your own account.

Which connector: amoCRM and Kommo are the same product. Accounts at <subdomain>.amocrm.ru use this connector; the old international addresses <subdomain>.amocrm.com forward there, so enter the same subdomain. Accounts at <subdomain>.kommo.com use the Kommo connector.

Setup (account administrator, about 5 minutes)

1. In amoCRM open амоМаркет (amoMarket) in the left menu, click ⋯ in the top right (next to + WEB HOOKS) and choose Создать интеграцию (Create integration), then Внешняя интеграция (external integration).
2. Enter a Ссылка для перенаправления (redirect URL): the form requires one, but the long-lived token never uses it, so any https address of yours will do. Tick the accesses under Предоставить доступ, give the integration a name and description, and click Сохранить (Save).
3. Open the integration's Ключи и доступы (Keys and scopes) tab and click Сгенерировать токен (Generate token). Pick an expiry date (1 day to 5 years) and copy the token right away: amoCRM shows it only once.
4. Paste it into AMOCRM_ACCESS_TOKEN, and your account's subdomain into AMOCRM_SUBDOMAIN: for https://acme.amocrm.ru enter acme.
5. The token acts as the administrator who created it. Revoke it on the integration's Выданные доступы tab with Отозвать доступ; when it expires, generate a new one.

Read-only setup: amoCRM tokens cannot be limited to reading, so switch off amocrm_create_lead, amocrm_update_lead, amocrm_create_contact, amocrm_create_task and amocrm_add_note. Nothing in this connector deletes data.

Ids and values: every id is an integer, except event ids, which are strings. Deals are called leads in the API. Deal stages are status_id values inside a pipeline_id from amocrm_list_pipelines; 142 is Closed-won (Успешно реализовано) and 143 Closed-lost (Закрыто и не реализовано) in every pipeline. Loss reasons (the loss_reason_id of a lost deal) come from amocrm_list_loss_reasons. Responsible users come from amocrm_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; amocrm_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.

Where to start: amocrm_get_account (account, currency, task types), then amocrm_list_leads / amocrm_get_lead, amocrm_list_contacts / amocrm_get_contact, amocrm_list_companies and amocrm_list_tasks.

Notes and events: amocrm_list_notes reads one record's timeline; amocrm_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). amocrm_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, customer, task), unlike the other tools.

Pagination: list tools take page (from 1) and limit (up to 250; 100 for amocrm_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 integration and 50 per account. Over it amoCRM answers 429; repeated violations block the account's API access with 403 for every call. Avoid paging through all deals or events when a filter or search does the job.

Errors: 401 means the token is wrong, expired or revoked, or no account has this subdomain on amocrm.ru (a Kommo account belongs in the Kommo connector). 402 means the subscription has ended: writes stop at once, reads 30 days later. 403 can mean the token's user lacks rights or API access was blocked after too many requests. 404 is a wrong id. 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, customers (покупатели), unsorted (incoming) leads, chats and messages, lists (catalogs), webhooks and Salesbot.