Ghost Webhooks

Questions
1

Hi everyone,
I’m trying to build a workflow with the WhatsApp Trigger in n8n, but I keep running into this error:
The WhatsApp App ID XXXXX already has a webhook subscription. Delete it or use another App before executing the trigger. Due to WhatsApp API limitations, you can have just one trigger per App.
I already checked the Meta Developers dashboard under WhatsApp → Configuration → Webhooks, and the Callback URL field is empty, so it looks like there’s no webhook configured on Meta’s side. I also deleted my old Zapier integration that was using the same WhatsApp App ID, but the error still shows up in n8n.
Currently I only have one workflow with a WhatsApp Trigger in my n8n instance, so there shouldn’t be any duplicates.
Does anyone know how to force n8n to “reset” or clear out this ghost webhook subscription so that the WhatsApp Trigger can register properly?
Thanks in advance!

Problem running workflow

The WhatsApp App ID 1330951205478242 already has a webhook subscription. Delete it or use another App before executing the trigger. Due to WhatsApp API limitations, you can have just one trigger per App.

It is a very basic workflow

2 Likes
2

Hey, I would recommend creating a new app if you don’t mind. If not, you can use the Meta Graph API:

Check if you have active webhooks:

curl -X GET \
  "https://graph.facebook.com/v17.0/YOUR_APP_ID/subscriptions?access_token=APP_ACCESS_TOKEN"

Delete them:

curl -X DELETE \
  "https://graph.facebook.com/v17.0/YOUR_APP_ID/subscriptions?access_token=APP_ACCESS_TOKEN"

Then stop/start the workflow. Let me know how it goes :slight_smile:

3

Thanks. I created the new app but still could not get ahead.

How specificaly do you use the meta graph api? -sorry I am no tech-

4

Hmm, do you get the same error with the new app? Feel free to share what you did exactly.

For the commands above, you need to replace the capitalized sections and copy paste the entire thing from each block in your terminal (shell). This will make a request to META and will print some result which will tell you more.

5

So, I went and exceuted the CMD prompt and typed what you suggested. But still recieving the same error message… thanks for your support

ice_screenshot_20250919-064550
ice_screenshot_20250919-0645501976×674 102 KB

6

Hey, sorry for the delay, the command didn’t find any webhooks. Can you please try this:

  1. Create a new whatsapp app, don’t use it yet.
  2. Duplicate your workflow
  3. Connect the new app before you run the workflow for the first time
  4. Double check if all’s good and run it

Let me know how it goes :slight_smile:

1 Like
7

well this worked but…why did it happened? Won’t that be a big time issue once I go live? I just began testing your services, hoping to scale it soon and this makes me a bit doubtful.

8

Hey, if you ran my commands, this all has to do with Meta, not n8n. Also, please note I’m not from the team, if you see a user with n8n Team next to their name - they are from the team.

Edit: I am now on the team :smiley:

4 Likes
9

Got it, I thought you were devs team. Thanks.

1 Like
10

I have the same problem :pensive_face: why does n8n insist there is another whatsapp webhook even I deleted all workflows and meta apps ?

11

same Problem here

12

I’ve been running into this same issue, ran the commands with an empty array coming back as the response but still ran the delete just in case. Created multiple new apps and all ran into the same issue. The webhook subscription only appears after I turn the workflow to ‘active’ and try to execute it, but if I execute without activating it, the OnMessage trigger never triggers. I turned on webhook listening on the WhatsApp developers website and can see the messages I send. Any idea what I can do to troubleshoot this?

13

Did you guys found anything for this problem? i tried to create a new app i created i think 5 , and i still have the same problem i removed all the apps and kept 1 and still the same problem i tried to delete the subscription with the Delete Curl but did not made a difference. - I Then tried to create a new business account , and i have the same problem …

14

I’ve also got the same issue try everything from new app, new workflows, new numbers etc still no good. Can anyone provide a full walkthrough solution?

1 Like
15

I’m having the same problem, has anyone been able to fix it?

16

You just need to call the api subscrived_app api to fix it. Where is the doc for the end points.

I don’t know why but there is not info about this. I think the app is created with webhook configured by default to show results on the API Testing page and you need to configure a new webook to receive outside.