A self-hosted bridge that lands inbound WhatsApp messages in a Bitrix24 Open Channel — auto-creating a Lead per new customer — and relays your operators' replies straight back to the customer on WhatsApp.
Built for reliability — no inbound message is silently lost, no outbound reply is silently duplicated.
Inbound WhatsApp → Open Channel, and operator replies → WhatsApp, end to end as text.
Each new customer number auto-creates a Bitrix Lead in the Contact Center.
Queued jobs retry with backoff and dead-letter on terminal failure — recoverable, never lost.
Inbound deduped on wamid, outbound on the Bitrix message id — no doubles on re-delivery.
Secrets live encrypted in the DB, edited via a token-gated admin form — .env is only a fallback.
The Bitrix OAuth grant is refreshed proactively and on demand — sending keeps working past the hourly expiry.
Every webhook is recorded with a correlation id; /health exposes DB, queue depth & failures.
Raw payloads are persisted and replayable; PII is pruned automatically on a schedule.
Two independent, queue-backed pipelines — each audited and idempotent.
POST /webhook/whatsapp (HMAC-verified, audit-logged).wamid and queued.imconnector.send.messages drops it into the Open Channel.OnImConnectorMessageAdd → POST /bitrix/events (token-gated)./{phone-number-id}/messages delivers it.The documentation walks through install, connector activation, credentials and verification — step by step.
Open the documentation →