Connect a whatsapp number through the official mechanism
The Owner connects a WhatsApp Business Platform number through Meta's Embedded Signup flow, so the company can start receiving and sending WhatsApp messages in the shared Inbox without ever handling a personal WhatsApp credential.
When this happens: Owner opens Admin — Channels — Connect New Channel — WhatsApp.
Step by step
- 1
Open Admin — Channels and clicks Connect New Channel — selects *WhatsApp*.
Launches Meta's Embedded Signup flow, embedded in the page.
- 2
Signs in with the company's Meta Business account, selects or creates the WhatsApp Business Account, selects or adds the phone number *+373 69 …*, and confirms.
Meta completes provisioning and returns the WABA id, the phone number id and an exchangeable authorization code to the page. Exchanges the code server-side for a system-user access token, encrypts it, and creates a
ChannelConnectionwithConnecting. Calls the phone-number metadata endpoint to verify the connection works; on success setsActiveandDisplayIdentifierto the masked number. EasyCRM shows Connected: +373 69 •• •• ••. Ready to receive messages on the channel administration screen.
Other paths
Add a second waba or number to an existing connection
If selects a different WABA or phone number than any already connected. Continues at step 4.
If something goes wrong
Owner cancels or denies
Close the Embedded Signup window before completion. No ChannelConnection is created. EasyCRM shows WhatsApp connection was not completed
Initial verification fails
If the metadata call fails (e.g. The returned token is not yet usable). Sets Error, records the failure in the error history, and shows the connection with a Connection could not be verified — try Test Connection message rather than silently leaving it at Connecting.
Good to know
- No personal WhatsApp credential is ever collected; only the system-user token from the Embedded Signup exchange is stored, encrypted.
- Only
EasyCrm.Channels.Connectholders can start a new WhatsApp connection. - The integration targets Embedded Signup v4; v2 is deprecated by Meta on 2026-10-15.