hey on my google calender on n8n it doesn’t show a redirect url, client detail or client secet, all it says is “allowed https request domains” how do i fix this?
Describe the problem/error/question
What is the error message (if any)?
Please share your workflow
(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)
Share the output returned by the last node
Information on your n8n setup
- n8n version:
- Database (default: SQLite):
- n8n EXECUTIONS_PROCESS setting (default: own, main):
- Running n8n via (Docker, npm, n8n cloud, desktop app):
- Operating system:
Hey @shuaib_mohamed !
Ae you on self-hosted or Cloud version?
If is cloud version, is normal… you have just to click connect since n8n cloud handles that in background.
In self-hosted version you can set that details .
Hi @shuaib_mohamed welcome to the community!
If you could copy-paste a screenshot that will help diagnose the issue further… just remember to black out any secrets from the screenshot.
What steps have you followed to create the google credentials?
Did you follow the n8n docs to create your Google oAuth client credentials?
hopefully this helps, I do have a google cloud I just cannot get it to connect to my n8n because it doesn’t show redirect url, client detail or client secet. Thanks!
That’s how it supposed to work @shuaib_mohamed , it seems you are using the Cloud n8n version.(and n8n it handles by itself in background).
Only in the self-hosted version you can see that type of credentials where you suppose to do it manually.
Cheers!
From your image, I can see
From your screenshot I can see it showing a green box and Account connected. And that you are also trying to connect to Google Calendar. This is expected because we are using OAuth2 Authorization Code Flow - so there is no need for supplying a client ID and secret.
However, if you want to connect say a Google Drive trigger or you want to search a google drive, this is when you do need to setup and use OAuth2 Client Credential Flow, and this does require supplying a Client ID and Secret.
For example below this is what shows when I try to setup a trigger on a Google Drive
What this shows me is that I think you are connecting to your own personal Google calendar and so the credential flow needed is Authorization Code Flow and so does not required supplying the Client ID and Secret.
Are you haveing any issues connecting to your calendar?
If you are, please supply some more screenshots, errors and a copy of the workflow and that may help us to diagnose the problem further.
