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?
This workaround worked for me… turns out you can click on the little expand on the text box where the error show, and add the phone number id behind.. and it works.
Thanks!!
had the same issue… I just regenerated new Access Token in API Setup … worked for me ..
I had the same issue - realized I had to add both the App and the WhatsApp account as assets to the user before generating the token. I had added the App before but I got exactly this error. As soon as I added the WhatsApp account as an additional asset, it worked.
this does not work. it says it cant find the number
Just to add I’ve the same issue, I did added the App and the WhatsApp as assets to the account, before generating a new token. I’m using a token with expiration set as never.
[SOLVED] Definitive Solution for WhatsApp Node API Permissions Error
Hello everyone,
After extensive troubleshooting on the issue discussed in this thread, I have found the definitive solution and wanted to share a clear, step-by-step guide.
The Problem: Like many others, I was facing two issues after creating a permanent System User token for the WhatsApp Business API:
The n8n WhatsApp node showed an [object Object] error and failed to load the list of “Sender Phone Number IDs”.
Even when entering the Phone Number ID manually, I received an API error: Object with ID '...' cannot be loaded due to missing permissions.
The Root Cause: The core problem is that when you create a new System User in Meta Business Manager, it has no permissions or access to any of your assets by default. You must manually grant it control over both your App and, most importantly, your WhatsApp Business Account (WABA) before generating the token.
Here is the exact process that solved the problem completely:
This is the most critical step. A System User without assigned assets is useless.
Go to your Meta Business Manager (business.facebook.com).
Navigate to Business Settings.
Under the “Users” section, click on System Users.
Select the System User you are using for your n8n integration.
In the right-hand panel, click the “Assign Assets” button.
A new window will pop up. You must assign two types of assets:
Apps: Find your app, select it, and enable Full Control.
WhatsApp Accounts: This is the key. Find your WhatsApp Business Account (WABA) in the list, select it, and enable Full Control.
If your WABA was not assigned, this was the source of the API error.
After you have assigned the assets, your old token is still invalid. You must generate a new one.
On the same System User page, click “Generate new token”.
Select your app from the dropdown.
Set the token expiration to “Never”.
Check the boxes for the following required permissions:
whatsapp_business_management
whatsapp_business_messaging
Generate the token and copy it.
Go to your n8n instance.
Navigate to the “Credentials” section.
Find and edit your WhatsApp Business credential.
Paste the NEW token you just generated into the “Permanent Access Token” field.
Save the credential.
After following these three steps, the API permission error was completely resolved. You may still need to enter the “Sender Phone Number ID” manually due to the known n8n UI bug, but the node will now execute successfully.
I hope this detailed guide helps everyone else who is stuck on this!
“Error fetching options from WhatsApp Business Cloud”
The same issue i faced but i found the solution the it also
Step 1: Change from Fixed to Expression
Step 2: Go to Your Previous Node
Step 3: Take phone_number_id
here is short tutr
After this You’re good to go.
