Integration
amoCRM and Instagram integration
The conversation ends and the lead appears in amoCRM. With a name, a phone number, what they asked for, and which ad they came from.
Start 7 days freeNo card required
The manual work between Instagram and amoCRM
A customer arrived from Instagram, asked a question, left a phone number. Now somebody has to copy it into amoCRM: the name, the number, what they wanted.
That happens dozens of times a day, and it always ends the same way — some of it never gets copied. During a busy hour, in the evening, on a weekend.
What changes
The agent gathers what it needs during the conversation, and when the conversation wraps up it sends this to amoCRM:
- Name — what the customer said, or from their Instagram profile
- Phone number — normalised (+998…)
- Detected intent — what they want to buy, which service
- Conversation transcript — as a note, in full
- Source — which post or ad they came from
By the time a manager opens amoCRM, the lead is already there, with its context.
How to connect it
1. Grant access through OAuth. You press “Allow” on your amoCRM page. No password is typed here, and the token is stored encrypted.
2. Choose the pipeline. You set which pipeline and which stage leads land in. Working through Unsorted is an option too.
3. Map the fields. Which piece of information goes into which field — including custom fields you created yourself.
4. Check it. Run a test conversation and watch the lead appear in the right place in amoCRM.
Duplicates
Phone numbers are normalised to international format and checked against existing contacts.
When the same number writes a second time, no new lead is created — the new conversation is attached to the contact that already exists. One customer stays one record in your CRM.
If the connection drops
An amoCRM token expires, or gets revoked. That is a normal thing to happen.
The dashboard shows an “authorisation expired” state and you get a notification. Leads that could not be sent during that window are held in a queue and delivered automatically once the connection is restored.
No lead is lost — it is built that way on purpose.
Bitrix24 and Google Sheets
The same thing works for Bitrix24. Google Sheets is the simplest path of all: each lead becomes a new row, and you need no CRM at all.
If your CRM is not on the list, an outbound webhook connects it to anything. Every send is HMAC-signed and retried if it fails.
Getting started
Seven days free. During the trial the CRM integration runs in test mode — meaning you connect your real amoCRM and check the whole thing end to end.
Frequently asked questions
How does it connect to amoCRM?
Through OAuth — you grant access on your own amoCRM page and never type a password here. The connection is one press, about a minute.
Which pipeline do leads land in?
The one you choose. You set the pipeline and the starting stage in settings. Working through Unsorted is supported too.
Can I map the fields myself?
Yes. In field mapping you decide which piece of information goes into which amoCRM field, including custom fields you created yourself.
Will I get duplicate leads?
Phone numbers are normalised and checked against existing contacts. When the same number comes back, no new lead is created — the new conversation is attached to the existing contact.
What happens if the amoCRM token expires?
The dashboard shows an "authorisation expired" state and you get a notification. Leads that could not be sent are held in a queue and delivered once the connection is restored.