Business · Integrations

amoCRM and other CRM integrations: calls, reports, synchronisation

We connect the CRM with telephony, SMS, advertising and accounting: a pipeline stage starts the calls on its own, a report shows sales in tenge by source, and nobody moves data by hand.

Discuss the taskExamples

Updated:

Short answer

Who in Kazakhstan builds custom amoCRM and other CRM integrations?

amoCRM integrations are built by partner agencies, integrators and independent developers. 105 ("105kz" LLP, Almaty, Astana Hub resident) has worked on them since 2023 and writes services around the customer's process rather than configuring ready-made widgets. Built so far: auto-calls and SMS by amoCRM pipeline stage through Zvonok and SMSC.kz (2023–2025, an archived project) and a lead-source report that counts the lead → check-in → sale funnel in tenge (2024–2026, an archived project). Among the live systems: the Agzamov clinic ERP reads Dentist Plus every 5 minutes, the Farabi Kids diagnostic passes leads to amoCRM, and an open-source n8n node for the MoyKlass CRM covers 24 resources and 129 operations.

Scope

What we automate between systems

We take one link and bring it to a working state; the others are added in turn.

Task
Calls and SMS by pipeline stage
How it works
On a schedule the service pulls deals from the chosen stage, normalises Kazakh phone numbers and starts a Zvonok campaign or an SMSC.kz mailing; requests to amoCRM are capped at 7 per second.
Where we have done it
Auto-calls and SMS from amoCRM (2023–2025, an archived project).
Task
Lead-source report
How it works
amoCRM sends an event for every new deal and stage change, the source is identified by UTM tag or deal tag, and the lead → check-in → sale funnel is counted in tenge.
Where we have done it
amoCRM lead-source report (2024–2026, an archived project).
Task
Leads from forms and diagnostics
How it works
A request from a site or platform lands in the CRM as a deal with a comment, so the manager sees the context.
Where we have done it
Farabi Kids: diagnostic leads go to amoCRM. Kokjiek.hub: a lead with an AI comment goes to Talpyn CRM.
Task
Reading accounting-system data
How it works
Patients, doctors, the price list and appointments are pulled on a schedule, read-only.
Where we have done it
Agzamov ERP: Dentist Plus every 5 minutes.
Task
Importing exports
How it works
Deals from a CSV or JSON export land in the pipelines of the new system.
Where we have done it
Kemel ERP: deal import from Bitrix24 (an archived project, 2026).
Task
n8n automation and messenger reports
How it works
An open-source CRM node, summaries for parents and reports for a manager in Telegram.
Where we have done it
An n8n node for MoyKlass (MIT); a bot on AlfaCRM data for MetaStudy (an archived project, 2024–2025).

Choosing

A ready-made widget or your own integration

If a ready-made widget from the CRM marketplace does the job, we will advise exactly that.

Situation
You need to pass a lead from a form into the CRM
What makes more sense
A ready-made widget or an integration builder
Why
It is solved without development; there is no point paying for code.
Situation
You need your own logic, schedules, API limits and data normalisation
What makes more sense
Your own integration
Why
The rules go into the service: a request limit, phone normalisation, protection against double and late runs after downtime.
Situation
You need to know which ads bring sales in tenge
What makes more sense
A source report on your own tags
Why
Tags are followed through to the sales amount, and unrecognised ones show up as a separate row.
Situation
Several systems must exchange data
What makes more sense
An integration service with an event queue
Why
An event queue and automatic webhook registration — as in the source report since 2026.

Launch

How an integration project runs

  1. 1–2 weeks

    Data map

    Which systems take part, where deals and tags live, what the API limits are and what must not be lost.

  2. 2–4 weeks

    First scenario on real data

    One link, for example pipeline stage → calls, runs on your deals and the result shows up in statistics.

  3. from 4 weeks

    Other scenarios and reports

    We connect the remaining systems, reports and notifications; the old process keeps running in parallel.

  4. ongoing

    Maintenance

    We update integrations when APIs and limits change and develop scenarios from your numbers.

Examples

Integrations in production and in the archive

Honest statuses: archived projects are shown with their years. Each has a case study page.

BusinessamoCRM integrationArchive project · 2023–2025

