WhatsApp template health and channel-disconnected triggers

React automatically when Meta approves, rejects or pauses a template, your WABA quality drops, or a channel goes offline.

Jun 26, 2026

Watch this step in the video · WhatsApp templates and the 24-hour window

What platform-health triggers are

Meta makes decisions about your templates and your number without warning you in advance: it approves a template, rejects it, pauses it for low engagement, or downgrades your WABA quality. If you find out late, your broadcasts start failing. Omnifox listens to those events over webhook and turns them into workflow triggers so your team can react in seconds instead of the next day.

These triggers live under the System category in the editor and are perfect for internal alerts (post to a Team channel, create a task) and for defensive actions (pause broadcasts when quality drops to RED).

Available triggers

  • Template approved (whatsapp.template_approved): Meta validated your template and it can now be sent. Handy to tell marketing the campaign is ready.
  • Template rejected (whatsapp.template_rejected): Meta rejected the template. Exposes $template.rejection_reason so you know why.
  • Template paused (whatsapp.template_paused): because of low quality or too many complaints, Meta stopped sends of that template. Exposes $template.paused_reason.
  • WABA quality changed (whatsapp.quality_rating_changed): your number's quality moved between GREEN / YELLOW / RED. Critical for damage control.
  • Channel disconnected (channel.disconnected): a channel of any type (WhatsApp, Instagram, Messenger and the rest) lost its session or its token expired and stopped sending/receiving. For the same channel it doesn't repeat within 1 hour. See Trigger: Channel Disconnected.

Requirements

  • Available on all plans (from Lite), with a monthly quota of workflow runs based on your plan.
  • At least one WhatsApp channel connected through Embedded Signup.

Steps to build the workflow

  1. Go to Settings → Workflows and click Create workflow.
  2. In the left palette, open the System category and drag the trigger you need (for example Template rejected).
  3. In the trigger inspector, use the Specific channel filter if you only care about one number, or leave it empty for all. On Template approved/rejected you can also filter by Template category (AUTHENTICATION / MARKETING / UTILITY).
  4. Connect an action. The most common ones: Post to Team to notify the team, Create task for follow-up, or Send email.
  5. Insert trigger variables into the message with the Insert variable button: $template.name, $template.rejection_reason, $channel.name, and so on.
  6. Flip the top switch to activate and Save.

Recommended defensive recipe (RED quality)

With WABA quality changed, set the New quality = RED filter and connect an action that pauses your broadcasts or pings the owner immediately. That stops you from burning the number's reputation any further.

How to verify

Because these are platform events, you can't trigger them on demand. Use the editor's Test button: these triggers are synthetic and ask you to fill in test data (template ID, channel, reason) so you can simulate the firing and confirm your actions run. After a real event, check the workflow's run history.

If it doesn't work

  • Nothing fires: make sure the workflow is active (green switch) and the Specific channel filter matches the affected channel.
  • I only get some events: Meta does not resend historical events; you only receive the ones that happen while the webhook is connected.
  • Rejected template with no reason: Meta sometimes sends no reason, so $template.rejection_reason may arrive empty.

Tips

  • Combine Template paused + WABA quality changed in separate workflows for a complete health dashboard for the number.
  • If you have several channels, create one workflow per channel with its filter so each alert is routed to the right team.

Related articles

Was this helpful?

Related articles

Message us on WhatsApp