Make.com Google OAuth for users with restricted scropes without Google security assessment

Features
, ,
1

I am currently developing an app that integrates Google OAuth with restricted scopes, such as Gmail Compose. Currently I am handling OAuth process in my app, however I ran into an issue that I am required to undergo security assessment when verifying Google App. I am exploring the option of using Make to handle these Google actions on behalf of my users to simplify the OAuth process.

I imagine that the flow would look something like this:

  1. User connects his Google account via Make provided Google OAuth screen;
  2. User invokes “Create draft” or some other action in my system and calls Make webhook with some required data;
  3. Make creates a Gmail draft for that specific users.

So my question is - is it possible to fully rely on Make’s native Google actions to handle OAuth and Google API actions for all my users without requiring my app to undergo Google’s OAuth verification and third-party security assessment or would this assessment be required regardless when working with restricted scopes?

4

Welcome to the Make community!

Without verification, your custom GCP app supports up to 100 users, before Google blocks new logins. That’s their way of letting developers test things without forcing them into the full security audit straight away. Once you go beyond that, you’re expected to go through the official process.

For more information, see

Hope this helps! Let me know if there are any further questions or issues.

— @samliew
P.S.: investing some effort into the tutorials in the Make Academy will save you lots of time and frustration using Make!