You picked the complicated route — navigating Google’s developer console to avoid a monthly subscription fee. That’s a reasonable call. Here’s how to get through it without a software degree.
Disclosure: Some links in this article are affiliate links. If you purchase through them, we may earn a small commission at no extra cost to you.
The math: Time to implement: ~30 min | Tasks automated: email triage, auto-replies, label sorting | Weekly time reclaimed: ~2-4 hours
The Fork in the Road: n8n Cloud vs. Self-Hosted Setup
Here’s the thing: which path you take depends entirely on how you installed n8n.
n8n is an open-source workflow automation platform. Think of it as a visual board where you drag, drop, and connect apps together. A “node” is one block on that board representing a single app or action, like “read Gmail” or “send a Slack message.”
OAuth (Open Authorization) is a security handshake. Instead of giving n8n your Gmail password, OAuth lets Google issue a temporary pass that says “this app can read your email, but nothing else.” Every Google-connected app you have ever used goes through some version of this.
Now, the fork. n8n Cloud (starting at $20/mo billed annually — check n8n’s pricing page for current rates) handles OAuth for you behind the scenes. You click “Sign in with Google,” approve the popup, and you’re done. No developer console required.
Self-hosted n8n (free, unlimited executions) requires you to create your own OAuth credentials in Google Cloud Console. Google has no idea who your self-hosted instance is, so you introduce them manually. This is the nuclear submarine path.
Who should use which:
- n8n Cloud if you want Gmail connected today and $20/mo is a reasonable trade for skipping everything below. Confirm current pricing at n8n’s site before upgrading.
- Self-hosted if you already run n8n on your own server (or Railway, Docker, etc.) and prefer zero recurring platform fees.
The rest of this tutorial covers the self-hosted path. If you chose Cloud, skip to the final section for your first workflow idea.
Navigating Google Cloud (The Dummy-Proof Walkthrough)
The upshot: you only need four screens out of the hundred Google shows you.
The Google Cloud Console is built for developer teams managing thousands of services. You need exactly one service (the Gmail API) and one credential set. Everything else on screen is noise. Here is what to do and, more importantly, what to ignore.
Step 1: Create a Google Cloud Project
Time: 3 minutes
Before starting, confirm you are logged into the same Google account that owns the Gmail address you want n8n to access.
Go to console.cloud.google.com. If this is your first visit, Google may ask you to accept terms. Accept them.
At the top of the page, find the project selector dropdown — it usually says “Select a project.” Click it, then click “New Project.” Name it something recognizable. “n8n-gmail” works fine. Leave the organization field alone if it appears. Click Create.
You will know it worked when the project name appears in the top bar dropdown.
Ignore: billing setup prompts, “Getting Started” tutorial cards, the dashboard widgets. You do not need billing enabled for the Gmail API at personal usage levels.
Step 2: Enable the Gmail API
Time: 2 minutes
In the search bar at the top of Google Cloud Console, type “Gmail API” and select it from the results. You will land on a product page. Click “Enable.”
That single click tells Google your project is allowed to talk to Gmail. Nothing else happens yet.
You will know it worked when the page changes to show a Gmail API dashboard with graphs (they will be empty, which is fine).
Ignore: the “Credentials” button on this dashboard page. You will create credentials through a different, more reliable path in Step 3.
Step 3: Configure the OAuth Consent Screen
Time: 5-8 minutes
This is the screen that tripped up most people. Navigate to “APIs & Services” and then “OAuth consent screen” in the left sidebar.
Google asks you to pick a User Type. Select External. (Internal is only for Google Workspace organizations, and it locks the credential to your company domain.) Click Create.
Now fill in the required fields. Google shows roughly 15 fields. You need exactly three:
- App name: type “n8n” or “n8n-gmail”
- User support email: select your Gmail address from the dropdown
- Developer contact email: type that same Gmail address
Leave every other field blank. No logo, no homepage, no privacy policy URL. Click Save and Continue.
On the Scopes screen, click Save and Continue without adding anything. You will handle scopes differently inside n8n itself.
On the Test Users screen, click “Add Users” and enter your own Gmail address. This is critical. Since your app stays in “Testing” mode (not published to the world), only test users can authenticate. Click Save and Continue, then Back to Dashboard.
You will know it worked when the OAuth consent screen summary shows your app name and your email as a test user.
Step 4: Create OAuth Client ID Credentials
Time: 3 minutes
Navigate to “APIs & Services” then “Credentials” in the left sidebar. Click “Create Credentials” at the top and choose “OAuth client ID.”
Set Application type to Web application. Name it “n8n” or whatever helps you remember.
Under “Authorized redirect URIs,” you need your n8n instance’s callback URL — but don’t guess it. Leave this field blank for now and click Create anyway. A popup appears with your Client ID and Client Secret. Copy both immediately and store them somewhere safe. You will get the exact redirect URI from n8n in the next step and come back to add it here.
You will know it worked when your new credential appears in the OAuth 2.0 Client IDs table on the Credentials page.
See the official n8n Gmail node docs if you need to troubleshoot credential configuration for your specific n8n version.
Translating Scopes: Telling Gmail What n8n is Allowed to Do
What matters here: scopes are permission slips, not code.
Get Your Free AI Tools Starter Kit
Take the 2-minute quiz to find your AI match — plus get the tools, checklist, and 50 prompts matched to your business type.
Take the Quiz →When n8n connects to Gmail, Google asks what this app is allowed to do. The answer comes in the form of scopes. A scope is a permission label — one key opens the “read email” door, another opens the “send email” door. You hand over only the keys you actually need.
Common Gmail scopes in plain English:
- Read email (
gmail.readonly): n8n can see your inbox and read messages. It cannot send, delete, or change anything. - Send email (
gmail.send): n8n can send email on your behalf. Paired with read access, this covers most automation needs. - Full access (
mail.google.com): n8n can read, send, delete, and manage labels. Use this only if your workflow needs to organize or delete messages.
Start with the narrowest scope your workflow actually requires. Watching for incoming client inquiries and forwarding a summary to Slack? Read-only is enough. Sending auto-replies? Add send permission.
You select scopes inside n8n’s credential setup (next section), not in Google Cloud. The consent screen step you did earlier intentionally skipped scopes because n8n requests them dynamically when you authenticate.
If you already have our n8n Google Sheets integration working, you went through a similar scope selection for Sheets. Gmail follows the same pattern.
Plugging It In: Your First Gmail Node in n8n
The short version: paste two strings, click authorize, and watch the green checkmark.
Step 5: Add Gmail Credentials in n8n
Time: 5 minutes
Open your self-hosted n8n instance. Create a new workflow or open an existing one. Click + to add a node and search for Gmail.
Before choosing between n8n and alternatives, you should understand Make.com’s free plan limitations before committing to any automation platform.
- Select the Gmail node. In the parameters panel, click the Credential dropdown and choose Create New Credential.
- Paste your Client ID and Client Secret from Google Cloud into the matching fields.
- n8n now displays its OAuth Redirect URI. Copy that URI exactly. Go back to Google Cloud Console, open your OAuth Client ID, paste the URI under Authorized redirect URIs, and click Save. This URI is the authoritative value, use what n8n shows you, not a manually constructed URL.
- Back in n8n, click Sign in with Google. A browser window opens asking you to pick your Google account and approve permissions. You may see a warning that says “This app isn’t verified.” That’s expected for personal-use apps. Click Advanced, then Go to n8n-gmail (unsafe). It’s your own app.
- Approve the listed scopes. The window closes. A green checkmark appears next to the credential name. You’re connected.
Troubleshooting tip: If the OAuth popup closes instantly with no checkmark, a redirect URI mismatch is the most common cause. Confirm the URI in Google Cloud Console matches exactly what n8n displayed, trailing slashes and http vs https both matter.
Step 6: Configure and Test the Gmail Node
Time: 3 minutes
With credentials saved, the Gmail node opens its full menu of operations. Here’s a practical first test:
- Set Resource to Message and Operation to Get Many.
- Leave filters at their defaults. This pulls your most recent emails.
- Click Test step. If everything is wired correctly, n8n returns a JSON list of your latest messages, subject lines, senders, timestamps.
Try a second test to confirm send permissions work:
- Change Operation to Send.
- Fill in To (your own address), Subject (“n8n test”), and Message (“If you’re reading this, the integration works.”).
- Click Test step, then check your inbox.
That round-trip, read and send, confirms your connection is fully operational.
Pro tip: Use the Gmail Trigger node when you want workflows to fire automatically on new email. Depending on your setup, the trigger checks for new messages on a defined interval or via Gmail’s notification system, either way, you don’t run the workflow manually.
The 15-Minute Setup: Your Next Five Minutes
You have the connection. Now do something with it before the tab-closing reflex wins.
- Open n8n right now and build the simplest possible workflow: Gmail Trigger, then a Set node that pulls the subject line, then a No Operation node at the end. Activate it. Send yourself a test email. Watch the execution log.
- That’s it. One trigger, one action, one proof that the pipeline works. Every complex automation you build later is just more nodes added to this same skeleton.
The Google Cloud Console feels heavy the first time. When you connect Google Calendar or Sheets next, you’ll move through it in two minutes, the project and consent screen already exist. You just create a new credential and authorize.
You’ve cleared the hardest part. Go automate something.
Before You Go — Grab Your Free AI Tools Starter Kit
Join 250+ small business owners getting smarter about AI. Take the 2-minute quiz and get your personalized toolkit.
Get Your Free Kit →Frequently Asked Questions
How much does n8n cost for a solopreneur?
n8n Cloud’s Starter plan starts at $20/mo (as of May 2026) billed annually, check n8n’s current pricing before signing up, as rates can change. It includes Gmail integrations without any Google Cloud setup. Self-hosting n8n is free with unlimited executions, but you manage your own server and handle OAuth credential setup yourself.
Does n8n work with Google Gmail for email automation?
Yes, n8n integrates directly with Gmail via its dedicated Gmail node. You can automate tasks like sorting emails into labels, sending auto-replies, and triaging support inquiries by connecting the platform using OAuth credentials you create in Google Cloud Console.
Do I need technical skills to set up n8n with Gmail?
Setting up n8n with Gmail on a self-hosted instance means navigating Google Cloud Console to create OAuth credentials, there’s a real learning curve for non-developers. The n8n Cloud plan removes that entirely with a one-click ‘Sign in with Google’ flow.
How long before I see results from automating Gmail with n8n?
You can build and deploy a basic Gmail automation workflow, like forwarding specific emails to Slack, within an hour of completing the setup. Most users report reclaiming 2-4 hours per week on email management once their initial workflows are active and tuned.
How we create this content
AIscending articles are researched using public documentation, verified user reviews, and published benchmarks, then written with AI assistance and editorially reviewed for accuracy. Some links on this site are affiliate links — we may earn a commission if you sign up, at no extra cost to you. Affiliate relationships never influence our recommendations. Read our editorial policy for details.
You Might Also Like
