Telegram Leads Straight Into Bitrix24: Setup in 30 Minutes
Our leads died in a spreadsheet for months. Webhook + field mapping + dedupe key fixed it: 40 seconds from message to manager.
Our Telegram leads were dying in a spreadsheet. Bitrix24 fixed it in 30 minutes.
Here's an embarrassing confession: for months, our own Telegram leads lived in a Google Sheet. Someone copy-pasted usernames, someone forgot, hot leads cooled for three days before anyone wrote back. We sell lead generation automation. The cobbler's children had no shoes.
So we wired Telegram leads straight into Bitrix24. Took 30 minutes. Here's the setup.
The pipeline
Telegram group → keyword/AI detection → webhook → Bitrix24 lead with source, chat link, and message text. A manager sees it in under a minute and replies while the person is still online. That's the whole trick — speed, not software.
Setup, step by step
- Incoming webhook in Bitrix24. Admin panel → Applications → Webhooks → Incoming webhook. Give it CRM permissions. Copy the URL — it looks like
https://yourdomain.bitrix24.ru/rest/1/abc123/crm.lead.add.json. - Catch leads on the Telegram side. In 24GO: lead rules → your keywords → action "send webhook." Paste the Bitrix URL. Map the fields: username → TITLE/COMMENTS, group name → SOURCE_ID, message text → COMMENTS.
- Lead distribution. Bitrix24 → CRM → Settings → assignment rules: round-robin across managers, or by direction (all "price" questions to sales, all "support" to support).
- Test with one message. Write your own trigger keyword in a monitored group. The lead should appear in Bitrix in under 60 seconds. If not — 99% of the time the webhook URL has a typo.
What broke for us (twice)
Duplicates. The same person wrote three messages with buying intent in one day — and became three leads, fought over by two managers. Fix: dedupe key on username + 30-day window. One person = one lead, new messages append to comments. Slow managers. Automation delivered leads in 40 seconds; managers replied in 6 hours. The bottleneck moved, it didn't disappear. Fix: Bitrix SLA timer + notification to the manager's Telegram after 15 minutes of silence. Reply time dropped to under an hour.Field mapping cheat sheet
| Telegram data | Bitrix24 field |
|---|---|
| @username | TITLE + COMMENTS |
| Group/chat name | SOURCE_ID |
| Message text | COMMENTS |
| Intent (HOT/WARM/COLD) | Custom field UF_CRM_LEAD_SCORE |
| Chat link | Custom field UF_CRM_CHAT_URL |
FAQ
Bitrix24 or AmoCRM for Telegram leads? Honestly? Both work. Bitrix if you need deep customization and already live there; AmoCRM if you want the pipeline view out of the box. We wrote a separate AmoCRM guide earlier — same principles, different buttons. Does this need a developer? No. Webhook URL + field mapping is admin-panel clicking. The only "code" is copying a URL. If you can set up a mailbox, you can set this up. What about leads that reply at 3 AM? Auto-reply handles the first touch ("Thanks, we'll get back at 9 AM"), Bitrix holds the lead, manager picks it up in the morning. Nobody waits, nobody lost.The takeaway
Leads don't die from bad tools. They die in the gap between "message received" and "manager replied." Our gap was three days and a spreadsheet. Now it's 40 seconds and Bitrix24. Measure your gap — that's your real conversion problem.
How fast do YOUR leads reach a manager?