Development of a WhatsApp bot with Bitrix24 integration
An online store processes 300 orders a day. Every second customer writes to support asking about order status. Operators are overloaded, responses are delayed. The standard WhatsApp doesn't work — an automated bot integrated with CRM is needed. Without integration, each incoming message means a manual search for the order, switching between windows, and wasted time. Bitrix24 allows automatic creation of leads, deals, and activities from chat. But for this to work, you need to properly connect the API, configure webhooks, and handle Meta's restrictions. WhatsApp Business API is the only legal way, and we'll explain how to connect it to Bitrix24. We'll cover two main approaches: through an official BSP provider (Wazzup, 360dialog) and the unofficial Green API, and show a bot architecture on a specific case.
How to connect WhatsApp to Bitrix24 without risk of blocking?
Meta does not give direct access to WhatsApp Business API — you work through Business Solution Providers (BSPs): 360dialog, Twilio, MessageBird, WABA.cloud. The provider registers your number in WhatsApp Business and issues API keys. The official path guarantees stability, compliance with Meta policy, and the ability to use message templates. Without it, the number gets blocked after sending a few dozen outgoing messages. The first message to a customer (not a reply to an incoming message) must go through an approved template — moderation takes 24–72 hours. Arbitrary text is only allowed in response to an incoming message within 24 hours.
What is a BSP provider and why is it needed?
Popular options for the Russian market:
- Green API — a Russian provider, fast registration, has a ready module for Bitrix24. Technically uses a WhatsApp web client, which is unofficial, but for medium businesses it's a working option.
- Wazzup — native integration with Bitrix24, an official application in the marketplace. Easier to configure, but limits custom logic.
- Chat2Desk — an omnichannel service with WhatsApp and Bitrix24 support.
Bot architecture via Green API + Bitrix24
Client in WhatsApp ↓ Green API (webhook instanceId + apiTokenInstance) ↓ Bot server ↓ ↓ Bot logic Bitrix24 REST API (crm.lead.add, crm.contact.list, etc.) Receiving incoming messages:
GET https://api.green-api.com/waInstance{instanceId}/receiveNotification/{apiTokenInstance} Reply in WhatsApp:
POST https://api.green-api.com/waInstance{instanceId}/sendMessage/{apiTokenInstance} { "chatId": "[email protected]", "message": "Hello! How can I help?" } Integration with Bitrix24 is similar to a Telegram bot: search for contact by phone number, create lead, record activities in timeline.
Provider comparison
| Provider | Setup | Integration with Bitrix24 | Custom logic |
|---|---|---|---|
| Wazzup | Easy (via marketplace) | Native, ready-made | Limited to routing |
| Green API | Medium (REST API) | Via module or custom | Full freedom |
| Chat2Desk | Medium (web interface) | Via module | Limited by settings |
Green API is easier to set up for a custom bot than Wazzup, roughly twice as fast if non-standard logic is needed.
Key differences from Telegram
WhatsApp supports limited formatting: italic, bold, strikethrough, monospace. No HTML tags, no Reply buttons (only via official API Templates). In unofficial APIs (Green API), buttons are not available — only text menu: "Write 1 — order status, 2 — contact operator". Through the official API, Interactive Messages with buttons are available, but only within approved templates.
Media transfers well: images, documents, voice messages. The bot can receive photos (e.g., for a return request) and save them to Bitrix24 Drive via disk.folder.uploadfile.
Integration via Wazzup ready module
If there is no need to implement complex bot logic, it's simpler to use Wazzup with ready integration:
- Register in Wazzup, connect a WhatsApp number.
- Install the Wazzup app from Bitrix24 marketplace.
- Configure mapping: incoming WhatsApp messages → open line → lead/deal in CRM.
- Operators reply from Bitrix24, the client receives the answer in WhatsApp.
Limitation: no custom bot logic — only routing to operators.
Case study: bot for delivery status notifications
Our client — an electronics online store with 200–400 orders per day. Customers flooded support with "where is my order" questions. We developed an automatic bot on Green API.
Solution: when the order status changes in CRM (deal stage) → webhook → bot server → send notification via WhatsApp.
def on_deal_stage_change(deal_id, new_stage): deal = bitrix.get_deal(deal_id) phone = deal['CONTACT_PHONE'] whatsapp_id = f"{phone.replace('+', '')}@c.us" messages = { 'ACCEPTED': 'Your order has been accepted for processing. Order number: {order_num}', 'SHIPPED': 'Your order has been shipped. Tracking number: {track}', 'DELIVERED': 'Your order has been delivered. Thank you for your purchase!' } if new_stage in messages: green_api.send_message(whatsapp_id, messages[new_stage].format(**deal)) Additionally: the bot receives an incoming reply "track" → responds with a tracking link; "operator" → transfers to support queue.
Result: support inquiries about delivery status dropped by 60% in the first two weeks. The client saved up to 150,000 rubles per month on operator salaries.
What's included in turnkey bot development
- Requirements analysis and provider selection
- Architecture design (server, API, CRM events)
- Bot implementation (command handling, REST integration)
- Business process setup (outgoing notifications by status)
- Testing (unit, integration)
- Documentation and operator training
- Production deployment and monitoring
- Technical support for 1 month
Estimated timeframes and cost
| Component | Effort |
|---|---|
| Provider setup (Green API / Wazzup) | 4–8 h |
| Basic bot (text commands) | 16–24 h |
| CRM Bitrix24 integration | 8–16 h |
| Outgoing notifications by CRM events | 8–16 h |
| Media reception and upload to Drive | 4–8 h |
| Deployment and monitoring | 4–8 h |
The average budget for such projects ranges from 150,000 to 300,000 rubles depending on complexity. Cost is calculated individually. Contact us to evaluate your project.
Typical integration mistakes
- Using unofficial clients — leads to number blocking.
- Ignoring message template requirements — first outgoing messages get rejected.
- Lack of fallback to operator for unrecognized commands — worsens user experience.
Checklist before start
- Verified Meta Business account - BSP provider selection - Approved templates for first outgoing message - API keys for Green API / Wazzup - Test WhatsApp numberOur team holds Bitrix certifications and has experience with over 50 projects integrating CRM with messengers. Order turnkey development — we guarantee a quality result and post-launch support. Get a consultation on your project. Contact us to discuss your scenario.