2
5 Comments

Google OAuth verification process is quite long

Hi đź‘‹

We are trying to go through Google OAuth Validation process for an add-on we are working on, but it’s quite difficult!

It has started mid-January and we are still not there. We are using some “sensitive” scopes (Gmail one), so it kind of explained that it is taking so long. But still :)

Is anyone facing the same issue? Did something help to move forward?

#tech-questions

on March 12, 2019
  1. 1

    are you still facing this? We're stuck here now and looking for a solution.

    We're building a sales automation tool for creators to find and close brand deals. We generate personalized cold email sequences for creators and want to enable them to manage their dealflow within our platform.

    For our gmail app verification, we just received the email to go through their CASA assessment which we see can also take considerable time. For read purposes, we just need to know which brands had responded and the content of those messages (only of the ones to brands that were contacted through our platform - not their whole inbox) so they can track their deals within it.

    • Do you know of any workarounds or ways we could enable this without the having to go through this assessment? Or any ways to expedite the process?
  2. 1

    I’m talking about that verification process : https://developers.google.com/apps-script/guides/client-verification

    Without being approved by Google team, the OAuth flow shows a warning that the app is not verified...

  3. 1

    Which verification? You're asking google to o_auth into gmail?

    I assume you're trying to read their emails?

    I was thinking of doing something like this to get users PDFs but to also (with their permission) send invites.

    1. 1

      You're asking google to o_auth into gmail?

      While add-ons technically use OAuth, it's not the same as the for the Gmail API. Add-ons only get access to specific email messages on a thread-by-thread basis when the user launches the add-on while a thread is open. This is as opposed to the normal Gmail API, where apps get access to the user's entire inbox, or to Chrome Extensions where they also (currently) get access to everything the user views in their browser.

      It's still a huge process to get approved though, it goes through multiple rounds of QA and their engineering team audits every line of code. I'm also currently going through this for two add-ons I made, overall it's going to be a multiple month process.

      1. 1

        can SaaS platforms be considered add-ons or are add-ons only those that are living within Gmail?