Weekend n8n Build: Gmail to Notion CRM Auto-Logger for Inbound Leads

Inbound leads land in a shared inbox and die there. Someone means to log them in the CRM, then a fire starts and the email scrolls away. We built an n8n flow for a 14-person Pune SaaS reseller that catches any email labelled "Lead", parses the sender, checks it isn't already in Notion, and writes a clean CRM row with an assigned owner — in under 8 seconds, with zero human touch. Around 12 nodes, self-hosted on a small Hetzner box. Here's the full build you can copy this weekend.

How do you auto-log Gmail leads into a Notion CRM?

Use an n8n Gmail Trigger watching a single label like "Lead". When an email arrives, parse the sender's name, email, and domain, then query your Notion database to check the email doesn't already exist. If it's new, create a Notion page with the lead's details and a round-robin owner; if it exists, log a note instead. The whole flow is about 12 nodes and runs in under 10 seconds per lead.

Why this matters now (May 2026)

Shared inboxes don't scale past two salespeople. The official n8n Gmail-and-Notion integration makes this trivial to wire up, and self-hosting n8n means unlimited executions for the price of a small VPS — no per-task Zapier bill. For a small Indian sales team, the alternative is a paid monthly connector or a CRM seat for an "ops" person who copy-pastes emails. With n8n's free, self-hostable core, you own the whole pipeline. We covered the broader pattern in our roundup of the 9 n8n workflows we ran most in 2025 — this is the cleanest entry point.

The deeper reason to fix lead intake first is that it's the cheapest stage to lose money at. A lead that never gets logged costs you the entire acquisition spend that brought it in — the ad click, the SEO work, the referral — for zero return. Every other CRM improvement (better follow-up cadence, sharper qualification) only matters for leads that made it into the system. Plug the intake leak and every downstream effort gets more leads to work with. That's why we build this flow before any fancier automation: it's the foundation the rest sits on.

It also removes a quiet source of team friction. When leads live in a shared inbox, "who was supposed to call this person?" has no answer, so nobody owns the miss and everybody feels vaguely guilty. Round-robin assignment at the moment of capture turns a fuzzy collective duty into a named individual task. The CRM stops being a graveyard people distrust and becomes the one place a rep checks first thing in the morning.

What you'll need before you start

Gather these first. The whole build assumes self-hosted n8n, but n8n Cloud works identically for the node logic.

The build, node by node

This is the full flow. Around 12 nodes including the branch. Each step has a verification so you can test as you go rather than debugging the whole chain at the end.

The 4 mistakes that break this flow

We've debugged each of these in production. They all look like "n8n is broken" and are all configuration.

Self-hosted vs Cloud: what running this actually costs

Three honest options, compared on monthly cost for a small team processing a few thousand leads a month.

Real example: where this saved a real team

The 14-person Pune SaaS reseller was logging maybe 60% of inbound leads — the rest scrolled away in a shared inbox. After this flow went live, logging hit 100% and first-response time dropped from "whenever someone notices" to under 10 minutes, because the owner gets pinged instantly. As Hrishikesh, our CTO, frames it: the value isn't the automation, it's that a lead can no longer fall through a crack.

The number that convinced their founder wasn't response time — it was that the team finally trusted the CRM. Before the flow, reps kept a private list of "real" leads in their own notes because the shared system was unreliable, which meant management had no honest pipeline view. Once every lead landed automatically with an owner attached, the side-lists disappeared and the CRM became the single source of truth. That second-order effect — accurate forecasting — turned out to matter more to the founder than the leads the bot caught directly. We've run the same dedupe-and-route pattern at larger scale building Radiant Finance's lead pipeline, where missing a single inbound enquiry had a real rupee cost. If you'd rather start with sales-call prep instead of intake, our n8n + HubSpot auto-brief workflow pairs naturally with this one. The whole thing is what our AI and automation team ships as a starter engagement.

Frequently asked questions

Do I need to self-host n8n for this lead-logger?

No. The node logic is identical on n8n Cloud and self-hosted. Self-hosting on a small Hetzner box gives you unlimited executions and full data control; n8n Cloud Starter is faster to start if you don't want to manage a server.

How does the dedupe step actually work?

Before creating a row, an n8n Notion node queries your database filtering where the Email property equals the incoming sender. An IF node then branches: zero matches means a new lead gets created, any match means a note is appended to the existing page instead of a duplicate row.

Can I use this with Airtable or Google Sheets instead of Notion?

Yes. Swap the Notion nodes for Airtable or Google Sheets nodes — the Gmail Trigger, parsing, dedupe-query, and IF logic stay the same. Notion is just a popular lightweight CRM for small teams; the pattern is storage-agnostic.

Will every reply from a lead create a new entry?

Not if you include the dedupe check. The Notion query plus IF branch ensures a known email appends a note to the existing page rather than creating a second row. Skipping that branch is the most common reason teams end up with duplicate CRM entries.

How do I assign leads to different salespeople automatically?

Use a round-robin counter: a small Code or Set node that increments a stored value and uses modulo to pick the next rep from a list. You can also branch on the parsed company domain or lead source to route enterprise leads to a senior rep.

How long does this take to build the first time?

A weekend for someone new to n8n — most of the time goes into the Gmail and Notion credential setup, not the nodes. Once you've done it once, rebuilding a variant takes under two hours.