amoCRM: requests become leads
Every request in your Sensever project can become a lead in your amoCRM pipeline. The lead gets the customer's contact (name, phone or email) and the tag Sensever, and a note with the channel, the customer's first message and a link to the request. When the request is closed, the conversation is added to the lead as a note.
A project works with one CRM at a time: amoCRM or Bitrix24.
What you need
An amoCRM account where you are an administrator — only an administrator can create the token.
Owner or admin rights in the Sensever project.
Step 1. A long-lived token in amoCRM
In amoCRM, create a private integration: amoMarket → Create integration (in some versions — Settings → Integrations). The redirect address and the other fields can stay empty.
Open the integration's Keys and scopes tab and click Generate long-lived token.
Choose the longest term (up to 5 years) and copy the token. amoCRM shows it only once.
Keep the token secret: anyone who has it can work with your amoCRM as an administrator. Sensever stores it encrypted and shows only its last characters.
Step 2. Connect it in Sensever
Projects → the project → the CRM tile → amoCRM.
Enter the account address — the address you open amoCRM at, for example
your-company.amocrm.ru(an address from the browser's bar works too).Paste the long-lived token.
Choose when to create a lead (see below) and the country for numbers written without "+". By default it's the country of the project owner's account.
Click Connect. Sensever checks the token and reads your pipelines.
Choose the pipeline and the stage for new leads, then Save. By default it's the main pipeline and its first stage. "Unsorted" and the closing stages are not offered.
When a lead is created
Only when the customer leaves a phone or email (default) — conversations without a contact don't clutter the pipeline.
Right at the first message — every request becomes a lead; the contact is added when the customer leaves it.
Where the contact comes from
As for Bitrix24: the messenger (the WhatsApp number, the name and @username), a phone your team typed into the request card or a contact the customer shared, the website's identify(), a Sensever account, and the customer's own messages — only clear phone forms and emails, never sums, order numbers or dates. Phones go to amoCRM in the international format (+79123456789), marked as mobile or work.
Customers amoCRM already has
Before creating a lead, Sensever searches amoCRM contacts by the phone and email and checks every match by the contact's own phone and email fields. If the customer is found, the new lead is linked to that contact — a repeat customer's new request shows up in the pipeline. Sensever never changes a contact it found: a phone or email that appears later goes to the lead as a note.
A contact Sensever created itself gets later phones and emails added to it; what it already has stays.
When the request is closed
The conversation goes to the lead as a note: who wrote what and when (time in UTC), files marked as "[files: N]". Very long conversations are cut from the beginning, and the latest messages are kept.
Errors
If amoCRM stops accepting leads, the CRM tile shows "Leads are not being sent" with the reason, and the Sensever Channels bot messages the project owner and admins once:
Message | What to do |
|---|---|
amoCRM does not accept the token | The token was revoked, expired or belongs to another account. Generate a new long-lived token and paste it on the CRM tile. |
amoCRM refused access | The account is not paid or is blocked. Check the account's status in amoCRM. |
This is not an amoCRM account address | Check the address — it's the one you open amoCRM at. |
amoCRM refused the lead data | Check required fields you added to leads or contacts in amoCRM. |
amoCRM does not respond | Nothing: Sensever retries by itself. |
Requests waiting during an error are sent as soon as you paste a working token. amoCRM limits how often it may be called, so a busy hour may reach the pipeline with a short delay.
Turning it off
Disconnect on the CRM tile stops sending new requests. Leads and contacts already created stay in amoCRM. If you connect again later — or connect another account — the numbering starts from 1, and requests opened before the connection are not sent.
コメント