Urgent N8N WhatsApp trigger not working(trigger) after inputting proper AppID and App Secret

[dk-22]

Describe the problem/error/question

After inputting the proper Client ID and Client Secret where i get these codes from Meta, a simple whatsApp message does not trigger the whatsapp trigger node where the trigger node stays running/listening until timeout.

What is the error message (if any)?

Please share your workflow/screenshots/recording

After sending a simple message from whatsapp the trigger node stays on listening

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)
⚠️ WARNING ⚠️ If you have sensitive data in your workflow (like API keys), please remove it before sharing.

{
"nodes": [
{
"parameters": {
"updates": [
"messages"
],
"options": {}
},
"type": "n8n-nodes-base.whatsAppTrigger",
"typeVersion": 1,
"position": [
-496,
704
],
"id": "bf3e6c67-a49e-496e-97cf-4317d2062db7",
"name": "WhatsApp Trigger1",
"webhookId": "169fcfd1-95fe-48bc-82f2-8dc8316b1450",
"credentials": {
"whatsAppTriggerApi": {
"id": "noGT4pOVTykuC1J0",
"name": "WhatsApp OAuth account"
}
}
}
],
"connections": {},
"pinData": {},
"meta": {
"templateCredsSetupCompleted": true,
"instanceId": "01f7d6f5bec76988ada96c48083dd4ac005a64f83a2d5239af9d97ddcd7ee721"
}
}

Share the output returned by the last node

Debug info

core

• n8nVersion: 1.122.4
• platform: docker (cloud)
• nodeJsVersion: 22.21.0
• nodeEnv: non-prod
• executionMode: regular
• concurrency: 5
• license: enterprise (sandbox)

client

• userAgent: mozilla/5.0 (macintosh; intel mac os x 10_15_7) applewebkit/537.36 (khtml, like gecko) chrome/143.0.0.0 safari/537.36 edg/143.0.0.0
• isTouchDevice: false

Generated at: 2026-01-05T09:32:15.812Z}

[n8n-assistant]

Hey @dk-22,

Thank you for reaching out! We’ve received your issue and are looking into it. To help us track this internally, we’ve created a Linear ticket with the reference: "GHC-6152".

We’ll keep you updated as we make progress, but if you have any additional details or context to share, feel free to add them here - it’s always helpful!

Thanks for your patience and for bringing this to our attention.

---

For INTERNAL use only: GHC-6152

[krisn0x]

Hi @dk-22 ,

Thank you for reaching out! It looks like this issue might be more of a support request rather than a bug report. For general support, troubleshooting, or questions, we recommend raising your request on our community support forum.

The forum is a great place to connect with both our team and other community members who can help out. You might even find answers to similar questions there!

For issues related to n8n cloud billing or instances going offline please email help@n8n.io as we are not able to access your cloud account or workflows from these issues.

We’ll go ahead and close this issue to keep the tracker focused on bug reports. Feel free to join the conversation on the forum, and let us know if you have any further concerns or questions.

Thanks again for being part of the n8n community!

Best regards,
n8n Team