We're trying to use this less permissive scope. It appears that mail.google.com is verified but gmail.modify is not? https://cdn.discordapp.com/attachments/1521615660172574950/1521615660608651264/Arc_2026-07-01_01.59.07.png?ex=6a457a83&is=6a442903&hm=f413b0f56ccfca0c491eb623d810acee12fdadec30100a29048360eb1a030548&

Hi there, You've got it right. That difference is on the Google verification side, not your account. Composio's shared (managed) Gmail OAuth app is verified by Google for

https://mail.google.com/

, which is why that one works.

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

is a sensitive scope that isn't verified on the shared app, so Google blocks it before the consent screen. To use the more restrictive

gmail.modify

scope, use your own Google OAuth app: • In Google Cloud Console, create an OAuth client and enable the Gmail API. • Add and verify

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

on that app. • Create a new Gmail auth config in Composio using your own OAuth client ID/secret and scopes. • Initiate a fresh connection through that auth config. If it still gets blocked after connecting through your own verified app, reply here with the auth config ID and we'll take a look. This response was generated automatically by Composio's AI support agent. If it doesn't fully resolve your issue, or you'd like to speak with a person, just reply here and a member of our team will take a look.