If your Make.com scenario never finishes and the WhatsApp connector hangs on Creating a connection, the common cause is OAuth or Business Manager misconfiguration. This whatsapp business cloud connection stuck usually means the Meta App is in Development, missing Graph API scopes, or the wrong phone number or token is used.
Why whatsapp business cloud connection stuck happens
The creating a connection hang is almost always an authentication or configuration problem, not a Make.com bug. Typical root causes are a Meta App still in Development mode, missing Graph API permissions, expired or wrong access tokens, or picking a Facebook Page when the connector needs the WhatsApp phone number. Make also needs the OAuth redirect and client credentials to match exactly, otherwise you will see errors like the connection popup failing or an immediate 401.
Step-by-step Make.com troubleshooting checklist
- Confirm the Meta App state. Open your Meta for Developers App, confirm the app is switched to Live and the business that owns the WhatsApp Business Account is verified in Business Manager. If the app is still in Development you will be blocked from real accounts.
- Check Business Manager ownership. In Business Settings, confirm the WhatsApp Business Account is listed under the same Business Manager that owns the Meta App. Also verify the phone number is added to that WhatsApp Business Account and shows as linked.
- Verify required Graph API permissions. Ensure the app has the WhatsApp permissions requested, for example
whatsapp_business_messagingandwhatsapp_business_management, plusbusiness_managementif you manage assets. These scopes must be available during the OAuth consent build or granted to the System User if you use tokens. - Use the correct connector target. When Make prompts, choose the WhatsApp phone number or WhatsApp Business Account, not a Facebook Page. Confusion between Page and phone number is common. The connector shows the phone number or a
phone_number_idoption in the selection list. - Confirm App ID and Secret. If the Make oauth flow requires you to paste an
App IDandApp Secret, verify the secret is current. A wrong secret returns the error shown in this Make forum thread, [401] The provided client secret is invalid. Regenerate the secret only in the Meta App settings and copy it exactly. - Check the OAuth redirect URI in the Meta App. Open the connection flow in Make and note the redirect URL shown, then add that exact URL to your Meta App Valid OAuth Redirect URIs. Mismatched redirect URIs cause the popup to hang.
- Watch the browser during the popup. If the connection stalls on
Creating a connection, open DevTools and look for blocked third party cookies, popup blockers, or 3rd party consent prompts. Try an Incognito window and login with the Business Admin account that is owner of the WhatsApp Business Account. - Check token lifetime and refresh. If you used a manually issued token, confirm it has not expired. If you are using short lived user tokens, reauthenticate. For System User tokens or long lived tokens, reissue if you see authentication failures.
- Retry in a different browser and account. If multiple developers use different Facebook accounts, make sure the account performing OAuth is an Admin on the Business Manager and has access to the WhatsApp Business Account.
Make.com specific OAuth flow mistakes most forum answers miss
Make has two common OAuth surprises. First, if you use the built-in connector and then switch to a custom Meta App, Make still stores the old connection settings. Always delete the old connection under the Connections list then create a fresh connection with the correct App ID and Secret. Second, if you are using a custom app, do not skip adding Make's redirect URI into the Meta App. The connection popup looks like it succeeds but will hang when the redirect is blocked or the app consent screen does not include the WhatsApp scopes.
Also be careful with the scope consent screen. If your Meta App requests scopes that are not approved for public use, the popup might prompt for an admin-only consent that fails silently. Use a Business Admin account for the OAuth step.
Tool notes: n8n, Make.com and Zapier
Make.com, n8n and Zapier all present similar blockers but differ in the connector behaviour. For Make.com, use the WhatsApp Business Cloud module connection popup and follow the checklist above. If you prefer n8n, you will typically use the HTTP Request node and your own token, so verify the token and phone_number_id in your request body. For Zapier, check the Auth step for the WhatsApp integration and confirm you select the phone number rather than a Page.
In n8n, because you directly control the HTTP request, you can debug faster: attach a Set node before the HTTP Request node to log the token and headers, then run manually. In Make, use scenario run history to inspect the module error and open the connection popup again with a cleared cache.
How to stop it happening again
- Document the App ID, App Secret rotation date and who is allowed to regenerate secrets.
- Use a single Business Manager to own the Meta App and the WhatsApp Business Account, avoid cross-BM setups.
- Set up a System User and assign roles for long lived server tokens when possible, this reduces interactive OAuth steps.
- Automate token refresh and store tokens securely. If you must re-authenticate, have a checklist so the Dev or Admin knows to use the Business Admin account for the OAuth flow.
When to get help
If you followed every step and the connector still hangs, capture the browser console logs and the exact error in Make scenario history. Post those details to Make Forum threads like this one about the connection hang, Make forum: WhatsApp Business Cloud connection stuck. If you get a specific 401 or client secret error, regenerate the secret in the Meta App and update the Make connection immediately. If the Business Manager or WhatsApp Business Account ownership is unclear, open a support ticket with Meta Business Support and include the Business Manager ID, WhatsApp Business Account ID and the phone number ID.
If you are sending messages and need a how-to after the connection is fixed, see our guide on sending WhatsApp notifications with Make.com or n8n, How to Send WhatsApp Notification from Make.com or n8n, which steps through the phone_number_id and sample payload.
Learn to build automations like this with Automate Naija.
Frequently asked questions
Why does Make.com say Creating a connection but never finish?
That status usually means OAuth did not complete. Common causes are the Meta App still in Development, missing Graph API permissions, a redirect URI mismatch, or the account doing the OAuth is not an Admin of the Business Manager that owns the WhatsApp Business Account. Check the browser console for blocked popups or cookie issues during the popup.
Which Graph API scopes do I need for WhatsApp Business Cloud connections?
Make sure your Meta App requests WhatsApp scopes such as whatsapp_business_messaging and whatsapp_business_management, plus business_management where applicable. These must be visible in the OAuth consent or granted to a System User. If scopes are missing the connector may hang or fail with permission errors.
I see [401] The provided client secret is invalid, what do I do?
Regenerate the App Secret in Meta for Developers and paste the new secret exactly into Make when creating the connection. Also ensure you are using the App that is in Live mode and that the Business Admin performed the OAuth. See the Make forum thread reporting the 401 for common troubleshooting steps.
How do I avoid this problem in future?
Keep App and Business ownership aligned, document secret rotations, use System User tokens for server workflows, and add Make's OAuth redirect URI to the Meta App. Use one Business Manager to own the WhatsApp Business Account, and always perform OAuth with a Business Admin account to prevent permission mismatches.
Build it with us. The community is free and the build track teaches this kind of automation week by week: see pricing or join the community.