Bot + 1C / CRM: why an API, not screenshot forwarding

The most common ask: “build the bot, 1C later”. Later never comes. The client asks stock, the bot answers from a manager’s head — screenshots again.

The smallest useful loop: read status, write a slot, change status, escalate. You do not need to pour the whole ledger into Telegram.

Joints we ship most: Bitrix24 and amoCRM, 1C HTTP services, Google Sheets as a temporary source of truth, your own REST, payments.

No API yet? We add a thin layer: the bot writes a sheet or a webhook, the system pulls in batches. More honest than “full 1C in a week”.

Care covers API drift: when Telegram or your stack changes a contract, we patch the core once — for every studio bot.