How can I avoid Google App verification for my personal n8n Google workflows?

Below is some guidance specific to how Google handles OAuth apps rather than an n8n issue:

Do You Need to Apply for Verification?

• For Personal Use:
  If you’re only using the credentials with your own Google account, you might avoid applying for full verification by creating your OAuth credentials from the exact same account you plan to authenticate with. Google’s documentation even advises that if you use OAuth credentials generated from your own account, you can dodge some of the warning messages (like “Google hasn't verified this app”).

• When Sensitive Scopes Are Involved:
  Some scopes (for example, the one for accessing Google Docs or those related to Google Apps Script) are classified as sensitive. Even if you’re the sole user, if you’re using one or more sensitive scopes, Google will require that you go through the verification process in order to remove warnings and fully lift test mode restrictions. This step is needed if you want to avoid having your workflows stop or receive warning dialogs.

What Does the Verification Process Entail?

• Detailed App Information:
  You’ll need to provide a comprehensive description of your application, including how and why each sensitive scope is used.

• Demo Video Requirement:
  Google may request a video walkthrough demonstrating how users (in your case, you) will interact with the app. This requirement is meant to ensure that the app only uses the scopes as described.

• Supporting Documentation:
  Depending on the scopes and your app’s purpose, you might need to provide additional information or undergo a security review.

Workarounds to Consider

• Separate Google Cloud Projects:
  One option is to create a dedicated Google Cloud project (and hence a separate OAuth app) solely for use with n8n. This way, you can configure it as needed without impacting any other apps.

• Continue in Testing Mode:
  If you’re comfortable with periodic interruptions or the warnings (and if they don’t exceed your practical usage limits), you might choose to continue using the credentials in testing mode. However, be aware that Google-imposed usage limits might cause your workflows to lose access until reauthorization is performed.

Conclusion

In summary, while you may not absolutely have to undergo verification for a personal app if you generate the credentials from your own account, the use of sensitive scopes such as those needed for Google Docs almost certainly triggers the requirement for verification. If you want a seamless experience without testing warnings or interruptions, you’ll likely need to apply for verification—and be prepared to follow the guidelines (including the video walkthrough) as outlined in Google’s documentation.

This behavior stems entirely from Google’s app security standards and is not an issue introduced by n8n.