This is expected behavior from Google’s side: the “App is blocked / unverified app” page typically appears when the OAuth client is requesting scopes that Google hasn’t verified for that client (often after adding scopes beyond defaults). Composio-managed OAuth is meant for quick start, but it won’t always cover every Gmail scope for production flows. Ref: Gmail FAQ (“Why am I seeing ‘App is blocked’…”) — https://docs.composio.dev/toolkits/gmail.md What to do: - If you need

https://www.googleapis.com/auth/gmail.modify

, switch to a custom auth config (bring your own Google OAuth app), request exactly the scopes you need, and (if required) submit for verification in GCP. Ref: Managed vs custom auth — https://docs.composio.dev/docs/custom-app-vs-managed-app.md Ref: Custom auth configs — https://docs.composio.dev/docs/auth-configuration/custom-auth-configs.md One quick confirm so we can point you to the right setup: are you using Composio-managed OAuth today, or a custom Google OAuth client already (your own client_id)? @User tagging staff because this may need owner action.

Hi Composio support team, We built an app that lets users connect Gmail through Composio so our agent can send and update emails. We were using this scope: https://www.googleapis.com/auth/gmail.modify This used to work, but now Google shows an app blocked / unverified app error during OAuth. Are we supposed to keep using gmail.modify with the Composio-managed Gmail app, or is there another recommended scope/auth config setup?

If you’re using Composio-managed Gmail OAuth, then yes — this is expected: Google will show “App is blocked / unverified app” when the OAuth client is requesting scopes Google hasn’t verified for that client (commonly happens after adding extra scopes like

gmail.modify

). The Gmail toolkit FAQ calls this out directly and recommends either removing extra scopes or switching to your own OAuth app. Docs: https://docs.composio.dev/toolkits/gmail (see “Why am I seeing ‘App is blocked’…”) Recommended production setup: keep Composio-managed auth for quickstart, but for

https://www.googleapis.com/auth/gmail.modify

you should move Gmail to a custom auth config (bring your own Google OAuth client) and request exactly the scopes you need (and complete Google verification if required). Docs: Managed vs custom auth: https://docs.composio.dev/docs/custom-app-vs-managed-app Docs: Custom auth configs: https://docs.composio.dev/docs/auth-configuration/custom-auth-configs.md One detail to confirm so we can point to the exact next step: are you adding

gmail.modify

by customizing scopes on an auth config, or are you just using the default managed flow and Google is blocking even without extra scopes? @User tagging staff because this may need owner action.

I am using composio managed

You can use https://mail.google.com/ - Our app is approved for that.