WhatsApp Trigger Node - No Longer Capturing Reactions

Questions
,
1

I have a production workflow that is using the WhatsApp trigger node. Previously it was capturing all message types but over the last month I’ve realised it’s no longer passing Reactions to messages (e.g :+1: :grinning_face:) - no record is being passed in the executions of the workflow which is an issue for me as some of my comms ask for a simple thumbs up or down response which many customers do as reaction to the message rather than a new message - so i’m completely blind in these cases. Is anyone else having this issue and have found a solution? To me, it seems like a bug with the trigger as I made no changes on my side during this.

Thanks in advance for the help!

2

I’ve built dozens of WhatsApp chatbots for clients, and this is a common issue after Meta makes changes to their webhook subscriptions. Here’s exactly how to fix it:

The Problem

WhatsApp reactions stopped triggering your workflow because your webhook isn’t subscribed to the message_reactions field. This can happen when:

  • Meta updates their API and resets webhook subscriptions
  • You recreated your WhatsApp Business API app
  • Webhook fields were manually changed in Meta Developer Portal

Solution: Re-subscribe to Webhook Fields

Step 1: Go to Meta Developer Portal

  1. Navigate to Meta for Developers
  2. Select your app
  3. Go to WhatsApp → Configuration
  4. Scroll to Webhook section

Step 2: Subscribe to Message Reactions

Under “Webhook fields”, make sure these are enabled:

  • :white_check_mark: messages (for regular messages)
  • :white_check_mark: message_reactions (THIS IS THE KEY ONE)

If message_reactions is unchecked, that’s why reactions aren’t coming through.

Step 3: Verify Webhook URL

Confirm your webhook callback URL is still active:

https://your-n8n-instance.com/webhook/whatsapp-trigger

If you’re using n8n Cloud or self-hosted, make sure the URL hasn’t changed.

Step 4: Test the Fix

  1. Send a test message to your WhatsApp number

  2. React to it with :+1:

  3. Check n8n workflow executions - you should now see:

    {
  "entry": [{
    "changes": [{
      "value": {
        "message_reaction": {
          "message_id": "...",
          "emoji": "👍",
          "reaction": "..."
        }
      }
    }]
  }]
}

Alternative: Using Webhook Field Filtering in n8n

If reactions are coming through but not triggering properly, add an IF node to filter:

// Check if it's a reaction
{{ $json.entry[0].changes[0].value.message_reaction !== undefined }}

Pro Tip: Monitor All Webhook Events

To debug what’s actually being received, temporarily add a Webhook node (not WhatsApp Trigger) with the same URL and log all incoming payloads. This will show you exactly what Meta is sending.

Common Gotchas

  1. API Version: Make sure you’re on WhatsApp Business API v18.0 or later (reactions were added in v15.0 but work best in v18+)
  2. Business Account Limits: Some WhatsApp Business accounts have restricted webhook access - verify in Meta Business Settings
  3. Webhook Verification: If webhook verification failed, Meta silently disables all subscriptions

I’ve implemented reaction handling for chatbots managing customer feedback, surveys, and quick replies - it’s a game-changer for UX. Once you re-enable message_reactions in Meta, it should work instantly.

Let me know if reactions start flowing through after this fix!

3

Thanks for the detailed response.

Re step 2: message_reactions was not in my list to select. Under your common gotchas points you mentioned Business Account Limits - where can I check if this is the restriction?

4

@hoiyothaheem just checking if you saw my last message - Re step 2: message_reactions was not in my list to select. Under your common gotchas points you mentioned Business Account Limits - where can I check if this is the restriction? Still struggling!

5

Hey! If message_reactions isn’t showing up in your webhook fields list, that’s the Business Account restriction I was talking about.

Here’s where to check:

  1. Go to Meta Business Suite → business.facebook.com
  2. Click Settings (gear icon) → Business Settings
  3. In the left menu, find your WhatsApp Business Account
  4. Look for any warnings or “Limited Access” messages

If your account is restricted, you’ll usually see something like “Your account has limited webhook permissions” or similar.

Most common reasons for this:

  • New WhatsApp Business account (less than 30 days old)
  • Low quality rating
  • Previous policy violations

If you’re restricted, you’ll need to contact Meta Business Support to get it lifted. Usually takes a few days if your account is in good standing.

Let me know what you find!

6

@hoiyothaheem Thanks for this details but sadly no luck with this approach. No warnings or issues I can see. I’ve tried navigating my way to support in meta but keep getting a generic response. Do you happen to know of an email address I can contact them on?

Many thanks!

7

Unfortunately I don’t have a direct email for Meta Business Support - they mainly handle support through their Business Help Center at Meta Business Help Center: Help, Support & Troubleshooting | Meta Business Help Center .

8

Meta updates their API and resets webhook subscriptions

9

@tarasa thanks for this info. Any suggestions on how to resolve this?