Hi everyone,
I’m having trouble integrating the WhatsApp node in n8n. When I use the final API key (the permanent application identifier), the node for sending WhatsApp messages stops working, and I receive the following error:
“Error fetching options from WhatsApp Business Cloud”
Has anyone else encountered this issue? Any suggestions on how to resolve it?
Thanks in advance!
It seems like you’re encountering an issue with the WhatsApp node after using the permanent API key. One thing to check is if you have the latest version of n8n installed, as updates can sometimes resolve these types of issues. Additionally, testing the workflow in a different environment or using a different approach to retrieve all items might help identify the root cause. Our team is growing and hiring, so if you’re interested in working with us, it’s a great time to get involved and learn from the folks on our team.
I have the same issue. Did you manage to resolve it in the meantime?
Your team?
Hey, i’m having the same issue. Unfortunately this happens with one number, but no with others. Both have the same permissions.
However if I try to query the cloud api directly, I can retrieve the data.
To be specific, I see those error messages when trying to select a number to operate or a template to send.
Hey!
I have exactly the same issue since I switched to a permanent token - even if the token has all the required whatsapp permissions… I don’t really understand what is happening!
Especially because I also can’t set the number to a fixed number via an ID or similar. Even providing a hardcoded number results in the error of “Error fetching options from WhatsApp Business Cloud”.
I am facing the same issue, every time I have to authenticate and key in the new token from meta into the WhatsApp node. Can someone help if there is any timeout for this defined some where ?
I’m having the same issue as the others mentioned above. The whatsapp nodes seem to work fine for about an hour or so, but then give me the same error “Error fetching options from WhatsApp Business Cloud”. I get a new API Access Token and start over…
Could it be the fact that you have to use a permanent token that is created under the system user settings?
You can try to ignore the error message and manually enter the Business Account’s Phone Number ID.
You can find it in the WhatsApp trigger node within the JSON object under
"metadata" → "phone_number_id".
I experienced the same thing previously. What I did was simply create a new application for my second number in Meta Developer and manually generate a token in the “API Setup” menu.
Permanent token/another used apps token (Success connected on credential)
New generated token on new apps (This generated token never expires)
I found this one. Maybe it helps.
Also I would try to hardcode the phone number and try if it works that way.
All the messages above are work around. Is there a definitely solution to this bug?
