Using Google Workspace (Gmail, Drive, Docs, Chat, etc.) nodes

This guide provides recommendations for configuring Google Workspace nodes in n8n.

Overview

n8n supports two primary authentication methods for Google Workspace integrations:

• ✅ OAuth2: (Recommended for most workflows) Standard, personal authentication
• ⚠️ Service Account: enables reliable automation, content sharing, and team collaboration

OAuth2 Configuration (Recommended or most workflows)

Google OAuth2 Credential Setup

Create a new credential and select the Google service you want to connect with from the list.

This will open up the credential creation dialog. Rename the credential to something like “Google Service - Your Name”. Make sure OAuth2 is selected. Sign in with Google.

After you have signed in, you will see a green success notification on the dialog. You may then close the dialog.

Common OAuth2 Issues

• ⚠️ Token expired: This will happen periodically and break your workflows because the OAuth2 connection with Google is no longer valid. Simply re-authorize the OAuth2 connection in your n8n credential by signing in again.
• Insufficient permissions: You may be using a Google node for a service which is not enabled for use from n8n. Please reach out to the Agentic AI - Community space in Google Chat for help.

Service Account Configuration

Note

⚠️ Important: Service account credentials are significantly more complex and to create and set up. They are also not free. They cost Trimble the same amount that a Google Workspace account costs for a real user.

Where service account credentials are beneficial

✅ Content Sharing & Collaboration

• Share files and folders directly with service account email
• Enable seamless access across team members without individual authorization
• Support for shared drives and team folders

✅ Reliable Automation

• No user intervention required for workflows
• Authorization Tokens don’t expire unexpectedly
• Consistent access for automated processes

Use service account authentication for:

• Team or organization-wide automation
• Sharing content with multiple users
• Automated processes that run without user intervention
• Long-running workflows that need reliable access

You would need a GCP Project for a service account credentials and Google Workspace service account for Impersonation.

To request a GCP Project, submit a request form to the Enterprise Cloud team. For detailed information about Enterprise Cloud Management and the request process, refer to the Enterprise Cloud Management documentation.

For Google Workspace service account impersonation, contact the IT Helpdesk team. Note that this approach is not generally recommended due to its complexity and cost implications.

For detailed instructions on setting up Google service accounts in n8n, refer to the official n8n documentation on Google Service Account configuration.