amoCRM
AmoCRM (Kommo)

Find the leaks in your sales funnel without opening amoCRM

Connect AmoCRM (Kommo) to the AI agent: deals, contacts and funnels. The agent finds funnel leaks, summarizes rep performance and revives stalled deals.

How the agent works with amoCRM

The agent calls your account API at the address of your subdomain — amocrm.ru for amoCRM or kommo.com for Kommo — and reads deals, contacts, companies, pipelines, tasks and notes. The first thing it fetches is the list of pipelines together with their stages: without that map there is nothing to measure conversion against. Then it counts the step-to-step transitions, amounts and timings per rep, deals with no movement and the fields left empty — budget, phone, owner.

A deal stage in amoCRM is moved by hand, so on its own it does not tell you whether anyone is working the client. The agent looks at the date of the last change, at open and overdue tasks and at the correspondence in the notes: a deal sitting in negotiations for a third week with not a single task lands in the stalled pile, not the active one. Identically named stages in different pipelines are different entities, and the agent does not merge them into one conversion.

For writes the agent does what the integration is allowed to do: create tasks, move deals between stages, append notes. Before an edit it re-reads the deal so as not to overwrite a rep's fresh change, and a bulk action — moving a dozen deals or handing out tasks — is shown as a list and waits for confirmation. Creations, updates and deletions of deals, contacts, companies and tasks arrive from amoCRM as signed webhooks, so the agent learns about a change without constant polling.

The long-lived token works until the expiry date chosen at issuance and does not renew automatically. When it expires, generate a new token in amoCRM and replace it in the connection. Deals, contacts and tasks come back from amoCRM in pages of 250 records, and the agent reads a selection to the end instead of stopping at the first page. Revoke the integration in the account and access stops immediately, and the agent says the connection has to be restored rather than quietly returning zero. It keeps the request rate within what is allowed, and if a section is closed by permissions or there simply were no deals in the period, it says so directly instead of showing an empty table.

Integration scenarios

Find the leaks in your sales funnel

The agent breaks deals down by stage, computes step-to-step conversion and shows where leads stall or slip away with no task attached.

Weekly rep performance summary

The agent gathers new deals, closures, amounts and overdue tasks for every rep, so the report is ready for the stand-up.

Revive stalled deals

The agent finds deals with no movement for N days, groups them by stage and prepares a call list with context on each one.

Keep CRM data clean

The agent checks for deals without a budget, contacts without a phone and leads with no owner, then sends a list to fix.

Keep watch on new leads

The agent catches a signed webhook about a new deal, pulls up the card with budget, contact and owner and posts it to chat — no scheduled polling.

Hand out tasks after a review

The agent collects deals with not a single task, lists who should get what, and once you confirm it creates the tasks, re-reading every deal first.

amoCRM examples

amoCRM
amoCRM
Frozen chats — click a question
Где теряются сделки в воронке?

Из 312 сделок квартала до оплаты дошли 47.

  • первичный контакт 312 → квалификация 168: половина отваливается уже здесь
  • переговоры 121 → счёт 63, причём у 24 сделок нет ни одной задачи
  • счёт 63 → оплата 47

Отдельно 41 сделка стоит без движения дольше 30 дней — воронка «Продажи», этапы других воронок с такими же названиями я в этот счёт не сводил.

Воронка «Продажи» за квартал

Table · XLSX

How to connect

Before you connect

  • Account administrator rights in amoCRM or Kommo.
  • Your full account URL, for example https://your-company.amocrm.ru.
  • A long-lived external integration token with access to the required data.
  1. 1

    As administrator, copy the account URL

    Copy your account URL, for example https://your-company.amocrm.ru, and paste it into Account URL. Administrator rights are required to generate a token.

  2. 2

    In amoMarket create an external integration

    amoMarket → Create integration → External integration. Enter a name and complete the required amoCRM settings, then save the integration.

  3. 3

    In the Allow access block select the scopes

    In the Allow access block every scope is checked. Keep leads, contacts, companies and tasks — the rest you can clear.

  4. 4

    In Keys and access issue a long-lived token

    In Keys and access, generate a long-lived token. Choose an expiry and copy it immediately: it is shown once. Enter your account URL and token in our form.

FAQ

Using a long-lived token: open your external integration in amoMarket, then Keys and access → Long-lived token → Generate token. Choose an expiry date and paste the token into our form along with your full account URL. Access runs on behalf of the integration and is revoked in the same place.

Deals, contacts, companies, pipelines, tasks and notes, within the permissions granted to the integration. The agent reads data on demand and never copies the whole database.

Yes, when write permissions are granted: create tasks, move deals between stages, append notes. The agent confirms every write with you unless you configure it otherwise.

Yes. Kommo is the international version of amoCRM with the same API, and the connector supports both.

Related integrations

Category
CRM
Connection
API key
Documentation
amoCRM

Connect amoCRM

Connecting takes a couple of minutes, and your data stays in your own systems.

Connect