Oauth creds failing

Hi everyone I’m just having some issues surrounding OAuth and was wondering if I can get some help?

So I am using an OAuth cred from GCP in a web app that I’m creating, and I am able to connect and use GMail/Google Drive/sheet and etc. but I can’t connect Microsoft Drive for example or the other sources.

The obvious solution is to get OAuth credentials for each of these services and configure them in the app, but I just wanted to ask if there is any other way that is easier to maintain and configure?

thanks for any help with this!

It looks like your topic is missing some important information. Could you provide the following if applicable.

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:

Hey @kyle_swire-thompson,

Are you getting any errors when trying to connect? I find the Google errors are normally pretty good at explaining what the issue is.

Hi Jon,

Thanks for the replie, the google one’s are okay it’s the other ones like Microsoft drive for example.

Hey @kyle_swire-thompson,

Ah I missed that bit, The first part of the question still applies though what error are you seeing when trying to connect?

I’m afraid we don’t get an error. let me rephrase the question:

Do we need to get OAuth credentials for each of the OAuth services? currently we have setup Google’s OAuth and services related to google work fine we are able to connect to google drive and sheet and etc. but for example Microsoft wants us to setup an OAuth in Azure, do we need to do this for all of the services? if so how do we manage this in the codebase?

Thank you for reaching out!

Hey @kyle_swire-thompson,

That makes more sense so for Microsoft it is not that differnet from Google, You will need to create your app registration then apply any permissions you might need for it. Similar to Google though you can use credential overrides so that each user doesn’t need to input the client id and client secret and will instead just see a “click to connect” button. This would only make sense if your internal users were connecting to n8n to authenticate if the authentication was happening outside of n8n it will be more complicated.