I am not sure I fully understand the issue here, is the webhook node running multiple times or the WhatsApp node? Do you also have a screenshot of an execution where it has ran multiple times as the ones you have posted only show it happening once.
That is a bit worrying as the node is not showing that happening looking at your images.
One node would finish before the next starts so it sounds like there is more to this. If you manually run the WhatsApp node does it also send a bunch of messages?
You have circled the executions on the left… is that the multiple runs you are seeing?
Can you share the version of n8n you are running and how you have it installed? It would also be handy to know how you are calling the webhook as looking at that I would say the webhook has been called multiple times so looks like it could be an issue outside of n8n.
Yes, you are right… webhook call is also making even i remove connection to WA API… now remove the webhook and add On-click node to execute manually… It works fine… but It takes around 1 minute to receive WhatsApp template message…
Could you please help me to rectify my WA webhook issue…
Webhook configuration is done & succeed as well (calling webhook endpoint returns hub.challege key, it require only one time for configuration… i tried to remove webhook response node and run, still infinite execution is happening… PLEASE HELP IF ANY CHANGES REQUIRED)
Split in Batches will probably not help as you only have one input item, The issue here is that something is calling your webhook multiple times this is not n8n running endlessly.
What is actually calling your webhook? If it is the Meta callback service that is probably going to be your issue and it would be worth speaking to them to find out why they are sending so many requests.
The endless execution is caused by the message you send from from n8n. Immediatly after the webhook you need to out an IF node and check if the the messages property is an array with only 1 object inside. If yes it is a message coming from the user else it is a system message and you dont have to do anything. Consider that every message you send generates 2 system messages notified to the hook in this causes your infinite loop.