Google Drive Input tool - Invalid Extension

[FkeetGuy]

Hi Team,

Alteryx Version Version: 2024.2.1.14

I recently updated the Google Drive connector tool(this was following the outdated python message). I followed the instructions and setup Google Sheets API, got the secret, and client id, enabled the API from the Goolge side everything looks like it should be.

I select Sign in using Web Browser & Connect Through Own Google App

Iv'e got my client id and secret and I click Sign in with Google. I go thorugh all the steps of authentication and give myself persmission. I tab back to Alteryx and can see on the Connected to that I'm Connected to my environment and I can chagne the 'Files to Display' but no matter what I choose no files show up.

This was a pretty straight forward setup vs the OneDrive setup which I'm likely to post about as well.

Any thoughts? thanks

[tim75 · Accepted solution]

Hello,

You recently updated the Google Drive connector tool in Alteryx version 2024.2.1.14 following an outdated Python message. You set up the Google Sheets API correctly, obtained your client ID and secret, enabled the API on Google’s side, and followed all instructions. When signing in using the web browser option and connecting through your own Google app, you successfully authenticated and gave permission, and Alteryx shows you are connected to your environment. However, despite being able to change the 'Files to Display' setting, no files are showing up. This issue could be related to OAuth scopes and permissions, so it’s important to ensure your Google app has the right access, such as full Drive read permissions, not just Sheets API access. Also, check that the files you want to see are actually in your Google Drive account and not only in shared drives or folders where you may have limited visibility. Try removing any filters in 'Files to Display' to confirm if files appear when no restrictions are set. Additionally, verify that your connector is the latest version and review Alteryx forums or release notes for any known bugs with Google Drive integration. Sometimes revoking the OAuth token in your Google account and reconnecting helps resolve hidden authentication glitches. If the problem persists, testing the same credentials outside Alteryx with a Google Drive API script can help isolate whether it’s an Alteryx-specific issue. If you want, I can assist you with next steps or help draft a support request to Alteryx.       Human to Cat Translator


Best Regards
tim75

[FkeetGuy]

Yeah, thank you, I hadn't added the google drive scope, that solved it. tyty

[FkeetGuy]

Another update, and I'll make a new thread if you think I should.

I can close the workflow and open it and run it wihtout clicking on any configuration and it works, I can even write to the file.

Is there somethign special different I need to do to let the scheduler process it? Just seems to hang at 33% thanks again.

[apathetichell]

Alteryx scheduler will not natively work with Python tools/connectors like Google Drive.

[FkeetGuy]

Is that a desktop automation limitation or a is it a limitation to server and desktop auto? Disappointing we were once able to setup schedules to use google sheets but now we can't.

[apathetichell]

That is a desktop automation limitation.You should be able to schedule google drive workflows on server IF you are using a service account key based authentication (vs a user oauth)....