amoCRM
amoCRM integration: every conversation — a deal with history
A client writes in any channel — a deal with the contact and full conversation appears in amoCRM. The manager works in the familiar CRM, the client in the familiar messenger.
14 days of the Team plan — free
Кира Мещерякова
Лид · amoCRM · 2 мин назад
Переписка прикреплена
Ответственный: Анна С. · назначена автоматически
2 min
from message to deal
5 events
stream to amoCRM automatically
100%
of history in the card
0 manual
lead work
amoCRM runs deals. Chatva runs conversations
amoCRM has a strong pipeline: stages, tasks, automation. But the actual customer conversation lives in messengers — and reaches the CRM in fragments or not at all. The Chatva connection divides the work fairly: Chatva receives and delivers conversations, amoCRM runs the deal — and they share one history.
- conversations from every channel — instantly deals and contacts in amoCRM;
- the manager replies from the fast Chatva inbox, not from the CRM;
- the Digital pipeline receives events: reply, closing, rating;
- no manual copying from chat to CRM.
What happens in amoCRM automatically
The connection works via webhooks — configured in the dashboard, no developer
| Event in Chatva | Action in amoCRM |
|---|---|
| New conversation from any channel | A deal is created with the client's name, channel and first message |
| Client leaves a phone or email | The contact is enriched and linked to the deal |
| Conversation assigned to an operator | The responsible person changes in the deal |
| Conversation closed | The deal moves to the right pipeline stage |
| Client leaves a rating | Rating and comment land in the deal note |
Every client channel in one deal
The client wrote first from the site, then on Telegram, and asked for a call on WhatsApp — for the manager it is one conversation, and for amoCRM it is one deal with the full touchpoint history.
- site, Telegram, WhatsApp, VK, MAX and Avito in one inbox;
- contacts merge by phone and email — no duplicate deals;
- the first-touch channel is stored for end-to-end analytics.
Инбокс Чатвы
Кира М. · Telegram
А есть ли рассрочка?
Пабло К. · Сайт
Доставка в СПб?
Инна Б. · VK
Запись на субботу
A fast reply wins the deal
Lead conversion drops tenfold if you answer in an hour instead of five minutes. Chatva pushes arrive instantly — the manager replies while the client is still looking at the screen.
- notifications to the browser, Telegram and email;
- a conversation unanswered for five minutes signals the manager;
- first-response time visible per manager.
Новый диалогсейчас
Telegram · Кира М.: «Здравствуйте! А есть ли рассрочка?»
Диалог без ответа 5 минут2 мин
Назначьте оператора, клиент ждёт
Events for the Digital pipeline
Conversation closing, responsible assignment, customer rating — all these are events the Digital pipeline can react to: create tasks, move the deal, launch scenarios.
- webhooks: message:new, conversation:new, conversation:update;
- signatures and retries — events never get lost;
- custom logic via the open REST API and OpenAPI.
Диалог
любой канал
Вебхук
conversation:new
amoCRM
сделка + контакт
Setting up the connection
Basic scenario — webhooks, advanced — REST API
- 1
Enable the API in Chatva
On the Business plan an API key is created in settings — it signs all requests and webhooks.
- 2
Create a webhook
Enter your handler URL and the events: new conversation, contact, closing, rating. Chatva POSTs JSON there.
- 3
Link with amoCRM
Via a connector (Albato, ApiX-Drive) or your own script: Chatva webhook → deal and contact creation via the amoCRM API.
- 4
Run a test
Message yourself from the site — a deal with the conversation appears in the pipeline within a couple of minutes.
Which sales teams this works for
A team with a pipeline and KPIs
Every inbound inquiry becomes a deal — the pipeline is finally honest. You see where deals stall and which manager is slow to reply.
Online store
“How much?” from five channels — instantly a deal with product context. Managers just take the next one from the queue, entering nothing by hand.
Developers and real estate
Long cycle: every touchpoint with the client in the card for months. A manager change does not break the sale — the history is there.
Services and clinics
A booking from chat — a deal with a date and a doctor. The reminder goes to the client's messenger from the same connection.
Three ways to connect
From “one evening, no developer” to fully custom logic
No-code connectors
Albato, ApiX-Drive and similar: pick Chatva events and amoCRM actions with the mouse. A basic connection in one evening, no developer.
Your own script
Your backend receives Chatva webhooks and calls the amoCRM API. Full control: field enrichment, custom stages, any logic.
An integrator
No developer of your own — message us: we will suggest proven amoCRM integrators and hand them the exchange scheme.
A pipeline you can believe
What changes when every conversation becomes a deal
0 manual
lead and contact entry
2 min
from message to deal card
100%
of conversations attached to deals
6 channels
in one deal with shared history
Leads from WhatsApp used to be entered into amo by hand — half got lost. Now the deal is created by itself, and the manager just takes the next one from the queue.
Honest pricing
Start free and grow with your customer flow. Cancel in one click, your data stays yours.
Pay for a year and get two months free.
Start
To test the idea
0 ₽/ per month
- 1 agent
- Site widget and Telegram
- 100 chats per month
- Quick replies
Team
For sales and support teams
1 490 ₽/ per month
- 5 agents
- All channels, no limits
- Autopilot and bots
- Telegram notifications
- Analytics and ratings
Business
Chains and high volumes
4 990 ₽/ per month
- Unlimited agents
- SLA and priority support
- API and webhooks
- White label, no Chatva mention
- A dedicated manager
FAQ about the amoCRM integration
The connection works through the open REST API and webhooks of both systems — the standard integration approach also supported by amoCRM.
No: the typical setup first searches the contact by phone or email and appends to the existing deal instead of creating a new one.
For the basic scenario, no-code connectors (Albato, ApiX-Drive) are enough. For custom logic, involve a developer — the API documentation is open.
Replies are more convenient in Chatva — it delivers them to the client's channel with read receipts and history. The full thread still stays in amoCRM.
API and webhooks are available on the Business plan. Any amoCRM plan with API access works.
Related reading
Connect chats and pipeline
The first deal from chat will appear in amoCRM today.