Why Can't I Authenticate Google Docs on n8n Cloud Like Developers Do?

Issue Explanation

The error you're encountering is due to Google’s OAuth verification requirements. For certain sensitive scopes—like those required for the Google Docs API—Google requires that the OAuth consent screen is associated with an approved application. Currently, n8n Cloud's integration for Google Docs isn’t fully approved for these scopes, so only developers using their own Google Cloud credentials (which have been properly configured and verified) can authenticate and test the node.

Workarounds

1. Developer Credentials:
   If you’re a developer, you can create your own Google Cloud project and set up OAuth2 credentials for Google Docs. This involves:

   • Creating a project in the Google Cloud Console.
   • Enabling the necessary API(s) (in this case, Google Docs).
   • Configuring your OAuth consent screen.
   • Creating an OAuth client ID, and using your custom OAuth Redirect URL from your n8n credential.

   Refer to the OAuth setup steps in the n8n documentation for detailed guidance.

2. Self-Hosting n8n:
   Using a self-hosted instance of n8n allows you to fully control the OAuth credentials. By setting up your own Google Cloud project and configuring the OAuth consent screen and client credentials, you bypass the restrictions currently in place with n8n Cloud.

3. Wait for Official Approval:
   If neither of the above options suits you, the alternative is to wait until Google Cloud grants n8n Cloud the necessary access as an approved platform for the Google Docs node. Once approved, the standard “Sign in with Google” flow on n8n Cloud should work seamlessly.

Summary

The problem is not with n8n itself but with Google’s verification process for sensitive OAuth scopes. Until the n8n Cloud version of this node is verified by Google, developers can work around the issue by using their own credentials or by opting for a self-hosted version of n8n.

Let me know if you need more details on setting up a custom Google Cloud project or further troubleshooting steps!