I'm trying to integrate WhatsApp Cloud API into my existing Make.com AI Lead Management System

Questions
,
1

:bullseye: What is your goal?

My goal is to add a WhatsApp follow-up message to Scenario 3. When a lead’s follow-up date is due, the scenario should send the Gmail follow-up first, then send a WhatsApp message to the phone number entered by the customer in Google Forms, and finally update the Google Sheet’s “Last Follow-up Sent” field.

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

I’m currently stuck at Meta for Developers → WhatsApp → API Setup (Step 1: Try it out).

  • My Phone Number ID and WhatsApp Business Account ID are populated.
  • I’ve generated a new access token.
  • I’ve entered my own WhatsApp number as the recipient and selected the “hello_world” template.
  • However, the test phone number field appears disabled, and I cannot select or interact with it. The test message is not being sent.

I’ve tried generating a new token, but the issue remains.

Could someone please explain why the test phone number field might be disabled and how I can successfully send the initial test message?

Also, once the test message works, what is the recommended way to connect WhatsApp Cloud API to my existing Make.com follow-up scenario?

Thanks!

3

The test phone number field in the Meta developer dashboard locks up if you haven’t explicitly added your personal mobile number to the allowed recipient list or if your temporary access token has expired. Once verified, configure make.com using a standard ‘Make an API Call’ module targeting the WhatsApp Cloud API endpoint with a JSON payload containing your template parameters. Let me know what specific error response code Meta returns in your Make execution logs and I can provide the exact JSON payload structure right here.

4

Thanks for your response. My personal WhatsApp number is already added as an allowed recipient, and I have regenerated the access token. The issue still persists: the test phone number field is not clickable in Meta’s API Setup.

I haven’t been able to send the test message yet, so I don’t have a Make.com execution error code. What should I check next to resolve the disabled test phone number field?

5

Great, since the token is fresh and your number is on the allowed list, the locked field almost always points to one of three things:
1. The phone number hasn’t completed OTP verification inside Meta’s Business Platform (separate from just adding it to the recipient list). Go to: Meta Business Suite - WhatsApp Accounts - Manage -Phone Numbers — your number should show status “Connected”. If it shows “Pending” or “Not Registered”, click it and complete the 6-digit SMS/call verification Meta sends. That’s what unlocks the test field.
2. App mode mismatch. In your Meta App Dashboard, confirm the app is in Development mode (not Live). In Live mode, the test phone panel behaves differently and the field can appear frozen. Switch: App Settings - Basic - App Mode - Development.
3. Missing permission scope. Open your app’s Permissions panel and verify whatsapp_business_messaging is approved. Without it, the API Setup UI partially disables.
Try step 1 first — it resolves this 90% of the time. What does the status column show next to your phone number in the Business Platform phone list?

6

Adding to the Meta tips, here’s the Make side. You don’t need a raw API call. Make’s WhatsApp Business Cloud app has a send-message module that can send an approved template. Put it right after your Gmail step and map the phone number from the Sheet (full international format, digits only, no + or spaces), then update ‘Last Follow-up Sent’. Because these follow-ups go out days later, outside WhatsApp’s 24-hour reply window, they have to use an approved template, not free text. Submit one with a variable for the lead’s name early, since approval can take a while. Also add an error handler on the WhatsApp module so one bad number doesn’t stop the whole run. If you want a hand wiring it in, send me a private message here.

7

A greyed-out test number field in API Setup usually isn’t an error. When your app only has Meta’s one test number, there’s nothing to choose, so the dropdown is disabled. What matters is whether the send itself works:

  • In the “To” list, the recipient has to be confirmed with the code Meta sends to that phone. Just adding the number isn’t enough.
  • Copy the cURL request shown on that page and run it (or use a Make HTTP module). The response gives you the real error code.

For Scenario 3 itself:

  1. Use the WhatsApp Business Cloud → Send a Template Message module. Follow-ups usually happen more than 24 hours after the lead’s last message, so free-text messages will be rejected. Create a utility template with variables such as {{1}} = first name.
  2. Normalise the Google Forms phone number to international format (country code, digits only) with a formula before the module.
  3. Only update “Last Follow-up Sent” after the module returns a message ID, and add an error-handler route that writes the failure to the sheet. That way a failed WhatsApp send doesn’t look like a successful follow-up.
  4. Add a “OK to contact me on WhatsApp” checkbox to the form and filter on it. Meta restricts numbers that message people who didn’t opt in.