Hello team, I was succesfully able to create an Oauth for whats app on N8N.
It is working and popping up for the trigger to receive messages, however, when I want to send a message back the Whats App OAuth does not show up as an option. Is that a bug? or is that on purpose?
Could you provide your scenario json and other details on how you setup the scenario?
1 Like
Could you show in the nodes where you say the connection isn’t available?
Could you copy the entire workflow, and paste it into the ``` when you click on the ‘</>’ button?
Ah well unless hardcoded all creds/PII are auto removed when pasted.
But, I believe I see the confusion.
Oauth 2 is only supported for the WhatsApp triggers, and the rest of the action nodes for WhatsApp only support API key.
You can see it later in the docs:
wow interesting… Very though that the cloud is an API key. It lasts only 2 hours. Do you suggest work arounds so the response could have an oAuth?
Thanks!
I am unsure, but you could manually fetch a new api key before every attempt to respond and insert it dynamically.
Or if on whatsapp’s end responses don’t have this limitation, you can manually use the HTTP node with the whatsapp Oauth.
But I am not confident on either solution without research.