How WhatsApp Syncs with Bitrix24 CRM in Real Time

WhatsApp messages reach TimelinesAI almost instantly, the same as WhatsApp Web. What happens next in Bitrix24 depends on one setting: by default, messages group into a single activity per chat per day — not real-time. Switching to one activity per message makes the CRM update in real time too.

"Real time" is really two separate questions, and most explanations answer only the first one.

A common version of this: a sales manager watches a rep reply to a lead on WhatsApp, then checks the Deal in Bitrix24 a minute later and sees nothing. The message wasn't lost — it's sitting in a queue that updates once a day, waiting to be bundled with whatever else that chat sends before the day ends.

The first is how fast a WhatsApp message reaches TimelinesAI. The second — the one people are usually actually asking — is how fast it shows up as something you can see in Bitrix24. Those are different systems moving at different speeds, and the gap between them is exactly why "why isn't Bitrix24 syncing in real time" is a common search. If you haven't connected WhatsApp to Bitrix24 yet, start with the setup guide — this piece picks up from there and explains what actually happens once it's running.

The two-speed mechanic

WhatsApp to TimelinesAI is effectively instant. Bitrix24 to TimelinesAI is not, by default — and that single setting is the whole answer to most real-time questions.

Leg one: WhatsApp to TimelinesAI. A message sent or received on a connected WhatsApp number appears in the TimelinesAI workspace essentially immediately — the same underlying mechanism as WhatsApp Web or any linked device.

Leg two: TimelinesAI to Bitrix24. This is where the setting lives. Our own setup guide states it plainly: "the default is one activity per chat per day; admins can switch to one activity per message." On the default, every message from a chat that day gets bundled into a single activity, updated once. On per-message, each message logs as its own activity as it happens — that is the setting that actually delivers real-time in the CRM.

Why it matters: most Bitrix24 accounts run on the default without knowing it's a choice. If a message from ten minutes ago isn't showing up as a separate activity in a Deal, the connection almost certainly isn't broken — the account is just on daily grouping, doing exactly what it's configured to do.

There is a third path worth knowing about if you're building custom automation rather than using the native Activity log: webhooks. Webhook delivery is configured separately again — immediate, or aggregated at 1, 6, 12, or 24-hour intervals. It's a different mechanism from CRM Activity logging, built for piping messages into external tools like Make.com rather than the built-in Activity feed, and it has its own timing setting entirely independent of Steps 3 and 4 below.

What determines which Bitrix24 record a message lands on

Every message is matched to a Bitrix24 record by phone number, and a new Contact is created automatically when no match exists — the same matching logic documented for Pipedrive, running on the same underlying mechanism for Bitrix24.

TimelinesAI's webhook checks the sender's number against Bitrix24 Contacts. A match logs the activity there. No match creates a new Contact from the number, then logs to that.

Why it matters: this is independent of the real-time setting above. A message can be correctly and instantly matched to the right Contact while still waiting inside a bundled daily activity — matching and timing are two different mechanisms, and troubleshooting one by adjusting the other is a common dead end. Diagnosing a "wrong Contact" problem by fiddling with the Activity-logging setting wastes time — it won't touch the matching logic at all.

Before you start

• Bitrix24 admin rights — to authorize the integration and to change the Activity logging setting.
• WhatsApp already connected to Bitrix24 — this guide assumes that part is done. If not, the setup guide covers it.
• About five minutes to review and adjust the settings covered below.

Step 1: Confirm your WhatsApp connection is active

Before touching any timing setting, confirm the underlying connection is actually live — an inactive connection looks identical to a slow one from inside Bitrix24. Full connection steps here if you haven't done this yet.

Why it matters: the single most common cause of "nothing is syncing at all" isn't a sync-speed setting — it's a WhatsApp connection that quietly dropped. Rule that out first.

Step 2: Authorize the Bitrix24 app once, at workspace level

Install the app from the Bitrix24 Marketplace and authorize it with an admin account. This happens once for the whole workspace, not per number or per user.

Why it matters: authorization scope determines what the sync can reach. An admin account is required for the Activity-logging setting in the next step to be visible and changeable at all.

Step 3: Switch Activity logging from daily to per-message

This is the step that actually makes Bitrix24 update in real time. In the integration's CRM logging settings, change activity creation from the daily-grouped default to one activity per message.

Why it matters: this single setting is the entire difference between "messages show up once a day, bundled" and "messages show up as they happen." If the goal is genuinely real-time visibility inside Bitrix24 — a live deal desk, a support queue, anything time-sensitive — this is the one setting that delivers it. Everything else in this guide is context around this step.

Step 4: Decide how unmatched numbers create Contacts