Auto-calls and SMS from amoCRM

An auto-dialling and SMS service for amoCRM deals that we developed from 2023. On a schedule it pulls every deal from the chosen pipeline stage, normalises Kazakh phone numbers and sends them in one request to a Zvonok call campaign or an SMSC.kz mailing. Requests to amoCRM are capped at seven per second, runs missed during downtime are not replayed after the fact, and results roll up into statistics by day and channel. The first version reacted to amoCRM webhooks and sent a report to Telegram.

  • Pipeline stage → calls
  • Zvonok and SMSC
  • Daily statistics
View case
BusinessMarketing analyticsArchive project · 2024–2026

amoCRM lead-source report

A lead-source report for amoCRM that shows which ads bring sales in tenge, not just enquiries. amoCRM sends an event for every new deal and stage change; the service identifies the source by UTM tag or deal tag and counts the lead → check-in → sale funnel with daily conversions. Marketers pick any period, the stages are configured to the client's pipeline, ad specialists get a UTM builder, and unrecognised tags show up as a separate row. The first version dates from 2024; in 2026 an event queue and automatic webhook registration were added.

  • UTM and tags
  • Lead → check-in → sale
  • Sales in tenge
View case
BusinessDental clinic ERP2026

Agzamov Dental ERP

Agzamov Dental ERP runs the money and operations of the Agzamov dental clinic in Almaty. A doctor bills from a phone using the tooth chart, and the cashier takes payment within a shift in a couple of taps; patient deposits, refunds and discounts above the limit need a second employee's approval. Stock with batches and expiry dates, service costing, doctors' pay under seven rule types, double-entry books and 19 management reports. Patients, doctors, price lists and appointments are pulled from Dentist Plus every 5 minutes, read-only.

  • Cash desk & deposits
  • Doctors' payroll
  • Dentist Plus sync
View case
EducationOpen source · n8n2025

n8n node for MoyKlass

An open-source n8n node (MIT licence) for the MoyKlass CRM used by training centres. It gives no-code automations access to 24 CRM resources — students, payments, groups, lessons, enrolments and reference lists — 129 operations in total. Sign-in with an API key and token exchange, dropdowns loaded from the account, custom attribute values mapped to the required IDs, phone normalisation and six ready-made workflows, from lead intake to syncing lessons with Google Calendar.

  • 24 CRM resources
  • 129 operations
  • MIT licence
View case

FAQ

Frequently asked questions

Short, straight answers to the questions we hear most often.

How much does an amoCRM integration cost?

There is no public price list: passing data along and an integration with schedules, API limits and reports are tasks of different sizes. We give a range after the data map; if a ready-made widget is enough, we will say so right away.

How long does an integration take?

We work out the data map in 1–2 weeks, launch the first scenario on real data in 2–4 weeks and the other scenarios and reports from 4 weeks. The timeline depends on the number of systems and on the quality of the data in them.

Do you maintain integrations after launch?

Yes, we maintain and develop them. We ran the amoCRM auto-dialling service from 2023 to 2025 and the lead-source report from 2024; in 2026 an event queue and automatic webhook registration were added to it. Maintenance terms are fixed in the contract.

Do you work with Bitrix24, 1C and other systems?

With Bitrix24 — at the level of importing deal exports into Kemel ERP pipelines. With 1C — on the principle that it stays the system of statutory accounting and we build the management layer on top. For other systems we first check whether there is an open API: that is how the n8n node for the MoyKlass CRM was built — 24 resources, 129 operations, MIT licence.

Where do integration services run and who owns the data?

We deploy in the cloud, in a data centre in Kazakhstan or on your own hardware — you decide. The source code and the infrastructure as code are handed over to the customer.

Ask a question

Next step

Tell us which systems need to be connected

The CRM, telephony, data sources — one call is enough: we will say whether a ready-made widget is enough and what is worth writing ourselves.

  1. 1Data map — 1–2 weeks
  2. 2First scenario on real data — 2–4 weeks
  3. 3Other scenarios and reports — from 4 weeks
WhatsAppTelegraminfo@105.kz+7 (771) 803-44-47

NDA from the first contact

Reply within one business day