Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.

next
md 1.7 KB

type: "reference" title: "Google OAuth setup and consent" description: "Shared OAuth setup and consent guidance for Google toolkits." category: "auth-config" visibility: "public" timestamp: "2026-08-17T00:00:00Z" tags: - "google"

- "oauth"

Google OAuth setup and consent

Google can block sign-in when an OAuth app requests a sensitive or restricted scope that is not approved for that app. Use the scopes already available on the selected Composio auth config, or create a customer-owned Google OAuth app and complete Google's required verification before requesting additional scopes. After changing scopes, create a fresh connection so the user grants the new scope set.

Google's current verification requirements are documented in its OAuth 2.0 policies and sensitive-scope verification guide.

Use a customer-owned Google OAuth app when the Google consent screen should show the customer's app name and branding. To avoid showing a Composio domain in the redirect path as well, route the callback through the customer's domain as described in white-labeling authentication.

The OAuth app's authorized redirect URI must still match the callback URI shown by Composio. Provider consent-screen branding and the URL to which the customer's application sends a user after authentication are separate settings.