Whatspp business cloud module has suddenly stopped working.
Tried connection again, no connections appear when connection. using whatsapp business api.
Error messages or input/output bundles
InvalidConfiguration Error
This connection type is no longer supported. Please use the correct WhatsApp Business Cloud connection. - this error is being showed.
Same exact thing happened to me. My Make scenario was working 6 days ago. I{ve even updated to the new Whatsapp module with no problems at all. Why is this happeningā¦ Now the module asks me for a new conection and it doesn{t recognize the phone that I have with meta.
Same for meāIām suddenly getting the error ānumber not foundā even though the number exists on the WhatsApp Business account. It was working until March 20, 2026, but today it stopped working.
We apologize for the frustration caused by the error.
Meta has recently updated the rules governing how third-party applications connect to its API. Make is now a Tech Provider/Partner with Meta, and due to this, new stricter connection requirements have been introduced. So the old WhatsApp connections have been deprecated and are no longer supported. You will now need to create a new connection(embedded type) for WhatsApp Cloud.
Please follow the documentation to create the new connection. If you encounter any issues or errors during the process, please share a screenshot so we can investigate further.
Hi. This didnāt solve it. I cannot see my page in the business portfolio. There must be a problem in makeās auth to meta side since the test API works perfectly on my side.
Hi Vendy. Thanks for replying. Unfortunately as stated by others, this does not solve the problem. We took special care to update the Whatsapp Business Module, more than a month ago.
Starting March 17-18 the whole scenario *which worked for more than a year failed.
No matter if I try to use the new connection method. MAKE does not see any of my previously registered phone numbers* (with the API). Which are working totally fine (tested them with Postman, with 200 OK results).
Both phone numbers do not exist for MAKE and Iāve even disconnected 2FA in both of them. No use.
Another thing is that Iāve tested N8N, and everything works perfectly thereā¦ I hope you are not trying to drive future customers away. Itās been very confusingā¦ You connection method seems to work if I register a phone number directly with Whatsapp Business (on the phone itself), but not with the ones used just for Whatsapp API (to be able to send template messages).
It has been a horrible experience, and you did this without even letting us know about the change. Iām really considering moving to N8N for good, but Iām giving a chance to MAKE to fix this. The whole process has been messy, and Iām not going to wait much longer while I lose prospects.
Again, your process works just for Whatsapp Business App, but not any more for us who took special care in registering phone with the API.
Thank you for the detailed explanation, and I apologize for the issues caused by this.
Our developers contacted the Meta team, and they are discussing the current possibilities. Iāll update this thread as soon as we have some new information.
Hello Community, since I saw a lot people having the same issue I decided to create a mini tutorial where I explain how to setup You Whatsapp Business Cloud API by using:
-Webhook module to listen for messages
-HTTP module to send āmessagesā and API
You need to have access to your facebook developers account and you should have your business already verified (that you should since most of you were already using the API through make modules)
PART 1: Setup Webhook is in case that you need to listen for incoming messages.
Thank you so much for doing this. IĀ“m really grateful that you took the time to make a tutorial. It is very complex hoever, and requires so many extra steps. Granted it may solve the problem. (I will try it). ItĀ“s been almost two weeks and the engineering team has been unable to correct the problem with the Whatsapp Module.
Ramon thank you for explanatory videos. this could solve it, yet, the damage it created on my business is huge.
Iāve very complex customer care service scenarios, spending 200-300k credits monthly. changing this first module means dropping everything apart. This should have been taken care by Make itself. Migrating to n8n, at least I wonāt get any surprise updatesā¦. My frustration and disappointment is huge
We apologize for the ongoing frustration and inconvenience caused by this issue.
Our developers are currently in conversation with Meta engineers to investigate the problem further.
Weāll be updating this topic with the latest information. If you want to get the updates directly in your email inbox, please create a ticket with our Customer Care team.
Thanks vendy for getting back to us. The partnership with Meta turned out to be for worse. As mentioned by many we are losing business opportunities because of this. Especially since I was planning to increase membership usage, and I find myself in need to migrate to N8N as I wonĀ“t get surprise like this. We useres are acting like beta testers and we shouldnĀ“t. The engineering team should have detected the mess created by the new faluty Whatsapp Connection.
Anyway, IĀ“ll be looking forward for updates. Thanks a lot in advance
Hereās what solved it for me, in case it helps anyone else.
I had the same issue where the old WhatsApp connection partly looked alive, but the scenario kept breaking when saving or when using modules like Send a Message, Get Media, or Upload Media.
What I was seeing:
Watch Events sometimes still received messages
Other WhatsApp modules failed
Make showed errors like:
This connection type is no longer supported
Provided account is not compatible with whatsapp-business-cloud:getMedia
Provided account is not compatible with whatsapp-business-cloud:uploadMedia
What the real issue was:
My old WhatsApp setup had been created with the older Meta Developers flow
Make had moved to the new Meta Tech Provider / Partner embedded flow
The old connection was no longer compatible
In my case, changing the connection field alone was not enough, because some modules still kept old internal references
What worked for me, step by step:
Create a brand new WhatsApp Business Cloud connection from inside Make
In Meta Business Manager, review:
WhatsApp Accounts
People
Partners
Phone Numbers
Identify which WhatsApp account currently owns the number
Move the number into the new WhatsApp account created through the Make flow
Complete OTP verification carefully. Do not spam retries
Wait until the number status in Meta becomes Connected
Run a small test scenario first:
Watch Events
Send a Message
In Watch Events, select only Messages, not all event types
If needed, run Register a Sender
If Register a Sender fails, recreate that module from scratch. In my case, doing it in an incognito window helped
Once the test scenario works, go back to the real scenario
Recreate or fully reconfigure the WhatsApp modules with the new connection
Important lesson from my case:
Importing the old blueprint and just switching the connection was not enough
I had to recreate the WhatsApp layer in the scenario, especially modules like:
Watch Events
Send a Message
Get Media
Upload Media
Final result:
New Make connection
Number moved to the new compatible WhatsApp account
Number status changed to Connected
Test scenario worked
Real scenarios saved and worked again
Short version:
The issue was not the phone number itself.
It was the mix of an old Meta Developers based setup with the new Make embedded connection model.
If you are stuck, I strongly suggest:
Stop trying to revive the old connection
Build a new one inside Make
Confirm the number is under the new WhatsApp account
Wait for Connected
Test with a tiny scenario first
Rebuild the WhatsApp modules in production if needed
Hi Oscar i finally make my scenarios work again. I sent you a mail with tept by stpe guide that hopefully works for you, and leave a short version of it lines below. Hope you make it! Big damage to my business because its difficult to explain to my customers why you r running your business on a platform that does not give a s**** about your customers, and have to explain to your final customer that solution provided its been running on a platform that makes big changes without even taking the time to notify or announce such critical changes without announcing it to us, developers. Hope all of you can fix it. For me it was the biggest disaster ever as I have big accounts affected because of this, and Iām starting to move to N8N at a slowly pace as I have big projects and can not stand to get through this mess again, so Iāll derisk using both platforms. Unfortunately i just received a mail replying to your question, and couldnt be delivered, but i wrote a little step by step guide that may help you inside this thread
Youāre totally right, Meta is a horrible platform. They change often and with that introduce breaking changes.. Not a good developer experience. But then again, that is the life of a developer. Stuff breaks, third parties decide to switch it up out of the blue, you fix it, am I right?
Good luck on switching to n8n, if you can handle an authentication issue as HUGE as this then n8n will be a breeze to use!
What is your goal?
What is the problem & what have you tried?
Error messages or input/output bundles
Screenshots (scenario flow, module settings, errors)
