How Do I Fix n8n Automations Broken by New Google OAuth2 Rules?

Below is some guidance on how to update your Google OAuth2 credentials in n8n to comply with the new Google requirements:

---

What Changed and What You Need to Do

Recent changes in Google’s OAuth2 rules might invalidate your existing credentials. This means you’ll need to reconfigure your Google Cloud project and create new OAuth2 credentials. The process involves the following steps:

1. Create or Use an Updated Google Cloud Project

   • Log in to the Google Cloud Console and select or create a new project.
   • Make sure you have the proper access and project selected.

2. Enable the Required APIs

   • Visit the APIs & Services Library and enable the specific API(s) required for your workflow (for example, Gmail, Google Drive, etc.).

3. Configure Your OAuth Consent Screen

   • Go to APIs & Services > OAuth consent screen in the Cloud Console.
   • Configure or update the consent screen. Google now requires more detailed app verification and updated scopes info, so make sure you fill in all the necessary fields (app name, user support email, authorized domains, etc.).
   • If you are using n8n Cloud visit the docs for the appropriate domain; if self-hosting, add your instance’s domain.

4. Create New OAuth Client Credentials

   • In the Cloud Console, navigate to APIs & Services > Credentials.
   • Choose + CREATE CREDENTIALS > OAuth client ID.
   • Select Web application as the application type and update the generated Name to something recognizable.
   • Copy the OAuth Redirect URL from your n8n credential and paste it into Authorized redirect URIs.
   • Create and note your new Client ID and Client Secret.

5. Update Your n8n Credential

   • Open your n8n instance and go to your Google credential settings.
   • Replace the old Client ID and Client Secret with the new values.
   • Ensure you also review and update the list of required scopes. For example, if you’re using multiple Google services, enter scopes as a space-separated list.
     For instance:

     https://www.googleapis.com/auth/gmail.labels https://www.googleapis.com/auth/gmail.modify
     

   • Complete authentication by selecting Sign in with Google and then save your credentials.

---

Useful Documentation

To assist with this process, please refer to the following sections in the n8n docs:

• Google: OAuth2 generic – For credentials that use OAuth2 with custom operations.
• Google: OAuth2 single service – If you’re using a single service such as the Gmail node.

Each guide provides detailed steps for setting up your Google Cloud project, enabling APIs, configuring the consent screen, creating the OAuth client, and finalizing the credential in n8n.

---

Final Notes

• It’s important to double-check that the Authorized Redirect URI in the Google Cloud Console exactly matches what n8n expects.
• Google’s changes could also affect the scopes you need—ensure that only supported scopes for your service are enabled.
• For Gmail nodes, while Service Accounts are an option, we recommend using OAuth2 due to their improved support and simplicity.

By following these updated instructions, you should be able to create new credentials that meet the latest Google OAuth2 rules and restore the functionality of your automations.

If you encounter further issues or specific error messages, please let us know so we can help troubleshoot further.

Below is a summary of the steps you'll need to follow to update your Google OAuth2 credentials in n8n. n8n provides updated documentation that walks you through the process in detail.

What Changed and What You Need to Do

Recent changes to Google’s OAuth2 rules mean that you must now ensure your Google Cloud project and OAuth credentials are compliant with the new policies. This typically involves:

• Updating your OAuth consent screen: Make sure that the essential details (App name, User support email, and Authorized domains) are correct.
• Configuring your OAuth Redirect URIs correctly: When creating your OAuth client credentials in Google Cloud, copy the OAuth Redirect URL provided in your n8n credential and paste it into the Authorized redirect URIs field in the Google Cloud Console.
• Double-checking scopes: If you have been using custom scopes, ensure that they are still valid and supported by the n8n integration.

Steps to Create New Credentials

n8n offers two ways to set up Google OAuth2 depending on your use case:

For a Specific Service (e.g., Gmail, Google Calendar, etc.)

1. Create or Select a Google Cloud Console project.
2. Enable the required APIs.
3. Configure your OAuth consent screen according to Google’s guidelines.
4. Create your OAuth client credentials:
   • Choose Web application as the type.
   • Copy the OAuth Redirect URL from your n8n credentials and add it under Authorized redirect URIs.
5. Finish your n8n credential configuration by pasting the Client ID and Client Secret into n8n.

See the updated documentation under the OAuth2 single service section for a step-by-step guide.

For Custom Operations Using Generic Google Credentials

1. Create a Google Cloud Console project (or select an existing one).
2. Enable necessary APIs.
3. Set up the OAuth consent screen with all required details.
4. Generate your OAuth client credentials:
   • Make sure to update the Authorized redirect URIs with the URL provided by n8n.
5. Complete your n8n credential configuration by entering the Client ID, Client Secret, and enclosing all required scopes (entered as a space-separated list).

Refer to the OAuth2 generic documentation for more details.

Next Steps

1. Review the Updated Docs:
   For the most recent instructions on setting up Google OAuth2 credentials, please review our updated guides:

   • Google: OAuth2 single service
   • Google: OAuth2 generic

2. Update Your Credentials:
   Recreate your credentials by following the detailed steps outlined in those guides, ensuring all redirect URIs, scopes, and consent screen configurations meet Google’s new requirements.

By following these steps, you should be able to update your OAuth2 credentials to work with Google’s new rules and get your automations back on track.

If you have any further questions specific to this process, please let us know!