Unverified50% confidenceFactExact time
When connecting a Google or Microsoft account, the OAuth permission flow must be completed: the user logs in in the browser and checks the permitted access scopes (such as reading mail but not sending mail), and the provider returns a revocable token to OGAD. Reading and sending are two separate sets of permissions.
1
Sources
50%
Confidence
Long-term
Relevance
10/13/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedOAuth 2.0规范将权限划分为不同scope，openid仅用于身份验证，email用于读取邮箱地址，https://mail.google.com/代表完整Gmail读写权限75% similarUnverifiedGoogle usually requires email verification before login, while the OIDC implementations of some self-hosted or niche providers allow users to set any unverified email; this inconsistency in verification policies across providers gives attackers an opportunity.74% similarUnverifiedConnecting n8n to Gmail typically relies on Google's OAuth 2.0 authorization mechanism, which allows third-party applications to access Google account resources in a restricted manner after user authorization without obtaining the account password.73% similarUnverifiedn8n's OAuth credential mechanism allows users to authorize via Google account login, with Google issuing access tokens and n8n automatically managing token refresh and storage in the background.70% similarUnverifiedGoogle has fine-grained control over Gmail API permission scopes, with read-only access to emails and read-write/delete access to emails being different permission levels.66% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1016492API
curl https://kongchang.com/api/v1/knowledge/claims/1016492MCP
get_claim(id=1016492)