Choose what happens when a message arrives from a number with no existing Bitrix24 match — a new Contact, a Lead, or nothing, depending on what the integration offers in your setup.

Why it matters: on a high-volume number, auto-creating a record for every unmatched sender can flood Bitrix24 with one-off contacts that were never real leads. Match this setting to how the number is actually used, the same consideration covered in more depth for Pipedrive in our sync mechanics guide. A dedicated sales number where every new sender is a genuine prospect usually wants auto-creation on. A general support or enquiries line usually doesn't — most of what arrives there was never going to become a Deal.

Step 5: Confirm messages are actually landing in real time

Send a test message and time how long it takes to appear as an Activity in Bitrix24 — this is the only way to know the per-message setting actually took effect, rather than assuming it did.

1. Send a WhatsApp message from a number with an existing Bitrix24 match.
2. Open that Contact or Deal in Bitrix24 immediately.
3. Confirm the message appears as its own Activity, not bundled with anything else.
4. Send a second message a few minutes later and confirm it creates a second, separate Activity rather than updating the first.

If step 4 doesn't hold — messages are still bundling — the setting from Step 3 didn't save, or a different profile or Team is generating the activity under different settings. Re-check Step 3 directly in the settings screen rather than assuming the earlier change is still in effect; settings that don't visibly confirm a save are the most common reason this test fails.

Common problems and how to fix them

Messages aren't appearing in real time. Almost always the daily-grouping default is still active. Revisit Step 3 and confirm the change actually saved.

Nothing is syncing at all, not even daily. This is a connection problem, not a timing one — see Step 1. Reconnect the WhatsApp account and confirm the workspace's Bitrix24 authorization is still active.

Messages are landing on the wrong Contact, or duplicating one. This is the matching mechanism, not the timing setting — the same root cause documented for Pipedrive: duplicate Contact records already in Bitrix24 confuse the phone-number match. Dedupe in Bitrix24 first.

Real-time worked for a while, then activities went back to bundling. Check whether the Activity-logging setting was reset — this can happen after reauthorizing the Bitrix24 connection or reinstalling the app, since some settings don't persist across a full reconnection.

It worked, then stopped. Check whether the connected WhatsApp account's phone went offline — the connection depends on that device staying reachable, independent of any Bitrix24 setting.

A teammate says it's real-time for them but not for me. Activity-logging settings can differ by Team or by the profile that connected the number — this is a configuration difference between two setups, not an inconsistent product. Compare the actual settings screen on both accounts rather than assuming they match.

Some conversations sync in real time, others don't. Check whether they're on different Teams or profiles with different Activity-logging settings — the per-message switch in Step 3 can be workspace-wide or per-connection depending on setup, so a mixed result usually means a mixed configuration.

Frequently asked questions

Is WhatsApp to Bitrix24 sync actually real-time?

The WhatsApp-to-TimelinesAI leg is, essentially. The TimelinesAI-to-Bitrix24 leg depends on a setting: daily-grouped by default, or true real-time once switched to one activity per message.

Why does it take up to 24 hours for a message to show up?

Because the account is on the default Activity-logging setting, which bundles a chat's messages into one activity per day rather than logging each one as it happens. Switching to per-message resolves this.

Should I use daily or per-message logging?

Per-message if real-time visibility matters — active deals, live support. Daily if the number handles high volume and a daily summary is enough; per-message on a busy line can generate a lot of individual Activities. As a rough guide: a number handling dozens of conversations a day can generate a genuinely long Activity list on per-message — worth it for a small, high-value pipeline, noisy for a high-volume support line.

Does switching to per-message cost more?

No — it's a configuration setting within the integration, not a plan-tier feature. Pricing depends on seats, not on this setting.

Do webhooks and CRM Activities sync on the same schedule?

No, they're separate and independently configurable. Webhook delivery can be immediate or aggregated at set intervals (1, 6, 12, or 24 hours); CRM Activity logging is the separate daily-vs-per-message setting covered in this guide.

Will messages sent before I set this up backfill into Bitrix24?

No. Sync starts from the point of connection forward; messages sent before the integration was set up remain on the phone and in the TimelinesAI workspace, not retroactively in Bitrix24.

Does group-chat sync follow the same daily-vs-per-message setting?

Check this directly in your workspace's Bitrix24 integration settings — it isn't something we can confirm generally here, since group-chat handling is configured separately from one-to-one chats in some setups.

Get started

Already connected? Check your Activity-logging setting today — it's the difference between a daily summary and real-time visibility. Not connected yet? Start with the setup guide, or see how the cost compares to staying manual. Get started with WhatsApp for Bitrix24 — no credit card required.