Why can’t I just get the webhook URI? It didn’t use to be this way, the webhook URI used to be displayed right under the webhook name, now it only says “we read your mind, we attached this webhook automatically for you”. No more information, it’s a bit frustrating.
As I’m configuring a Flow in WhatsApp Business, I need the webhook URI to establish the endpoint. It is a requirement of this process.
No, you don’t. Once you established your connection to WhatsApp Business Cloud, Make “reads your mind” and sets everything up for you. No need to bother with any configuration on Meta’s side.
Haven’t you tried sending a message to your test number and watching the triggering of the scenario?
The only reason you would use the Webhook’s addres would be to access it from some other app via URL call. But that would trigger a response via WhatsApp Bussiness API (WABA) and this, my friend, is completely against the Terms of Use and would get your number banned from Meta in no time.
Think of the connection between Make and WABA as a VPN. Once established, you just can’t inject anything in it.
Thus, it’s simply a compliance issue between Make and Meta.
I cannot send a Flow without having entered a webhook URI.
it is true that the recently updated “Watch Events” module for WhatsApp Business Cloud in Make can receive WhatsApp messages without the need to set up the webhook in Meta Developer, but it cannot handle receiving input from a WhatsApp Business Flow because it does not provide the user with a webhook URI.
Has anyone successfully established a communication between a Flow and Make using the WhatsApp Business Cloud modules?
