The idea is:
Currently, when connecting an OAuth-based app (e.g., Google Drive) multiple times with the same account, n8n creates multiple credentials with identical account info.
This can lead to confusion — users might think they need to reconnect each time, even though an existing credential already exists.
My use case:
When setting up multiple workflows that use the same OAuth account (for example, the same Google Drive or Slack account), I often reconnect by mistake, thinking I need to reauthorize.
This results in multiple credentials with the same email/account name, making it unclear which one to select later — especially for users managing several workflows or environments.
I think it would be beneficial to add this because:
It prevents accidental duplication of credentials.
Keeps the credential dropdown clean and organized.
Improves clarity for users managing multiple workflows with the same connected accounts.
Aligns with UX patterns seen in other automation tools (Zapier, Make.com, etc.), where existing connections are reused when possible.
Any resources to support this?
Original GitHub discussion: n8n-io/n8n#21560
Maintainer Joffcom suggested raising a feature request to gather community feedback.
Are you willing to work on this?
Yes — I’d be happy to explore this enhancement and contribute a PR if the feature gains traction and aligns with the roadmap.