Skip to main content
Question

WhatsApp Business trigger not firing despite successful connection in Zapier

  • June 12, 2026
  • 3 replies
  • 40 views

Hi,

I’m trying to connect WhatsApp Business to Zapier using the official WhatsApp Business app on Zapier.

Goal:
Trigger a Zap when a new WhatsApp message is received, then send the message data to a webhook.

Current Zap setup:
Trigger:
WhatsApp Business -> New Message Received

Action:
Webhooks by Zapier -> POST

The POST action works correctly when I run a Zapier test. The test payload is successfully sent to webhook.site.

Problem:
Real incoming WhatsApp messages do not trigger the Zap at all.

What works:
- Zapier App Connection status: Connected
- Test connection in Zapier: successful
- Test run in Zapier: successful
- Webhooks by Zapier POST test: successful
- webhook.site receives Zapier test payload correctly
- Zap is published and turned on
- Zap History only shows test runs, no real runs from incoming WhatsApp messages

What does not work:
- When I send a real WhatsApp message from another phone number to the connected WhatsApp Business number, no Zap run is created.
- Zap History remains empty for real incoming messages.
- webhook.site receives nothing for real incoming messages.

Meta / WhatsApp Business state:
Business portfolio: xxxxx
WABA ID: xxxxxx
WhatsApp Business Account name: xxxxx
Phone number: xxxxx
Phone Number ID: xxxx
Partner assigned in Meta: Zapier
Partner access: full control

Important detail:
In Meta WhatsApp Manager, the phone number status is still:
Pending / Oczekuje

The display name status is:
xxxxxx
In review / W trakcie sprawdzania

Meta shows this message:
“To register the phone number, contact your partner or use the registration API.”

Question:
Does Zapier automatically complete the WhatsApp phone number registration for numbers added through the Zapier onboarding flow?

If yes, why is the phone number still Pending in Meta and why is the New Message Received trigger not firing?

If no, what exact step is required to complete the phone number registration so that real incoming WhatsApp messages trigger the Zap?

I have already confirmed that:
- The Zap is ON.
- The selected WhatsApp Business connection is active.
- The trigger configuration has Message type = Text.
- From phone number is blank, so it should accept messages from all customers.
- Only replies = False.
- Real messages were sent after the Zap was published.
- The webhook action works correctly during manual tests.

It looks like Zapier is connected to the WABA, but the WhatsApp phone number is not fully registered/active for real messaging events.

Can someone confirm whether the Pending status in Meta is expected during review, or whether this indicates that Zapier did not complete the phone number registration?

3 replies

Forum|alt.badge.img+4
  • Zapier Solution Partner
  • June 12, 2026

Troy Tessalone
Zapier Orchestrator & Solution Partner
Forum|alt.badge.img+14
  • Zapier Orchestrator & Solution Partner
  • June 12, 2026

Hi ​@Konrad F 

Help links for using WhatApp Business Manager in Zaps: https://zapier.com/apps/whatsapp-business/integrations#help


Forum|alt.badge.img

Hi,

I’m trying to connect WhatsApp Business to Zapier using the official WhatsApp Business app on Zapier.

Goal:
Trigger a Zap when a new WhatsApp message is received, then send the message data to a webhook.

Current Zap setup:
Trigger:
WhatsApp Business -> New Message Received

Action:
Webhooks by Zapier -> POST

The POST action works correctly when I run a Zapier test. The test payload is successfully sent to webhook.site.

Problem:
Real incoming WhatsApp messages do not trigger the Zap at all.

What works:
- Zapier App Connection status: Connected
- Test connection in Zapier: successful
- Test run in Zapier: successful
- Webhooks by Zapier POST test: successful
- webhook.site receives Zapier test payload correctly
- Zap is published and turned on
- Zap History only shows test runs, no real runs from incoming WhatsApp messages

What does not work:
- When I send a real WhatsApp message from another phone number to the connected WhatsApp Business number, no Zap run is created.
- Zap History remains empty for real incoming messages.
- webhook.site receives nothing for real incoming messages.

Meta / WhatsApp Business state:
Business portfolio: xxxxx
WABA ID: xxxxxx
WhatsApp Business Account name: xxxxx
Phone number: xxxxx
Phone Number ID: xxxx
Partner assigned in Meta: Zapier
Partner access: full control

Important detail:
In Meta WhatsApp Manager, the phone number status is still:
Pending / Oczekuje

The display name status is:
xxxxxx
In review / W trakcie sprawdzania

Meta shows this message:
“To register the phone number, contact your partner or use the registration API.”

Question:
Does Zapier automatically complete the WhatsApp phone number registration for numbers added through the Zapier onboarding flow?

If yes, why is the phone number still Pending in Meta and why is the New Message Received trigger not firing?

If no, what exact step is required to complete the phone number registration so that real incoming WhatsApp messages trigger the Zap?

I have already confirmed that:
- The Zap is ON.
- The selected WhatsApp Business connection is active.
- The trigger configuration has Message type = Text.
- From phone number is blank, so it should accept messages from all customers.
- Only replies = False.
- Real messages were sent after the Zap was published.
- The webhook action works correctly during manual tests.

It looks like Zapier is connected to the WABA, but the WhatsApp phone number is not fully registered/active for real messaging events.

Can someone confirm whether the Pending status in Meta is expected during review, or whether this indicates that Zapier did not complete the phone number registration?



Hi ​@Konrad F,  Has this been resolved yet?

If Not, The detail that stands out to me is the phone number still showing as **Pending** in Meta. Since your test actions are working but no real events are reaching Zapier, I'd be looking closely at the WhatsApp number registration/activation status rather than the Zap itself.

That feels like the most likely bottleneck based on everything you've described.

Happy to take a look if you'd like:

--link removed by moderator--

This post has been edited by a moderator to remove self-promotional calendar booking link as per our Community Code of Conduct.