Google Docs Writer Failed! with/without Make Doc Public checked

[rmck]

Google Docs Writer is returning the following error when the Make Doc Public is both checked and unchecked.

“Google Docs Writer Failed!
The application doesn’t have permission to create public documents. Please check the Google Cloud Console settings and ensure the necessary scopes are approved.”

Anyone else having this issue?

[Wasay-Gumloop]

Hey @rmck - Could you please share the failed run link from the https://www.gumloop.com/history page?

[rmck]

https://www.gumloop.com/pipeline?workbook_id=cqsLxWYZx6xrA8Fn5obSqQ&run_id=LtGkGJjBpfaDxLXnDpaAy5

[Wasay-Gumloop]

Looping @rahul-gumloop here ^

[rahul-gumloop]

Hi,

It looks like your organization is blocking Gumloop’s access to creating Google Docs. Can you tell your IT team to check the following:

1. Sign in to the Google Admin console (admin.google.com) as an administrator 1.
2. Navigate to Security > API Controls1.
3. Review the “Block All Third-Party API Access” setting. If it’s enabled, this could be blocking the app1.
4. Click on “Manage Third-Party App Access” to view a list of apps with access to Google Workspace data1.
5. Look for Gumloop in the list. Note its status (trusted, limited, or blocked)1.
6. If it is not listed or is blocked, hover over the app name and select "Change Access"1.
7. Choose the appropriate access level.
8. If necessary, review individual user access to Gumloop:

• Go to the list of users in the Admin console
• Click on a user’s name
• Check the “Security” section for "Connected Applications"1

9. Ensure that the necessary Google Workspace APIs are enabled for your app in the Google Cloud Console6.

[rmck]

Thank you, Rahul. I believe the Google Admin console isn’t available for Gmail accounts. Interestingly, I initially tried using a Google Workspace account but abandoned it after encountering the same public documents error when attempting to write to a non-public document. Would you recommend giving Google Workspace another try?

[rahul-gumloop]

Ah apologies, didn’t realize this was a gmail account. A couple things about the run you linked:

• Can you try deleting the node and re-adding it, but NOT selecting a Google Drive folder, and NOT selecting “Make Doc Public”?
• If the above works, can you try in isolation selecting “Make Doc Public” and running and seeing if that works? And then (without “Make Doc Public” selecting a Google Drive Folder and seeing if that works?
• I suspect the issue here is actually that the Google Drive and the Google Doc credentials are mismatched, so the account that you’re creating the doc with doesn’t have permission to create a doc in the given folder, but the above steps will help confirm and narrow down the issue

If any / all of the above fail, please send links to each of the runs with those settings being attempted and we can investigate further.

[rmck]

I deleted the node and re-added it, did NOT selecting a Google Drive folder, and did NOT selecting “Make Doc Public”. Same error.

Failed run link:
https://www.gumloop.com/pipeline?workbook_id=cqsLxWYZx6xrA8Fn5obSqQ&run_id=VfqT9U4rYNUh7QW7D324rV

[rmck]

[rmck]

Google Drive File Writer does not fail, but the document is 0 bytes (empty).

[rahul-gumloop]

Hi, for the Google Docs scenario. Can you try revoking all Google Docs and Drive credentials from the credentials page: https://gumloop.com/credentials

and then re-connecting them? And then trying again with the same scenario of no to make doc public and no folder.

[rmck]

Thank you Rahul. We have success! revoking and re-authenticating the credentials did the trick.

[rahul-gumloop]

Great, sorry about the troubles