Website lead → CRM → manager: a live integration bench
A model of a website ↔ CRM integration: a form on the site, a deal pipeline and a log of API calls. A repeat request from the same phone does not create a duplicate; it is added to the deal. Each stage fires its robots: an email, a calendar meeting, an SMS reminder, a proposal PDF, an invoice in 1C, an NPS survey. Every call is shown with its request body and response, in the amoCRM or Bitrix24 format.
- 6
- pipeline stages
- 2
- CRMs: amoCRM and Bitrix24
- 15 min
- to call back, a task with a timer
The interactive demo did not start in this browser, so a static version is shown.
The task
Show how to connect a website, a CRM, a messenger and accounting so that no request is lost or duplicated and the manager always knows the next step.
What I did
- A website request → a contact and a deal with the budget, the plot and UTM tags
- Contact lookup by phone: a repeat request becomes a note on the same deal
- A Telegram message to the manager and a “call back within 15 minutes” task with a countdown
- Robots per stage: email, calendar, an SMS a day before the meeting, a proposal PDF, an invoice in 1C, NPS in a week
- One scenario in two API dialects: amoCRM v4 and Bitrix24 REST
Proof
- The bench runs on the page: send your own request, drag deals around, switch the API
Materials
3 · Click any item to enlarge it
What else you can hand over to me
- An AI assistant for your site that knows your prices and sends leads to Telegram
- A Telegram bot, deployed on a server
- Set up or fix the exchange between 1C and your site
- Deploy a service on a VPS and document it in a clear runbook
- A cloud pipeline for IRL streaming
A cloud IRL streaming pilot: phone → server → Twitch
When the mobile signal drops, only the scene changes and the broadcast stays up. Built and load-tested on a test bench
1C ↔ online store exchange: a live bench
Prices, stock and photos go from 1C to the site, orders come back to 1C with a reserve. Every request of the exchange is shown with its XML