WhatsApp Business Cloud Coexistence connection fails with “Resource not found” after successful Meta setup

Questions
1

:bullseye: What is your goal?

Connect my existing WhatsApp Business App number to Make using WhatsApp Business Cloud in Coexistence mode, while keeping the WhatsApp Business mobile app active.

:thinking: What is the problem & what have you tried?

I am trying to connect an existing WhatsApp Business App number to Make using WhatsApp Business Cloud – Coexistence mode.

The Meta onboarding process completes successfully. I select “Connect a WhatsApp Business App”, enter my existing verified phone number, confirm the AurasNet WhatsApp Business account, grant Make the requested permissions, and Meta finally displays “Your account is connected to Make.”

However, after clicking Finish, the callback to Make ends on a blank page displaying:

“Resource not found”

As a result, no WhatsApp connection/credential is created in Make.

I have retried the onboarding several times with the same result.

I also verified in WhatsApp Manager that:

the phone number status is Connected;
the WhatsApp Business App remains active;
Two-step verification is disabled;
the Phone Number ID is 3240546492626190.

Meta Business Settings also shows Make as a partner with access to the WhatsApp account.

I do not want to migrate or deregister the number because the goal is specifically to use Coexistence and keep the WhatsApp Business mobile app active.

Could you please help determine why the Make OAuth callback returns “Resource not found” even though Meta reports that the account was successfully connected to Make?

:clipboard: Error messages or input/output bundles

Meta onboarding completes successfully and displays: “Your account is connected to Make.”

After clicking Finish, the browser is redirected to the Make OAuth callback and displays:

Resource not found

No WhatsApp Business Cloud connection is then created in Make Credentials.

4

Hello Make Support,

I am still unable to create my WhatsApp Business Cloud connection in Make using WhatsApp Business App (Coexistence).

We have now completed an extensive verification on the Meta side.

The Meta onboarding completes successfully and displays:
“Your account is connected to Make.”

We have confirmed the following:

  • WhatsApp Business Account: AurasNet
  • Active WABA ID: 149264049643018
  • Phone Number ID: 3240546492626190
  • Phone number status in Meta: Connected
  • Time zone: Europe/Paris
  • Account type: WhatsApp Business App
  • Make is now listed in Meta Business Settings as a partner with full control of this active WABA.

Therefore, Meta appears to complete the authorization and asset-sharing process successfully.

However, immediately after clicking Finish in the Meta onboarding, the browser is redirected to:

make.com/oauth/cb/whatsapp-business-cloud?...

and Make displays:

Resource not found

When I return to my Make scenario, the WhatsApp Business Cloud module still displays “Create a connection”. Therefore the connection is not being saved in Make.

We also identified a second/older WABA associated with the same business during troubleshooting. Make’s partner access was removed from that old WABA before repeating the onboarding. The new onboarding then correctly assigned Make to the active WABA above, but the callback still returned Resource not found.

Could you please investigate the OAuth callback / connection creation on the Make side and confirm why the connection is not being created even though Meta successfully grants Make access to the active WABA?

Please let me know if you need the callback URL, screenshots, scenario ID, WABA ID or any additional diagnostic information.

Thank you.

5

Hey there :waving_hand:

You can open a ticket with the Customer Care team. This community consists of Make users and enthusiasts who can help you only so far. The official Make support has access to internal systems and logs, and can help you with technical issues, bugs, and all other questions regarding Make.

If you cannot log a ticket, please upgrade to a paid plan.

When you get the issue resolved, feel free to post it in the community to contribute to the knowledge base, we’re building here!

Thank you :folded_hands:

6

We are connecting an existing WhatsApp Business mobile-app number to Make using WhatsApp Business Cloud in Coexistence mode.

Meta recognises the correct business profile and finishes with a connected-to-Make confirmation. WhatsApp Manager shows Connected, and Make appears as an authorised partner. After clicking Finish, however, we get Resource not found. Make’s authenticated Connections page still has no saved native connection.

The documented retry using an existing account is also unclear: Regular mode marks this existing Coexistence number Ineligible with the message This number can’t be shared with this app. Coexistence recognises the phone again, but we still have no saved connection.

The first attempt involved an expired Make session. We signed back in, but later retries involved multiple popup attempts, so we cannot rule out a stale popup/parent association. We are looking for a supported clean recovery procedure, not claiming that the root cause is established.

Has anyone recovered the native connection while preserving the existing WhatsApp Business app and its history? Which retry mode applies after Meta has already onboarded the Coexistence account? If the legacy token connection is supported for this case, is there current official guidance covering the required webhook and message-echo handling?

The private support form currently offers our Free-plan account only self-help resources and an upgrade link. We have not removed the partner grant, deregistered the number, disabled two-factor authentication or created another WhatsApp account.