How to Build an n8n Gmail + Google Sheets Lead Tracker
(That Updates Itself)
If your leads are still living inside Gmail threads and your spreadsheet gets updated whenever you "have a sec," you do not have a lead system. You have vibes. Here's the n8n Gmail automation I use to kill that problem.
What's in this guide
Gmail is not a CRM. Every day you use it as one, leads disappear.
Most businesses don't have a lead tracking problem because their software is bad. They have a lead tracking problem because Gmail is where good intentions go to die.
A lead comes in. You read it on your phone. You tell yourself you'll log it later. Then another message hits, then a client thread, then some random platform alert, and you forget. By the time you remember, that promising email is buried under forty newer ones and your spreadsheet is missing half the story.
That is how leads get lost. Not in some dramatic enterprise-system collapse. Just in normal, stupid, everyday inbox chaos.
If your lead process depends on you manually copy-pasting names and emails into a sheet after reading Gmail, your process is already lying to you.
So I built a simple n8n Gmail automation that watches for qualifying emails, pulls out the useful details, and appends a clean row to Google Sheets automatically. No babysitting. No fake "I'll update CRM later" optimism. The row just shows up.
This workflow exists because I got tired of inboxes pretending to be systems. A spreadsheet isn't perfect either, but at least it doesn't bury things under new email.
What this workflow does (boring to describe, useful to run)
In plain English, this workflow sits between Gmail and Google Sheets and acts like the adult in the room.
- Gmail Trigger watches for emails that match your lead filter
- Parse step extracts sender name, sender email, subject, date, and a short body snippet
- Google Sheets appends that data as a new row in your lead tracker tab
- Optional alert sends you a Telegram notification when a new lead lands
That's it. Nothing fancy. But that boring little pipe is enough to make sure inbound leads stop vanishing into Gmail threads you swear you'll organize someday.
The real value is not that Google Sheets is some perfect lead database. It isn't. The value is that Sheets gives you one visible place where every inquiry lands in the same format. That means you can sort by date, scan follow-up gaps, hand the list to somebody else, or move it into a bigger system later without first doing inbox archaeology.
If you're also trying to clean up the rest of your inbox mess, my n8n email triage bot guide is the companion piece to this. One workflow catches leads. The other stops your inbox from becoming psychic damage.
What you need before you start (and the one decision to make first)
You do not need a massive stack for this, but you do need the basics wired up correctly before you start clicking around like a maniac.
I would also decide one thing up front: what exactly counts as a lead in your business? A contact form? A reply to your pricing email? A marketplace message forwarded into Gmail? If you skip that definition, the workflow becomes a random-email logger instead of a lead tracker, which is a fantastic way to build extra admin work and then blame the automation.
- An n8n instance, cloud or self-hosted
- A Gmail account connected to n8n with OAuth
- A Google Sheets account connected to n8n with OAuth
- A sheet with headers already created, like
Name,Email,Subject,Date, andSnippet - Basic n8n familiarity, because this is not a zero-to-one beginner walkthrough
Small but important tip: create the Google Sheet tab first and get the column names right before mapping anything. If your headers are sloppy, n8n will happily turn a five-minute workflow into a "why the hell is this blank" afternoon.
Build the workflow in 5 steps (keep the shape clean)
The whole point of this n8n Gmail Google Sheets setup is that it should be simple enough to trust. So keep the shape clean:
Gmail Trigger → Set / Code → Google Sheets Append Row → Optional Telegram → TestGmail Trigger node and connect your Gmail credential. Then decide what counts as a lead. That part matters more than the node itself.My favorite setup is using a Gmail filter that auto-applies a label like
Leads the second a qualifying message arrives. Then the trigger watches that label. Clean, predictable, hard to screw up.You can also filter by subject keywords, sender domains, or whatever pattern fits your business. If you get a lot of contact-form emails, you might watch for a subject fragment like
New inquiry. If leads always come from a marketplace or partner, filter by sender domain.The point is to make Gmail do part of the sorting before n8n ever wakes up. Let the inbox do some work for once.
If you share an inbox with a VA, partner, or salesperson, labels become even more useful because they give everyone the same intake rule. Without that, one person's "definitely a lead" is another person's "eh, maybe later," and then you're back to losing deals in the cracks.
Set node or Code node to pull out only the useful fields. Usually that means from.name, from.email, subject, date, and snippet.Keep this part boring. You are not writing a thesis on MIME payloads. You are trying to move clean lead data into a sheet.
If your Gmail node output looks different from screenshots you've seen, you're not crazy. n8n has changed field shapes across versions, and the Gmail node is one of those places where a tutorial from last year can quietly waste your time. Inspect the real JSON output from your version and map from that, not from some dusty blog post.
Also: strip reply prefixes from subjects if you can. Nobody needs a spreadsheet full of
Re: Re: Re: Quick question like it's 2009.
Google Sheets node and use the Append Row operation. Point it at the right spreadsheet and the right tab, then map each parsed field to the matching column.This is where most people create their own pain by getting lazy with headers. If the sheet columns are named one thing and your mapping expects another, n8n will not magically read your mind. Make the sheet and the node agree on reality.
A simple column set works fine:
NameEmailSubjectDateSnippet
You can absolutely add source, pipeline stage, assigned owner, or anything else later. First get the row writing cleanly. Fancy is how people end up debugging basic shit at midnight.
One extra field I do like adding early is
Status, defaulted to something like New. It seems tiny, but it gives you a dead-simple way to scan which leads still need action without turning the sheet into a weird manual CRM cosplay project.
Telegram node and send yourself a quick alert with the sender, subject, and maybe the snippet.I like this because it keeps me aware of new leads without making me stare at the spreadsheet all day like a deranged hall monitor. And yes, this is basically the same "missed-lead alert" idea I include in the See Google Workspace MCP → because it solves a painfully common problem with almost no complexity.
If Telegram isn't your thing, swap it for Slack, Discord, or whatever you already check. The alert channel matters less than the fact that you're no longer relying on memory and vibes.
Check the sender name. Check the sender email. Check the timestamp. Check the snippet. Then check the timestamp again, because timezone issues are one of those dumb little bugs that make you distrust the whole workflow for reasons that feel supernatural but are actually just UTC being annoying.
If you added the Telegram branch, make sure the alert fires once and only once. A lead notification is useful. Three duplicate lead notifications make you want to throw your phone into a lake.
Want this without rebuilding every node by hand?
If you just wanted the workflow working today, not a charming evening spent mapping fields and swearing at OAuth, the prebuilt version lives in my n8n Starter Pack with 13 other workflows I actually use.
See Google Workspace MCP →Three places this breaks (and none of them are the interesting part of the problem)
This workflow is simple, but simple does not mean magical. It still breaks in very normal, very annoying ways.
Gmail triggers are not always instant
Depending on how your n8n setup is handling Gmail, you may be polling on an interval rather than getting some lightning-fast real-time push. That means a lead can land and show up a few minutes later. Usually fine. Just don't promise yourself "instant" if your setup isn't actually instant.
OAuth expires because of course it does
If the workflow suddenly stops pulling or writing, check the credentials first. Gmail and Google Sheets reconnects are not a moral failure. They're just maintenance. Boring, recurring, deeply unsexy maintenance.
Duplicate rows happen
If the trigger fires twice or Gmail decides to be weird, you can end up with duplicate lead rows. If your volume is low, who cares. Delete the duplicate and move on. If volume is higher, add a dedup check using message ID or thread ID before appending.
Column mismatches will waste your time
If your sheet headers don't match what you're mapping, the append step turns into nonsense fast. Name the columns clearly. Keep them stable. Do not "tidy them up later" unless you also plan to update the workflow and remember to do it before something breaks in production.
The honest version: this stuff usually breaks at the edges, not in the middle. The core logic is fine. It's credentials, headers, duplicate handling, and timezone crap that gets you. Fix those first before assuming n8n itself is haunted.
If you want the prebuilt version, here it is
If you built this manually, you now have a working n8n Gmail automation that logs leads to Google Sheets without you doing the copy-paste dance every day. That is a real improvement over what you had before.
If your real goal was not "become emotionally intimate with one more workflow editor," the easier move is to grab the pack. The See Google Workspace MCP → includes this missed-lead workflow, inbox systems, and a bunch of other automations built for people who run actual businesses and do not want their process held together by memory and optimism.
It's $97, instant download, backed by a 30-day guarantee. Either you want the shortcut or you don't.
A spreadsheet is not the end state here. It's the intake layer. Plenty of bigger systems start with a sheet because a sheet is visible, cheap, and brutally honest about what's actually in your pipeline. You can graduate later. What you cannot do is keep treating unread Gmail threads as a sales system. They are not a system. They are a pile of good intentions sorted by most recent.