Zoom WJT Auth will be deprecieted soon. I am trying to set my Oauth following the steps that I found in de Zoom Node documentation. Got this message when trying to activate the app in the zoom marketplace: Something went wrong. Please try again!
URL: https://oauth.n8n.cloud/oauth2/callback?code=jVFwbn8XCI9WsH3MtDkTyuyGxEKV4zRXw
My credentials worok fine when using de Zoom node but not when trying to use endpoints thru http request node.
Apparently as the last step on the settings did not work (the callback) the credential has not permissions in the scope.
That is interesting, I am not sure why the authentication fail unless there is a scope issue. We have just released 0.229.0 which will include more useful errors but it won’t be available on cloud for a few days. I suspect this may show us what is going on and we will be able to work it out from there.
For now though I would double check the settings and maybe recreate the credential and see if that helps.
It may also be worth sticking with JWT for now until the new version is available as well so that it doesn’t block you from building.
I have my all operations working on workflows based on JWT credentials on N8N and need to move to oAuth ASAP. Do you have any recommendation to solve the problem with the callback?
Using JWT was a temporary solution until 0.229.0 is available which has more information on OAuth issues.
I have however just given this a go on my cloud account and I can connect without any issues, Can you share the settings you have configured in Zoom and where you see the error message as I suspect this could be a configuration issue with the Zoom app.
Hi @Jon , I’ve been exploring different options to resolve the issue. I tried deleting and reinstalling both the Zoom apps and the credentials. Additionally, I experimented with using both the HTTP node and the Zoom node. Unfortunately, I encountered the same error related to callbacks and scopes. Do you have any suggestions on how to proceed?
Annoyingly I can’t think of anything, I have gone through the setup a couple of times and it seems to work for me which is of course not really a good answer.
Did you try with the subdomain check disabled? That is the only difference that I can see. Have you also tried on a newer version of n8n?
