WhatsApp Business Cloud BSUID support
Michael Palance
Native WhatsApp Business Cloud Send Message module support for BSUID recipients using Meta’s recipient field.
Our WhatsApp webhook now receives users without phone numbers. Instead, the webhook includes a Business-Scoped User ID (BSUID) in messages.from_user_id and contacts.user_id.
The current WhatsApp Business Cloud — Send a Message module exposes only the to recipient field. Sending the BSUID through to was accepted by WhatsApp but later failed with error 131026 — Message undeliverable.
Meta’s newer WhatsApp username flow appears to require sending the BSUID through the recipient field while continuing to use to for phone-number recipients.
Does the current Make WhatsApp Business Cloud module support sending to BSUIDs?
If not, is support for the recipient field planned?
Is there a recommended Make-native workaround that does not require a separate Meta Developer App or access token?
What is the expected timeline or tracking reference for BSUID support?
We need to preserve normal phone-number messaging and only use BSUID handling when messages.from is absent.
Log In
Delight favour
One thing worth considering is keeping recipient identification separate from the message-sending logic.
The workflow could first check whether a phone number is available. If it is, use the existing phone-number recipient flow. If only a BSUID is available, route the request through the appropriate API payload, provided the current Meta API supports that recipient format.
This would preserve the existing phone-number workflow while allowing a separate path for BSUID recipients.
The important part is validating the exact API request and response before assuming the alternative recipient field is supported.