Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
Mirrored from https://github.com/Camo67/composio.git
Synced Nov 21, 06:00 UTC
| 1 | --- |
| 2 | type: "reference" |
| 3 | title: "Google OAuth setup and consent" |
| 4 | description: "Shared OAuth setup and consent guidance for Google toolkits." |
| 5 | category: "auth-config" |
| 6 | visibility: "public" |
| 7 | timestamp: "2026-08-17T00:00:00Z" |
| 8 | tags: |
| 9 | - "google" |
| 10 | - "oauth" |
| 11 | --- |
| 12 | # Google OAuth setup and consent |
| 13 | |
| 14 | ## An unapproved Google OAuth scope can block consent |
| 15 | |
| 16 | Google can block sign-in when an OAuth app requests a sensitive or restricted |
| 17 | scope that is not approved for that app. Use the scopes already available on |
| 18 | the selected Composio auth config, or create a customer-owned Google OAuth app |
| 19 | and complete Google's required verification before requesting additional |
| 20 | scopes. After changing scopes, create a fresh connection so the user grants the |
| 21 | new scope set. |
| 22 | |
| 23 | Google's current verification requirements are documented in its |
| 24 | [OAuth 2.0 policies](https://developers.google.com/identity/protocols/oauth2/policies) |
| 25 | and [sensitive-scope verification guide](https://developers.google.com/identity/protocols/oauth2/production-readiness/sensitive-scope-verification). |
| 26 | |
| 27 | ## A customer-owned OAuth app controls the provider consent-screen brand |
| 28 | |
| 29 | Use a customer-owned Google OAuth app when the Google consent screen should |
| 30 | show the customer's app name and branding. To avoid showing a Composio domain |
| 31 | in the redirect path as well, route the callback through the customer's domain |
| 32 | as described in [white-labeling authentication](https://docs.composio.dev/docs/white-labeling-authentication#routing-the-callback-through-your-domain). |
| 33 | |
| 34 | The OAuth app's authorized redirect URI must still match the callback URI |
| 35 | shown by Composio. Provider consent-screen branding and the URL to which the |
| 36 | customer's application sends a user after authentication are separate settings. |