WhatsApp template message accepted by Meta API but not delivered when using a production number

Hi everyone,

I’m having an issue with WhatsApp Cloud API when moving from a test number to a production number, and I’m not sure if this is an n8n configuration problem or a Meta App limitation.

Context

  • I have an n8n workflow that sends a WhatsApp template message using the WhatsApp node (Message → Send Template).

  • Initially, everything worked correctly when my Meta App was configured with the Test Number.

  • The workflow successfully sent template messages to the phone number associated with the test setup.

Problem

After configuring the Meta App with a real (production) phone number:

  • The n8n node does not fail.

  • The execution output shows:

    • message_status: "accepted"

    • A valid wamid returned by the API (see screenshot below).

  • However:

    • No message is delivered to WhatsApp.

    • In the Meta Business Manager / WhatsApp Manager, no outgoing message appears for that phone number.

    • The Meta App is still in “In Development” mode.

Has anyone encountered this issue before or knows what might be causing it?

Hi @Aitor_PM Welcome!
just check that your Meta App is subscribed to your WABA and switch your message template category from MARKETING to UTILITY in Meta Business Suite, as production numbers block initial marketing messages

1 Like

Hi @Aitor_PM

Welcome to the n8n community :tada: !

The message_status: "accepted" status only means the WhatsApp API accepted the request — it doesn’t mean the message was actually delivered. When you’re using a production phone number while your Meta App is still in “In Development” mode, WhatsApp accepts the request and returns a wamid, but it silently blocks delivery. The message won’t show up in WhatsApp Manager and won’t reach the recipient.

Solution

To make message delivery work in production:

  1. Switch the Meta App to “Live Mode”
  2. Make sure the production phone number is verified and active in WhatsApp Manager
  3. Verify that the Phone Number ID used in n8n belongs to the production number (not the test number)
  4. Ensure the template is Approved under the same WABA

After this, the same n8n workflow should start delivering messages normally
fingers crossed :crossed_fingers:

1 Like

Thank you very much.

I have switched the app to Live mode.

In the image, the phone number status appears as Connected, but I also see a message saying “Under Review.” I am not sure whether this review applies only to the display name or also to the phone number itself.

The Phone Number ID configured in n8n is correct.

I tested both my own template and a new one Service template. Both templates belong to the same WABA. I can select them in the WhatsApp node in n8n.

So far, the result is the same in all cases.