Why connect Telegram to Kommo (amoCRM)
Kommo (formerly amoCRM) is built around messenger sales and is popular across the CIS, Latin America, Spain, Portugal and Turkey. It has a native Telegram channel for chats; we extend it with Mini Apps, structured data and automation that the built-in Salesbot cannot express. A Telegram bot or Mini App without the integration creates a second customer list that nobody maintains; with it, every Telegram interaction lands on the right record, managers get alerts where they already are, and customers get updates in the chat they actually read.
How the integration works
- Auth. A private OAuth integration with refresh tokens, scoped to leads, contacts, chats and webhooks.
- Chats. The native Telegram channel handles conversations; our bot pushes Mini App events (orders, forms, payments) into the same lead through the Chat API and notes.
- Digital pipeline. Stage changes trigger our webhook; messages go out through the bot with templates and personalization beyond Salesbot limits.
- Commerce. Orders from a Telegram storefront become leads with products and payment status.
Typical flows
- Mini App order → lead in the right pipeline with Telegram chat attached
- Stage “Payment” → invoice via Stars, card or local provider
- Abandoned form → reminder sequence through the bot
- Manager replies in Kommo, client reads in Telegram
Architecture
| Layer | What runs there |
|---|---|
| Telegram | Your bot (grammY or aiogram) and Mini App; users never leave Telegram |
| Middleware | A small service on your cloud (Node.js or Python): auth with Kommo (amoCRM), upserts, dedupe, templates, rate limits, retries, audit log |
| Kommo (amoCRM) | Native objects and automations; no custom code inside Kommo (amoCRM) beyond fields and triggers |
| Monitoring | Failed syncs alert your team in a Telegram group; a daily reconciliation report catches drift |
We keep business logic in the middleware so that Kommo (amoCRM) upgrades, API version changes and bot changes do not break each other. The middleware ships with tests, an admin page for retries and documentation your developers can extend.
Data, consent and compliance
Telegram user IDs, usernames and phone numbers are personal data. The integration stores consent (captured in the bot or Mini App), supports unsubscribe commands, honors deletion requests by removing the Telegram identity from Kommo (amoCRM) records, and keeps data in your Kommo (amoCRM) region and your cloud region. For GDPR, UK GDPR, PIPEDA and the Australian Privacy Act we provide a data flow document for your DPO.
Pricing and timeline
| Scope | Budget | Timeline |
|---|---|---|
| One-way: Telegram → Kommo (amoCRM) records and manager alerts | from $2,000 | 1–2 weeks |
| Two-way: plus triggered messages and operator replies | +$1,500–$3,000 | +1 week |
| Commerce or support add-ons (orders, tickets, payments) | +$1,500–$4,000 | +1–2 weeks |
Every integration includes field mapping, a sandbox phase, a go-live checklist and 30 days of fixes. Need the bot or Mini App built as well? See Telegram bot development and Mini App development.
* All prices and ranges on this page are indicative. The final cost is calculated for each project individually and depends on the complexity of the task, the number of developers and specialists required, and the delivery timeline you set. Use the ranges to understand the typical bracket, not as a fixed offer; the fixed price is confirmed in writing after scoping. Read our pricing terms.