Connect our existing WhatsApp Business App number to Make using the official WhatsApp Business Cloud integration in Coexistence mode, while keeping the WhatsApp Business mobile app active. We want to use Make’s Watch Events module to receive incoming customer WhatsApp messages for automation.
What is the problem & what have you tried?
Meta successfully completes the WhatsApp Business App Coexistence embedded signup and confirms the existing production WhatsApp Business number. The number also shows as Connected in Meta Business Settings.
However, after clicking Finish, the callback to Make displays “Resource not found.” Make then reports “Failed to verify connection [400].”
The connection is never saved in Make, and the Make Connections/Credentials page still shows no connections created.
We have retried the Coexistence onboarding and receive the same result. WhatsApp two-step verification / 2FA is OFF. We do not want to create another WhatsApp Business Account, test number, or replace/disconnect our existing production WhatsApp Business App number.
Error messages or input/output bundles
Meta callback:
Resource not found
Make connection verification:
Failed to verify connection ‘Edward’s WhatsApp Business Cloud connection’. [400]
Result:
The WhatsApp Business Cloud connection is not saved in Make, and the Connections/Credentials page remains empty.
Hi Edward, the important clue is that Meta completes Embedded Signup and shows the account as connected, but the failure happens when Make verifies the connection after the callback. That makes this look different from a normal WhatsApp permission or 2FA issue.
I’d check whether the same WABA, Business Portfolio and phone number that Meta just connected are exposing the expected Cloud API phone resource to Make. In a very similar Coexistence case, Make was reaching the verification stage but couldn’t resolve the Cloud API resource, resulting in the same Resource not found → 400 sequence.
If those IDs and access all line up, I wouldn’t keep repeating the Embedded Signup or disconnecting the production number. At that point, I’d give Make Support the exact callback time/error and ask them to check which Meta resource their connection-verification request is trying to resolve.
That should tell you whether this is a Meta resource/provisioning issue or a Make-side verification issue without risking the existing WhatsApp Business App setup.
It sounds like the Meta Coexistence setup is completing successfully, but the connection verification between Meta and Make is failing afterward.
Could this be related to the WhatsApp Business Account or phone number ID not being correctly passed back to Make during the embedded signup callback? Since Meta shows the number as connected and the setup finishes successfully, it seems the issue occurs specifically when Make tries to verify the connection.
Has anyone encountered the same “Resource not found” / 400 error with an existing WhatsApp Business App number in Coexistence mode? Any guidance on which Meta Business or WhatsApp settings/permissions should be checked would be helpful.
We reproduced the issue again today using the official WhatsApp Business Cloud → WhatsApp Business App (Coexistence) signup flow.
This time, Meta successfully recognized and selected our existing registered WhatsApp Business number. The authorization process completed successfully and Meta explicitly displayed: “Your account is connected to Make.”
After clicking Finish, the callback returned to Make and immediately displayed: “Resource not found.”
We then checked Make → Credentials → Connections. Searching for “WhatsApp” returns “No results were found”, confirming that no WhatsApp Business Cloud credential was created despite Meta completing the authorization successfully.
Therefore, the failure appears to occur after successful Meta authorization, during Make’s callback/connection verification step.
Could someone from Make please confirm whether this is a known issue with the current Coexistence connection flow, or advise what Make-side resource/identifier is failing to resolve?
Thank you for the suggestions. We checked the Meta resources in more detail.
For the production WhatsApp Business Account (“Inspired Business And Home”), we confirmed:
The production WABA exists in Meta Business Settings.
The existing WhatsApp Business App phone number is attached to that WABA.
The production phone number shows Status: Connected.
Opening the production phone profile shows a Meta phone profile/resource ID.
Under the production WABA’s Partners tab, Make is already assigned as a partner with full control.
We have not disconnected or migrated the production number, and we have not created another WABA.
Despite these Meta-side checks, the Coexistence Embedded Signup still completes successfully and Meta confirms the account is connected to Make, but the callback then returns “Resource not found” and Make reports “Failed to verify connection [400]”. No WhatsApp credential is saved in Make.
At this point, is there another Meta resource or permission that should be checked, or does this need Make Support to inspect which WABA/phone resource ID its connection-verification request is attempting to resolve?
Hi, I’m experiencing the same issue with WhatsApp Business Cloud Coexistence.
Meta Embedded Signup completes successfully and my existing WhatsApp Business number remains working normally in the mobile app.
I verified in Meta Business Settings that:
The WhatsApp Business Account was successfully created inside my Business Portfolio.
My existing phone number appears under the WhatsApp account.
The phone number status is Connected.
Meta also created a Phone Profile Identifier for the number.
However, after clicking Finish in Meta, the callback to Make fails with “Resource not found”. On a second attempt, the Make OAuth page returned:
{"message":"Not found"}
In Make → Credentials → Connections, no WhatsApp Business Cloud connection is created or saved.
I specifically need Coexistence because this is an active business number and I need to continue using it in the WhatsApp Business mobile app. I do not want to migrate, deregister, or disconnect the number.
Has anyone found a workaround, or can Make confirm whether this is currently an issue with the Coexistence callback/connection verification?
If you still can’t resolve this, I highly recommend reaching out to our Customer Care team. They are the Make experts with the right access and tools to help you troubleshoot these issues.
Meta completes the WhatsApp Business Cloud setup in Coexistence mode and displays the connected account. Upon completion, Make returns a “Resource not found” error; previously, it also showed a 400 error and failed to save the connection. The number is already registered, and Make has full control within Meta. We are repeating the setup using the same assets, without deleting or migrating the number. How can we complete the connection while retaining the WhatsApp Business application?
Meta completes the WhatsApp Business Cloud registration in Coexistence mode and shows the connected account. Upon completion, Make returns a “Resource not found” error; previously, it also displayed a 400 error and failed to save any connection. The number is already registered, and Make has full control within Meta. We are repeating the registration with the same assets, without deleting or migrating the number. How can we complete the connection while keeping the WhatsApp Business application?
What is your goal?
What is the problem & what have you tried?
Error messages or input/output bundles
Screenshots (scenario flow, module settings, errors)