"Sign in with Google temporarily disabled for this app"

This app has not been verified yet by Google in order to use Google Sign In.

getting the same thing

I'm afraid Google has shut down the API used by the workflow. Sorry, but it looks like they don't want to allow workflows/apps like this to protect their users.

@fniephaus do you have any plans to update it to use available API (maybe with limited functionality? the search would be worth a lot by itself)

@Stvad I'm afraid I don't have any plans, but I'm happy to help if someone is interested in updating the workflow. What kind of things are still allowed with the current API and without a review? To be honest, I don't want to go through the review process, I'm not even sure a workflow like this would pass it.

Ah, I'm not sure what is the review process =.

Here's Google's blog post on their API changes and the reviewing process: https://cloud.google.com/blog/products/g-suite/elevating-user-trust-in-our-api-ecosystems

Since https://www.googleapis.com/auth/gmail.readonly is covered by the new restrictions, I don't think this workflow will be able to do anything without going through the reviewing process.

The assessment fee is paid by the developer and may range from $15,000 to $75,000 (or more) depending on the size and complexity of the application.

I don't think we want to invest in an assessment of this workflow.

Hey @fniephaus and @sepehr I recently had the same error for a GDrive Alfred workflow and there was a solution. The original issue was an authentication load issue on a single Google project.

Anyway, I was able to perform the below steps and from what I can tell the workflow has full functionality, can view, add label, archive, reply, etc.

1. create your own Google project, consent page, and set up OAuth 2.0 Client ID and Secret from https://console.developers.google.com/
2. select Internal vs External, which gets you around the need for the "review" process
3. under the same project, goto API Library and enable the Gmail API
4. finally, edit the workflow's client_secret.json to include the new ID/Secret

One caveat, I do have my own GSuite account vs the free Gmail.com account, don't know if this matters or not.

btw - nice workflow!!

best,

this worked like a charm, after some debugging. Thank you so much!

1. create your own Google project, consent page, and set up OAuth 2.0 Client ID and Secret from https://console.developers.google.com/
2. select Internal vs External, which gets you around the need for the "review" process
3. under the same project, goto API Library and enable the Gmail API
4. finally, edit the workflow's client_secret.json to include the new ID/Secret

One caveat, I do have my own GSuite account vs the free Gmail.com account, don't know if this matters or not.

Me too, depends on whether free gmail account can access Google Cloud I think.

The above indeed fixes access. Not sure why I don't see all the files, some are not found (will post on the forum).

For others trying to fix this:

# Go to Alfred dir
cd ~/Library/Application Support/Alfred

# Find file with secret and id
find . -name google-drive.rb

# Edit and update secret and id
vi ./Alfred.alfredpreferences/workflows/user.workflow.<LONG ID>/google-drive.rb

Then re-do the access/login part.

Another description I found for enabling the API: http://tajinder.net/articles/fix-alfred-workflow-issue-to-search-on-google-drive

Good luck!