CRM integration means a configured data exchange between the CRM and the rest of a company's software: the website, telephony, messengers, 1C and ERP. Requests, calls, invoices and payments land in the customer record on their own, with no copying by hand. There are four ways to build the exchange — an API, a webhook, a ready-made connector or a scheduled file export — and the choice depends on what the second system can do.
Key takeaways
Integration is needed when the same data lives in several programs at once and staff move it by hand. Until that duplication appears, a CRM works fine without any exchange.
Look at the list below. If three or more points match, manual re-entry is already costing the company working hours and mismatched numbers.
A CRM is connected to everything that creates or consumes customer data: inbound channels, record-keeping systems, payments and stock. The table shows how each connection works technically and what usually travels between the systems.
| System | How it is connected | What is synchronised | Direction |
|---|---|---|---|
| Website and forms | Form webhook or CRM API | Request, contact, landing page and campaign tag | Into the CRM |
| IP telephony | Operator connector or API | Inbound and missed calls, recordings, call-back tasks | Both ways |
| Telegram | Corporate bot on the Bot API | Conversation, request, source tag, alerts for sales reps | Both ways |
| WhatsApp Business Platform | Chat inside the service window, template order updates | Both ways | |
| 1C | REST interface over the OData protocol or file exchange | Counterparties, orders, invoices, payments, stock | Both ways |
| ERP or warehouse system | System API or a shared database | Order released to work, fulfilment status, reservation and shipment | Both ways |
| Payment service | API and a payment webhook | Payment link, payment status, refund | Both ways |
| Mobile app | The product's own API | Sign-ups, orders, support requests, loyalty points | Into the CRM |
If the company already runs an off-the-shelf CRM such as amoCRM or Bitrix24, there is no need to replace it: a boxed system is connected to 1C, telephony and internal services the same way a custom one is. The international version of amoCRM has been called Kommo since October 2022.
Connecting everything at once makes little sense: each exchange then has to be maintained, updated when versions change and checked after failures. Start with the pair of systems between which data is retyped most often.
The methods differ in who calls whom and how quickly the data arrives. There are four of them, and a single project normally uses several at once.
The closer an exchange gets to real time, the more it costs to run: it needs retries, a message queue and an error log. For payments a delay is unacceptable; for warehouse stock an hourly exchange is usually enough.
Data is exchanged with 1C through the platform's automatic REST interface: the application is published on a web server, after which external systems read and change data over the OData protocol. If the platform is old or outbound access is closed, a scheduled file exchange remains.
Directions are agreed in advance, otherwise the two systems start arguing over whose version of a reference list is correct.
| From the CRM to 1C | From 1C to the CRM |
|---|---|
| Counterparty with legal details | Payment and its date |
| Order and its line items | Outstanding balance per counterparty |
| Contract and its annexes | Stock levels and reservations |
| Invoice for payment | Shipment status |
| Products taken from the deal | Closing documents |
| Account manager | Returns and adjustments |
One rule removes half of the future trouble: every reference list has a single owner. Counterparties are maintained in the CRM, products in 1C, and in the opposite direction they arrive read-only. Then a sales rep sees the payment and the balance inside the deal, and the finance team does not edit what it should not touch.
Messengers are connected under the platforms' own rules, and those rules are stricter than people assume. Both channels work through official interfaces, not through an employee's personal account.
Important A Telegram bot cannot message a person first: the Bot API documentation states plainly that bots do not start conversations — the user has to write to the bot first. So only people who have already started the bot will receive notifications. In WhatsApp, a customer's message opens a 24-hour service window; once it closes, you may only write using a pre-approved template — those are the terms of the WhatsApp Business Platform.
Companies normally run a corporate bot alongside the CRM: it takes the request, files it in the customer record and alerts the sales rep. How the exchange between a bot and a CRM is built, which data to pass and how to tell where a person came from is covered separately in our article on connecting a Telegram bot to a CRM.
We do not recommend plugging employees' personal accounts into a CRM. It is done with unofficial tools, and the price is a blocked number together with the entire chat history — which by then already counts as company data.
The project takes five steps, and the first two are paperwork. Until it is written down which fields travel between systems and on which event, there is nothing to configure.
At the configuration step, website and advertising requests are given a source tag: without it you cannot later build end-to-end analytics from the ad to the payment.
The price depends on whether you are connecting systems that already run or wiring up data sources inside a CRM rollout. On our service pages these are three different formats.
Three things push the budget above the starting figure: the number of system pairs, closed or in-house programs without an API, and the quality of the source data — duplicates in reference lists are cleaned before the exchange goes live, otherwise they spread across both databases. What each format includes is set out on our CRM development and ERP development pages.
If an exchange is no longer enough and the company needs joined-up records for production, stock and finance, the task becomes an ERP project. How ERP differs from CRM and 1C is covered in our article on ERP in plain terms.
Walk through this list before you put the integration into daily use. These points close off the mistakes that are the most expensive to clean up later.
The fifth point is often skipped and it is the nastiest one: if the integration runs under a departed sales rep's account, the exchange stops the day that access is revoked. How this should be set up is covered in our article on access rights in a CRM.
Syntra Systems starts with a map of systems rather than with code: what is kept where, who enters data twice and which exchanges will genuinely save time. We then fix the design — fields, events, direction, error handling — and build the integration through APIs, webhooks or connectors, while closed programs get a scheduled file exchange.
We connect the website, Telegram, WhatsApp, telephony, email, 1C, ERP, warehouse and payment services, reconcile reference lists and set up a log that shows every failed transfer. After go-live we stay in touch: an exchange lives only as long as someone watches it.
Let’s discuss your project
Tell us what you need, and we will estimate the timeline and cost and suggest a solution.
With almost any system that offers an API, webhooks or a way to export data to a file. The hard cases are closed or in-house programs without documentation: there the database structure is reverse-engineered first, and the exchange is built to order, more often on a schedule than in real time.
A webhook fires at the moment of the event: a payment goes through and the CRM knows immediately. A scheduled exchange collects changes in batches, hourly or nightly. Webhooks are for decisions made right now; schedules are fine for reference lists and stock levels.
There are two routes. A ready-made connector from the CRM vendor or telecom operator connects fastest, but it only carries the set of fields built into it. For closed systems, an overnight file exchange is set up instead — the data updates once a day, which is enough for reference data and stock balances.
A matching rule is defined before go-live: which field tells the systems this is the same customer. Usually it is a phone number in one format, a company tax number or an external identifier. Reference lists are de-duplicated in advance, otherwise the duplicates spread across both databases.
Yes, an off-the-shelf CRM is connected to 1C, telephony, the website and internal services through APIs or connectors. There is one limit: the exchange works with the fields and permissions the platform exposes, so unusual logic sometimes has to live in a separate service.
Someone has to watch the error log and re-test the exchange after either system is updated. That is either your system administrator or a contractor under a support agreement. An unattended exchange eventually stops quietly, and it is usually discovered through mismatched numbers.
In Telegram — only people who have already started the bot, since a bot can't open a conversation first. In WhatsApp a 24-hour window opens after the client's message, and after it closes you can only send a pre-approved template.
