Hi Composio Team, We’re running into an issue with Google’s approval process for our Drive integration. Since we’re using our own client ID and secret, Google is requiring app verification for the requested Drive scopes. Their team suggested switching to the non-sensitive drive.files scope, which would not require verification. However, this approach limits our Web App’s capabilities, users would only be able to manually pick a file via the Drive Picker and add it to context. They would lose the ability to query their Drive using natural language, such as: “Schedule a follow-up meeting based on the GTM-25 document on my Drive.” Could you please advise on the best path forward?

You can use Composio's default Google Drive auth config. For sensitive scopes, verification is mandatory.