https://discord.gg/botpress logo
WhatsApp API - Verified Account with Manual Config...
# 🤝help
b
Hi everyone, I am stuck with my WhatsApp Business API integration and really need your help to unblock this. I am currently building on the Botpress Free Tier / Trial cloud account. I have followed all the troubleshooting steps, but the bot is still not processing messages. My Objective: I aim to deploy a large, advanced workflow designed for full business automation (administrative tracking, and logistics). I need Botpress to successfully recognize inbound WhatsApp messages and trigger the initial conversational flow nodes properly. The Current Issue Symptoms: Inbound messages sent from my personal WhatsApp do not trigger any activity in the Botpress logs. The bot does not respond, and after setting the Log Level to Debug, I don’t see any Received text message or Sending message errors (no 403, 401, or 400 codes). The logs only show the manual registration event when I update it. What We Have Already Attempted (Solutions Tested) To save time, here is everything we have already verified and configured based on prior troubleshooting: Meta Account Status: My business is fully verified in Meta Business Manager. The phone number status is active and verified as well (not pending). A valid payment method is configured in the billing hub. Clean Integration Reset: We completely uninstalled the WhatsApp integration in Botpress and cleared the Facebook OAuth permissions to remove any residual WABA account cache. Switch to Manual Configuration: I switched from OAuth to Manual Configuration inside Botpress to enforce the correct IDs. Credentials Check: Hand-copied the exact Phone Number ID and WhatsApp Business Account ID (WABA ID) from the Meta developer dashboard. Webhook & Token Setup: I have manually configured the Webhook URL and Verify Token inside Meta Developers multiple times. I also double-checked that the app is actively subscribed to the messages field in the Webhook fields. https://cdn.discordapp.com/attachments/1507111123218993242/1507111123529240758/image.png?ex=6a10b61c&is=6a0f649c&hm=5e6431c1379593ee674728bc457f0b0ee9ae0b048eb30ce1da2936f2e8c6c6a0& https://cdn.discordapp.com/attachments/1507111123218993242/1507111124280147998/image.png?ex=6a10b61c&is=6a0f649c&hm=0c88cd999fe7a45e46578f85dd73e30e4e24fa2a1b845dcf8c278783285cbac1& https://cdn.discordapp.com/attachments/1507111123218993242/1507111124598919238/image.png?ex=6a10b61c&is=6a0f649c&hm=3f573974ddfdef92db4641d39e1198066c227f392c7d6a56f5f5ae8a6e1876a1&
l
Can you drop your wroskpace ID? @busy-refrigerator-83645
b
wkspace_01JZVC5Z1V49D17B6GPNPEEADZ
l
Thank you 🙂 Will get back!
Root cause: Meta sandbox restriction The Whats app integration is configured with configurationType: manual, meaning the user set up their own Meta App and phone number. In this mode, Meta's WhatsApp Cloud API runs in development mode by default, which enforces a strict restriction: ▎ Only phone numbers explicitly added as test numbers in the Meta Developer Portal can send messages to the bot. Messages from any other number — including your personal WhatsApp — are silently accepted ▎ by the webhook (hence the 200s) but never delivered for processing. Solution: 1. Go to Meta for Developers → Your App → WhatsApp → API Setup 2. Under "To" field / Test numbers, click "Add phone number" 3. Add the personal WhatsApp number they're testing from and complete the verification code 4. Try sending again — the bot should now respond
b
I managed to trigger a manual test call directly from the Meta Developer Console using the exact credentials configured in my Botpress manual integration. But Meta just threw an error https://cdn.discordapp.com/attachments/1507111123218993242/1507125705765290096/image.png?ex=6a10c3b1&is=6a0f7231&hm=34933cc86742456c021270f3afe7e0d79fa3c56d38bfef05030c86c0768af394&
Also yesterday I managed to clear that previous Meta dashboard error. Here is the exact current state of the integration: API Outbound Works: I executed a manual POST request via the Graph API Explorer using the generated System User Token and payload. As you can see in the attached screenshot, the official "Hello World" template successfully reached my personal device. Inbound Webhook Fails: Immediately after receiving the template, I replied with "Hola" multiple times. However, the bot remains completely silent, and zero inbound activity is being captured by the Botpress Debug logs. This isolates the issue completely: Meta is successfully sending messages out using our credentials, but the webhook handshake or event routing on Botpress's end is not delivering the inbound messages back to the workflow. https://cdn.discordapp.com/attachments/1507111123218993242/1507127914821451878/632429a4-8ea7-4fa2-8ce9-af97f6757eb3.png?ex=6a10c5bf&is=6a0f743f&hm=6df4f1d2cac637216e7fc277efbff2e519741579e71f20ac789c130a55dcf754&
l
Root cause: The access token is invalid for phone number ID 968462799680297. This is a token/phone number mismatch. The System User token configured in the Botpress WhatsApp integration either: - Expired (user-generated tokens expire in ~60 days; only System User permanent tokens don't) - Belongs to a different Meta App or WABA than the one that owns phone number 968462799680297 - Lacks the required permissions (whatsapp_business_messaging + whatsapp_business_management) 1. Go to Meta Business Manager → Settings → System Users 2. Select the system user associated with the WhatsApp app, click Generate New Token 3. Enable permissions: whatsapp_business_messaging and whatsapp_business_management 4. Make sure that system user has been granted access to the WhatsApp Business Account that owns the phone number (Assets tab in Business Manager) 5. Paste the new permanent token back into Botpress Studio → Integrations → WhatsApp and save/re-register The phone number ID itself (968462799680297) is fine — Meta is sending events for it. The token is the only thing broken.
Lets try this now 😄
b
I have just generated a brand-new permanent System User Access Token directly from Meta Business Suite to rule out any expiration or caching issues. As you can see in the attached screenshot, the token was generated under the correct system user, with full asset permissions over the WABA, and explicitly enforcing the three required scopes: whatsapp_business_messaging whatsapp_business_management business_management I have successfully updated, saved, and re-published the bot in Botpress Studio with this exact new token. However, inbound messages sent to the phone number ID 968462799680297 are still failing to trigger any activity or logs in Botpress. Since the credentials match perfectly and the scopes are fully active, could you please check on your side if this specific workspace endpoint (wkspace_01JZVC5Z1V49D17B6GPNPEEADZ) is experiencing a backend synchronization delay or if the manual configuration hook is stuck in your database routing? https://cdn.discordapp.com/attachments/1507111123218993242/1507142939506114650/f74a2dc0-c89d-4d7a-b278-fb7f240db317.png?ex=6a10d3be&is=6a0f823e&hm=6139e24982444ac1d9ccbf967982c9cfd688b7f33dcb95b750621e928b2338a7&
"Hi Ross, I am having trouble with my WhatsApp integration. I have configured the webhook and the integration It's published in my dashboard, but I am unable to receive or send messages. When attempting to interact with the bot, I receive the following Graph API error: 'Unsupported post request. Object with ID '968462799680297' does not exist, cannot be loaded due to missing permissions, or does not support this operation.' I have already performed the following steps: Verified that the System User has full control over the WhatsApp Business account. Generated a new Permanent Access Token with whatsapp_business_management and whatsapp_business_messaging scopes. Updated the token in the Botpress integration settings and published the bot. Confirmed my WhatsApp number ID is 968462799680297.
l
taking another look now
Potential fix Step 1 — Fix the Phone Number ID: 1. Go to https://business.facebook.com → your Business Portfolio → WhatsApp Manager → Phone Numbers 2. Click on the phone number you're using 3. Copy the numeric ID shown (looks like 1234567890123456) — this is NOT the +57... number itself 4. Paste this into the Phone Number ID field in the Botpress WhatsApp integration settings Step 2 — Add the App Secret (clientSecret): 1. Go to https://developers.facebook.com → your Meta App → Settings → Basic 2. Copy the App Secret 3. Paste it into the Client Secret field in the Botpress WhatsApp integration settings Step 3 — Save and republish the bot.
b
"Hi! I already followed your steps: I verified and updated the Phone Number ID (using the 15-digit numeric ID from Meta, not the phone number string) and the App Secret into the Client Secret field. I saved and republished the bot, but it’s still not responding to incoming messages. I suspect the issue might be on Meta's side or with the Webhook handshake, because when I check my WhatsApp Manager under the Business Portfolio, my production number (+57...) doesn't appear listed there yet (only the +1 555... test number shows up), even though the number is fully visible and has an ID inside Meta for Developers (Cloud API).
11 Views