WhatsApp Trigger blocked by stale webhook subscription — same App ID

Questions
1

Hi, I have a WhatsApp Dispatcher workflow with a WhatsApp Trigger node. I’m getting this error when activating:
“The WhatsApp App ID 976855898413634 already has a webhook subscription. Delete it or use another App before executing the trigger.”
I’ve already:
Deleted and recreated the WhatsApp OAuth credential
Deleted the Meta webhook subscription via Graph API Explorer (returned success: true)
Deactivated and reactivated the workflow multiple times
The stale registration appears to be in n8n’s internal database. Can someone from the n8n team clear the subscription for App ID 976855898413634?
n8n Cloud instance: marketingeddine.app.n8n.cloud

Describe the problem/error/question

What is the error message (if any)?

Please share your workflow

(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.)

Share the output returned by the last node

Information on your n8n setup

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
2

Hi @Eddine_Belaid, before assuming it’s stuck in n8n’s DB, this error usually survives a Meta cleanup for one of two reasons:

  1. The WABA-level subscription is separate from the app one. Deleting /{app-id}/subscriptions doesn’t clear the WhatsApp Business Account’s subscribed_apps. Check GET /{waba-id}/subscribed_apps and delete there too.
  2. Another workflow in this instance (even inactive, or a duplicate) with a WhatsApp Trigger on the same App ID will keep re-registering it.

Did your Graph API delete cover the WABA subscribed_apps, and is this the only workflow using that trigger?

3

Hi @Eddine_Belaid

If you are in a production rush and the internal state is truly stuck, the fastest resolution is to create a new Meta App:

  1. Create a new App in the Meta Developer Portal.
  2. Generate a new App ID and App Secret.
  3. Update your n8n credentials with the new ID.
  4. This bypasses the “stale” registration entirely because you are using a fresh App ID.
4

I rather user Webhook node and put it in app’s webhook, it works faar better than WhatsApp triger node

5

Welcome @Eddine_Belaid!

Deleting at the app level via Graph API is the right move, but the error persists because n8n also stores its own internal webhook registration in the database - and that record survives credential deletion/recreation. The fastest fix: fully stop the workflow, then delete the entire WhatsApp Trigger node, save the workflow, then re-add it fresh - this forces n8n to clear its cached registration and register cleanly on the next activation. Also confirm you have no other workflows (active or inactive) sharing this same App ID, as even a deactivated duplicate will silently hold the subscription lock.

6

You haven’t yet verified whether the WhatsApp Business Account still has an active entry under /{waba-id}/subscribed_apps,

Regarding the workflow, as far as I can tell this is the only WhatsApp Trigger workflow currently in use, but I’ll do a full audit for inactive workflows, duplicates, or any leftover triggers that might be re-registering the webhook automatically.

7

I would stop recreating credentials for a minute and trace which system still owns the webhook subscription. The useful path is: confirm Meta app webhook subscriptions, confirm the exact callback URL n8n is trying to register, then check whether the old trigger record is stuck inside n8n Cloud/internal state.