Describe the problem/error/question
I’m using the WhatsApp Cloud node in n8n to send messages. The workflow is configured correctly, and in the logs, it shows that the node executes successfully (status 200), but the messages are not actually delivered to the phone numbers passed in each item.
As shown in the screenshot below, all 4 items appear to have been executed successfully, yet the message is not always delivered.
The behavior is intermittent:
- Each item has a different phone number, and the node should send the WhatsApp message to all items.
- However, sometimes the messages are not sent at all, even though the output indicates success.
- No error is thrown — everything shows as if it worked.
- If I create a new WhatsApp Cloud node with the same configuration, it starts working again, but after some time, it stops sending messages again.
This issue happened both on version 1.83.2 and after updating to 1.106.3.
In case it helps, I’ve been using the system user token from Meta. While reviewing Meta’s documentation, I found a note stating that if the user does not have the required permissions, the API might return a response with HTTP status 200 but still include an error in the body.
My hypothesis is that if this happens, n8n might be interpreting the 200 status as a successful execution without checking the body for an error message — which would explain why the execution is marked as “success” even when no WhatsApp message is actually delivered. The weird thing is that in the beginning this was working without any problem using the same token
What is the error message (if any)?
No error message. All executions return status 200.
Information on your n8n setup
- n8n version: 1.106.3 (also tested in 1.83.2)
- Database: SQLite
- Running n8n via: Docker
- Operating system: Ubuntu 20.04