1C
1C integration: a chat center that knows your orders
“When will my order arrive?” — the customer asks in a messenger, and your 1C answers: status, invoice number, delivery date. Automatically, without a manager.
14 days of the Team plan — free
Заказ 4417собран
Накладная: № 00БЯ-118823 от 06.09
Курьер: сегодня, 14:00–18:00
Оплачено: 12 400 ₽ из 12 400 ₽
up to 40%
of common questions closed automatically
0 calls
“where is my order?”
1 request
to a status in 1C
API
on the Business plan
“Where is my order?” — half of the inbound in any 1C company
The answer to this question lives in the accounting system. But a manager fetches it — by hand, on the phone, between tasks
The manager is an expensive “status” button
One request = find the order in 1C, check the stage, call the client back. Five minutes of a specialist's work for an answer the system already knows.
The client calls about every little thing
Paid? Shipped? When is the courier? While the client cannot see the status — they ask. Dozens of calls a day about the same thing.
Notifications never go out
The order was assembled Friday evening, and the client finds out on Monday — when they call themselves. The service formally exists, but the client does not feel it.
Manual mistakes
The manager mixed up the invoice, named the wrong date, forgot to call back. The accounting system is right, and the client is disappointed.
Order status without a manager
The client sends an order number in a messenger — your logic pulls the status from 1C via the Chatva REST API and replies in the conversation: stage, invoice, date, payment. Instantly and without mistakes.
- answers in seconds at any hour;
- always up to date — straight from accounting;
- a manager joins only for non-standard questions.
Заказ 4417собран
Накладная: № 00БЯ-118823 от 06.09
Курьер: сегодня, 14:00–18:00
Оплачено: 12 400 ₽ из 12 400 ₽
Notifications from accounting — by themselves
Order assembled, invoice created, payment received — 1C initiates a message to the client's messenger via POST /messages. The client knows before they even thought to ask.
- events in 1C trigger customer messages;
- any channel: Telegram, WhatsApp, MAX, VK, the site;
- templates: “order assembled”, “handed to delivery”, “invoice issued”.
Новый диалогсейчас
Telegram · Кира М.: «Здравствуйте! А есть ли рассрочка?»
Диалог без ответа 5 минут2 мин
Назначьте оператора, клиент ждёт
Counterparties under control
The contact from the conversation is checked against the 1C base: the manager instantly sees whether it is a regular client, their debt and special terms — without opening the accounting system.
- counterparty search by phone and email from the conversation;
- a new client — a new counterparty in 1C automatically;
- the conversation history is attached to the client card.
Диалог
Чатва
REST API
опрос по расписанию
1С
заказ и статус
What flows between the systems
A typical data set for the exchange
| Direction | Data | Method |
|---|---|---|
| Chatva → 1C | New conversations, contacts, question text | GET /conversations or webhook |
| 1C → customer | Order status, invoice number, delivery date | POST /messages |
| Chatva → 1C | Name, phone, email from contact collection | GET /contacts |
| 1C → customer | Invoice and payment confirmation | POST /messages |
How the integration is built
Two schemes: scheduled and event-driven
- 1
Enable the API in Chatva
On the Business plan a key is created — 1C will sign requests with it.
- 2
Set up the exchange
In 1C — a scheduled job or an HTTP service: fetch new conversations via GET /conversations, send replies via POST /messages.
- 3
Link the events
For instant reactions — Chatva webhooks: a new conversation goes straight to 1C without waiting for the schedule.
- 4
Test with a trial order
Ask the combo for a test order's status from a messenger — the answer from 1C should arrive in seconds.
Options for your configuration
The exchange is built on standard HTTP — it works everywhere
Trade Management and UNF
Scheduled jobs: every 1–5 minutes 1C pulls new conversations and replies with statuses from accounting. The classic scheme with no infrastructure changes.
ERP and CA
HTTP services on the 1C side receive Chatva webhooks: a new conversation is processed instantly, without waiting for the schedule. For busy departments.
1C:Accounting
Customer notifications about invoices and acts from accounting: invoice issued — the client gets a link in the messenger; payment received — a confirmation arrives.
Custom configuration
The Chatva REST API is plain HTTPS with JSON: connect from any language — in 1C that is the standard HTTPConnection and ReadJSON. OpenAPI included.
An office without “where is my order” calls
What automation on top of the accounting system gives
up to 40%
of common questions closed without a human
24/7
statuses available to customers
0 mistakes
in invoice numbers and dates
1C stays
the single source of truth
The manager used to spend half a day answering “shipped, invoice number such-and-such”. Now the bot replies with the status from 1C, and the manager works on orders. Calls halved.
Honest pricing
Start free and grow with your customer flow. Cancel in one click, your data stays yours.
Pay for a year and get two months free.
Start
To test the idea
0 ₽/ per month
- 1 agent
- Site widget and Telegram
- 100 chats per month
- Quick replies
Team
For sales and support teams
1 490 ₽/ per month
- 5 agents
- All channels, no limits
- Autopilot and bots
- Telegram notifications
- Analytics and ratings
Business
Chains and high volumes
4 990 ₽/ per month
- Unlimited agents
- SLA and priority support
- API and webhooks
- White label, no Chatva mention
- A dedicated manager
FAQ about the 1C integration
Any that can do HTTP exchange: UT, UNF, ERP, CA, BP and custom ones. The Chatva REST API works over HTTPS with JSON — 1C supports that natively.
Messages are signed with an author name — e.g. “Orders bot”. If the client asks for a human, the conversation goes to a manager with full context.
Not for outgoing requests from 1C — it calls the Chatva API itself. Webhooks are only needed for instant events and are received by a 1C HTTP service.
For now the API transfers text: a link to the PDF invoice from your system. The customer downloads the document via the link in the messenger.
Any 1C specialist can set up the basic exchange using our documentation. Message us — we will suggest a scheme for your configuration.
Related reading
Let 1C answer the common questions
Fewer office calls — more time for orders.