WhatsApp Business Cloud Coexistence – how to trigger one-time history sync within 24h?

Questions
1

:bullseye: What is your goal?

Hi,
today I connected my existing WhatsApp Business App number to Make using WhatsApp Business Cloud – Coexistence. During onboarding I selected Share all chats.
The connection works correctly and the Watch Events module receives new incoming messages.
My goal is to recover the recent WhatsApp history that was shared during onboarding, ideally for the period 20/08/2026–05/09/2026, without disconnecting or re-onboarding the number.

:thinking: What is the problem & what have you tried?

The WhatsApp Business Cloud Coexistence connection is working and Watch Events receives new incoming messages correctly.
I verified that Make’s official WhatsApp Business Cloud app does not expose any module for chat history, list messages, smb_app_data, or sync_type=history.
I also tested the webhook successfully with real incoming messages.
What I have not been able to determine is whether Make automatically triggers Meta’s one-time Coexistence history sync during onboarding, or whether there is a supported way to trigger it afterward without disconnecting or re-onboarding the number.
This is time-sensitive because I want to avoid losing the onboarding window.

4

Hi Cristobal, since your Coexistence connection is already receiving new messages, I wouldn’t expect ‘Watch Events’ to recover the 20/08–05/09 history, it only receives events delivered after the webhook is active.

The important question is whether Meta actually completed the one-time ‘history’ sync during Coexistence onboarding. Make’s standard WhatsApp Cloud modules don’t expose a way to manually request that sync afterward.

I’d check the webhook/event logs around the original onboarding for a ‘history’/sync event. If Meta didn’t deliver the history during that onboarding window, I don’t believe there’s a supported Make module/API call that can trigger the historical sync afterward without going through Meta’s Coexistence onboarding flow again.

So I’d avoid disconnecting anything for now and first verify whether Meta actually sent the historical sync to the WABA during onboarding.