Prevent WhatsApp Webhook from sending message status

[Murilo_Lima_Alves]

Hello guys.

I’m using n8n to build a WhatsApp virtual assistant. Everything works as expected, but I noticed that each message sent to the test number triggers three additional executions:

After reading the Meta documentation, I found that when the Message API is activated, status updates are also sent. The executions are:
#914 - The sent message
#915 - Status sent
#916 - Status delivered
#917 - Status read

To avoid errors in the execution history, I added an If node to advance only if the “message” array exists. However, this doesn’t prevent the Webhook from being triggered, which still consumes my execution limit. Is there a way to avoid this situation? I saw a similar topic without a solution to this.

Information on your n8n setup

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

[solomon]

What do you have enabled here?

[Murilo_Lima_Alves]

My WhatsApp trigger has only Messages enabled, just as yours:

[solomon]

Hey @Murilo_Lima_Alves,

I just checked WhatsApp Webhook documentation and unfortunately there’s no current solution for your problem.

You will receive extra events =(

I even found another post about the same issue and they solved it just like you did.

• Prevent unnecessary webhook triggers in n8n from WhatsApp API - #12 by Jaylton_Alencar

If my reply answers your question, please remember to mark it as a solution.

Btw… are you Brazilian too?

[Murilo_Lima_Alves]

No problem mate, I’ll consider the possibility of a local host to use this integration.
Yes, I am from São Paulo mano