↑↓ select · ENTER go · ESC close

TURKIN Map your project

Demo project Bots, AI & automation

Site integrations: WordPress, Tilda, Bitrix, OpenCart and CS-Cart with a CRM, 1C and payments

An interactive map on the page: five site platforms and three processes, a request into the CRM, an order into 1C and a payment with a receipt. For each pair you see the hook point on the platform itself (a hook, an event or a webhook), the code and the format of every request. It also shows the cases where integrations usually break: a repeat request does not create a duplicate, a CRM outage does not lose the request, a payment notification delivered twice is not processed twice.

5
site platforms
3
processes: request, order, payment
6
systems: amoCRM, Bitrix24, 1C, YooKassa, Telegram, Google Sheets
Discuss a similar task All work: bots & AI
Site integrations: WordPress, Tilda, Bitrix, OpenCart and CS-Cart with a CRM, 1C and payments
The map runs right here. Pick the site’s platform and a process to see where I hook into the site, what the handler does and what the CRM, 1C, YooKassa and Telegram receive. “Run” plays the flow step by step; click a step to see its data and code on the right. “Case” shows repeats and failures.

The task

Show how a site on a popular platform fits into the business processes: where to get the event on the site, how not to lose or duplicate data, and what the CRM, accounting, the payment service and the manager receive.

What I did

  • Five platforms, each with its own hook point: Contact Form 7 and WooCommerce hooks, a Tilda webhook, 1C-Bitrix events, OpenCart 3 events, CS-Cart hooks
  • Request → CRM: a contact lookup by phone, a deal in amoCRM (leads/complex) or Bitrix24 (crm.lead.add), a Telegram message to the manager, a row in Google Sheets
  • Order → 1C: products matched by article, the CommerceML 2.10 exchange, a reserve, a deal with products and a message to the warehouse
  • Payment → receipt: a YooKassa payment with an idempotence key and a 54-FZ receipt, the notification checked through the API, the order status on the site, the CRM stage, the payment in 1C
  • Special cases: a repeat from the same phone, the CRM is down, 1C is offline, the payment notification arrives twice
  • Every step has its data and code: PHP for WordPress, Bitrix, OpenCart and CS-Cart, Node.js for the handler

Proof

  • The map runs on the page: switch the platform, the process and the CRM, run the flows and the failures, and see on the right what is sent and by which code

4 · Click any item to enlarge it

What else you can hand over to me

  • Requests from a WordPress, Tilda or Bitrix site straight into amoCRM or Bitrix24, without duplicates
  • The exchange between your site and 1C: products, prices, stock and orders
  • Payments on the site through YooKassa: a receipt, the order status, a message to the manager
  • An AI assistant for your site that knows your prices and sends leads to Telegram
  • A Telegram bot, deployed on a server
  • Deploy a service on a VPS and document it in a clear runbook
Discuss a similar task
All work: bots & AI