Bitrix24 and amoCRM are what RU/CIS teams mean when they search “интеграция CRM.” This page is webhooks and APIs: site form → deal, bot → contact, warehouse status → lead field. It is not a 1C accounting core—that is 1C and CRM. It is not building Bitrix24 from scratch as an intranet product. Messenger-only CRM hooks also appear under bots + CRM.

I map entities first: what is a lead vs a deal vs a company in your pipeline. Then inbound (site, bot, telephony) and outbound (status back to the cabinet or MAX). Idempotent webhooks, so a double submit does not duplicate the funnel. Tokens and incoming URLs stay in env, not in a manager’s chat history.

n8n can orchestrate simple SaaS-to-SaaS flows—see n8n. Custom TypeScript services appear when you need validation, queues, or a UI your CRM cannot express. Related fullstack: external integrations.

I am not a Bitrix24 licensed implementer of every marketplace app. I will say no to “sync everything including 40 custom fields we never use.” First slice: one inbound, one outbound, plus a staging portal. Telephony and call-tracking widgets stay in scope only when the CRM already owns the number; I do not resell PBX licenses.

Timeline: a contained CRM contour is often 3–7 weeks after API users exist.

What you get

• Entity map, field list, and duplicate rules
• Webhook endpoints, retries, staging CRM
• Minimal admin log: last payload, last error
• Hypercare for the first real leads