Trigger: WABA Quality Rating Changed

The WABA Quality Rating Changed trigger fires when Meta updates your WhatsApp Business Account's quality rating (GREEN, YELLOW, or RED) for a connected channel.

When to use it

This is key to protecting your number: if quality drops to RED, Meta can drastically cut your messaging limit. This trigger lets you react instantly instead of finding out days later by checking Meta Business Manager.

Configuration

In the Trigger node pick "WABA Quality Rating Changed" and you can filter by:

• Specific channel
• New rating (GREEN / YELLOW / RED) — ⚠️ today this filter does not actually restrict the trigger: the workflow runs on any quality change (including an improvement to GREEN), not only when it drops to the value you picked. Don't rely on it as your only control.

Available variables

• $channel.id / $channel.name
• $waba.previous_rating
• $waba.new_rating
• $waba.phone_number
• $waba.current_limit (current messaging limit)

Example

Workflow "Critical quality alert": Trigger = WABA Quality Rating Changed (leave "New rating" empty, since it doesn't filter today). Add a Condition node comparing {{$waba.new_rating}} == RED. If true → Action 1: notify the "Alerts" Space in Team with Channel {{$channel.name}} dropped to RED quality. Action 2: pause outbound broadcast campaigns (via another automation or manual notice) until the issue is resolved.

Tips

• Don't leave this trigger unused if you send campaigns or bulk notifications: an uncontrolled drop to RED can get your number restricted.
• Pair it with manual reviews of your template content and sending volume, which are usually the root cause of quality drops.
• Since the "New rating" filter doesn't discard anything today, always add a Condition node right after the trigger to keep only the value you care about (e.g. RED).

Troubleshooting

• If you don't see the expected trigger fire, confirm the WhatsApp channel is correctly connected via Embedded Signup and that Meta is actually reporting quality changes for that number (some updates take time to propagate).
• If the workflow runs for ratings you didn't pick in "New rating" (e.g. it also fires on GREEN when you only expected RED): this is a known limitation, that filter doesn't discard anything yet. Filter the value with a Condition node after the trigger instead.