Google Sheets + Gmail: CRM follow ups that run
Your “CRM” is probably a Google Sheet that’s doing way too much. Someone changes a lead stage, someone else forgets to follow up, and now you’re digging through old threads trying to remember what you promised and when.
This is where Sheets Gmail CRM automation earns its keep. Sales ops people feel it first, but agency owners and marketing managers running lead pipelines in spreadsheets live in the same chaos. You get consistent follow-ups, cleaner client records, and delivery time tracking without buying a heavyweight CRM.
This workflow turns simple sheet edits into actions. You’ll see what triggers it, what it updates, what it emails, and how it keeps your pipeline honest.
How This Automation Works
See how this solves the problem:
n8n Workflow Template: Google Sheets + Gmail: CRM follow ups that run
flowchart LR
subgraph sg0["Flow 1"]
direction LR
n0["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/webhook.dark.svg' width='40' height='40' /></div><br/>Webhook: Lead Stage Changed"]
n1@{ icon: "mdi:swap-vertical", form: "rounded", label: "Prepare Email Fields", pos: "b", h: 48 }
n2@{ icon: "mdi:message-outline", form: "rounded", label: "Gmail: Send Stage-Change Email", pos: "b", h: 48 }
n3@{ icon: "mdi:swap-horizontal", form: "rounded", label: "IF: Stage == Won", pos: "b", h: 48 }
n4@{ icon: "mdi:cog", form: "rounded", label: "Format Start Timestamp", pos: "b", h: 48 }
n5@{ icon: "mdi:database", form: "rounded", label: "GS: Clients Append (On Won)", pos: "b", h: 48 }
n16@{ icon: "mdi:swap-horizontal", form: "rounded", label: "If", pos: "b", h: 48 }
n16 --> n2
n16 --> n3
n3 --> n4
n1 --> n16
n4 --> n5
n0 --> n1
end
subgraph sg1["Flow 2"]
direction LR
n10["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/webhook.dark.svg' width='40' height='40' /></div><br/>Webhook: Client Status Changed"]
n11@{ icon: "mdi:swap-horizontal", form: "rounded", label: "IF: Delivered?", pos: "b", h: 48 }
n12@{ icon: "mdi:database", form: "rounded", label: "GS: Clients Lookup by Email", pos: "b", h: 48 }
n13@{ icon: "mdi:cog", form: "rounded", label: "Format End Timestamp", pos: "b", h: 48 }
n14@{ icon: "mdi:database", form: "rounded", label: "GS: Clients Update End & Dur..", pos: "b", h: 48 }
n15["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/code.svg' width='40' height='40' /></div><br/>Code"]
n15 --> n14
n11 --> n12
n13 --> n15
n12 --> n13
n10 --> n11
end
subgraph sg2["Flow 3"]
direction LR
n6["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/webhook.dark.svg' width='40' height='40' /></div><br/>Webhook: Lead Qualified?"]
n7@{ icon: "mdi:swap-horizontal", form: "rounded", label: "IF: Is Qualified", pos: "b", h: 48 }
n8@{ icon: "mdi:message-outline", form: "rounded", label: "Gmail: Send Cal.com Invite", pos: "b", h: 48 }
n7 --> n8
n6 --> n7
end
subgraph sg3["Flow 4"]
direction LR
n9@{ icon: "mdi:database", form: "rounded", label: "GS: Leads Update Stage to Me..", pos: "b", h: 48 }
n17["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/webhook.dark.svg' width='40' height='40' /></div><br/>Webhook: Meeting Booked"]
n17 --> n9
end
%% Styling
classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
classDef disabled stroke-dasharray: 5 5,opacity: 0.5
class n3,n16,n11,n7 decision
class n5,n12,n14,n9 database
class n0,n10,n6,n17 api
class n15 code
classDef customIcon fill:none,stroke:none
class n0,n10,n15,n6,n17 customIcon
The Challenge: Spreadsheet CRMs Fall Apart in Follow-Up
A Google Sheet is great at storing lead info. It’s terrible at making sure the next step actually happens. The moment your pipeline depends on “someone remembering,” you get gaps: no proposal heads-up, no booking link, no clean handoff when a deal is won. Then the “Clients” tab becomes a graveyard of half-filled rows, missing dates, and delivery timelines that nobody trusts. And honestly, it’s the mental load that stings most. You’re running the business while also trying to be the workflow engine.
It adds up fast. Here’s where it breaks down in real life.
- Stage changes happen in the sheet, but the follow-up email never gets sent because it wasn’t tied to the change.
- Won deals don’t get copied into a separate “Clients” tracker, so delivery status lives in random places.
- Start and end timestamps are missing or inconsistent, which makes “time to deliver” more like a guess.
- Even when someone does everything right, it still takes constant checking and nudging to keep the pipeline moving.
The Fix: Turn Sheet Edits Into Automatic Follow Ups
This n8n workflow watches your Google Sheet like a lightweight CRM assistant. When someone edits a lead’s stage or marks them as qualified, a small Google Apps Script sends that change to n8n instantly via webhook. n8n then decides what to do based on the exact update: send the right Gmail follow-up, append a won lead into a proper Clients tab, or stamp end dates when a project is delivered. It also calculates “Time to Deliver” so you stop doing date math in your head. The end result is a pipeline that moves forward because actions happen as soon as the sheet changes, not when you remember later.
The workflow begins when your sheet is edited and the Apps Script posts JSON to n8n. From there, n8n branches based on the field that changed (Qualified, Stage, Project Status). Finally, Gmail and Google Sheets updates happen automatically so your Leads and Clients tabs stay in sync.
What Changes: Before vs. After
| What This Eliminates | Impact You’ll See |
|---|---|
|
|
Real-World Impact
Say you handle 20 active leads a week and you usually do 3 manual steps when they move stages: send an email (about 5 minutes), update another tab (about 3 minutes), and add timestamps (about 2 minutes). That’s roughly 10 minutes per lead update, which turns into about 3 hours of fiddly work weekly. With this workflow, the “work” is changing a cell in Google Sheets, then waiting for the email and updates to complete in the background. You still decide the stage, but you stop doing the admin.
Requirements
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Google Sheets to store Leads and Clients tabs
- Gmail to send follow-up emails automatically
- Google Apps Script access (Extensions → Apps Script in Sheets)
Skill level: Intermediate. You’ll paste an Apps Script, connect Google credentials in n8n, and replace a few placeholders.
Need help implementing this? Talk to an automation expert (free 15-minute consultation).
The Workflow Flow
A sheet edit triggers the automation. A small Google Apps Script listens for edits in your Leads or Clients tabs and posts the changed row data to the right n8n webhook.
n8n checks what changed and routes it. If the update is “Qualified? = true,” it goes down the qualification branch. If it’s a stage change, n8n checks for “Awaiting Proposal” or “Won.” If it’s a client status change, it checks for “Delivered.”
Emails and timestamps happen automatically. Gmail sends your booking email (with your Cal.com link) or a proposal heads-up message. When a lead becomes “Won,” n8n formats the start time and appends a new row to the Clients tab so fulfillment starts with a clean record.
Delivery duration gets calculated and written back. When a project status becomes Delivered, the workflow looks up the client row by email, stamps an end time, computes the time-to-deliver, and updates the sheet.
You can easily modify Gmail copy to match your voice, or switch the notification step to Slack based on your needs. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Webhook Trigger
This workflow uses three webhook entry points for different CRM events. Set each webhook path and method exactly as shown so your external systems can call them.
- Add the Incoming Lead Stage Hook node and set HTTP Method to
POSTwith Path set tolead-stage-changed. - Add the Lead Qualified Webhook node and set HTTP Method to
POSTwith Path set tolead-qualified. - Add the Meeting Booked Webhook node and set HTTP Method to
POSTwith Path set tocal-booked. - Add the Client Status Webhook node and set HTTP Method to
POSTwith Path set toclient-status-changed.
Step 2: Connect Google Sheets
Several nodes read and write to your CRM spreadsheet for leads and clients. Connect Google Sheets once and configure each node to the correct document and sheet.
- Open Append Won Client Row and select the spreadsheet in Document using
{{GOOGLE_SHEETS_DOC_ID}}, then set Sheet to{{CLIENTS_GID}}and keep Operation asappend. - Set the Append Won Client Row column mappings: Name →
{{ $json.body.name }}, Client Email →{{ $json.body.email }}, Start Date & Time →{{ $json.data }}. - Open Lookup Client by Email and set the filter Client Email to
{{ $json.body.email }}, with Document{{GOOGLE_SHEETS_DOC_ID}}and Sheet{{CLIENTS_GID}}. - Open Update Lead to Meeting Booked, set Operation to
update, Document to{{GOOGLE_SHEETS_DOC_ID}}, Sheet togid={{LEADS_GID}}, and match on Client Email. - Map Update Lead to Meeting Booked values: Stage →
Meeting Booked, Client Email →{{ $json.body.payload.attendees[0].email }}. - Open Update Client End Duration and set Operation to
update, with Document{{GOOGLE_SHEETS_DOC_ID}}and Sheet{{CLIENTS_GID}}, matching on Client Email. - Map Update Client End Duration values: Client Email →
{{ $json["Client Email"] }}, End Date & Time →{{ $json.endStr }}, Time to Deliver →{{ $json.duration }}. - Credential Required: Connect your googleSheetsOAuth2Api credentials to Append Won Client Row, Lookup Client by Email, Update Lead to Meeting Booked, and Update Client End Duration.
Step 3: Set Up Lead Stage Processing
This branch handles stage-change notifications, sends proposal emails, and appends “Won” clients to the spreadsheet.
- In Assemble Email Fields, add fields with these expressions: firstName →
{{ $json.body.name ? $json.body.name.trim().split(' ')[0] : 'there' }}, sourcePlatform →{{ $json.body.source_text || 'Unknown' }}, stage →{{ $json.body.stage }}, previousStage →{{ $json.body.previous_stage || '' }}. - In Check Awaiting Proposal, set the condition to compare Left Value
{{ $json.stage }}equalsAwaiting Proposal. - Configure Gmail Send Stage Update with Send To
{{ $('Assemble Email Fields').item.json.body.email }}, SubjectNext Steps, and the provided HTML in Message. - In Check Stage Won, set the condition Left Value
{{ $json.stage }}equalsWon. - Configure Format Start Time with Value
{{ $now }}and To FormatDD/MM/YYYY 'at' HH:mm. - Credential Required: Connect your gmailOAuth2 credentials to Gmail Send Stage Update.
Step 4: Configure Lead Qualification Emailing
Qualified leads receive an invitation email to book a discovery call.
- In Verify Qualification, set the condition to check Left Value
{{ $json.body.qualified }}istrue. - Configure Send Cal Invite Email with Send To
{{ $json.body.email }}, SubjectBook Your Discovery Call, and the provided HTML in Message. - Credential Required: Connect your gmailOAuth2 credentials to Send Cal Invite Email.
Step 5: Track Client Delivery Status and Duration
This branch updates the client’s end date and delivery duration once the project is marked as delivered.
- In Check Delivered Status, set the condition Left Value
{{ $json.body.project_status }}equalsDelivered. - Configure Format End Time with Value
{{ $now }}and To FormatDD/MM/YYYY 'at' HH:mm. - Keep Compute Delivery Duration as-is, ensuring it runs after Lookup Client by Email and Format End Time to compute
endStrandduration. - Confirm Compute Delivery Duration outputs to Update Client End Duration to write the computed values back to the spreadsheet.
DD/MM/YYYY at HH:mm. If your sheet uses a different format, adjust the parser in Compute Delivery Duration.Step 6: Test and Activate Your Workflow
Run manual tests for each webhook path to confirm emails and spreadsheet updates occur as expected.
- Use the Test button on Incoming Lead Stage Hook, send a sample payload, and confirm Gmail Send Stage Update sends an email when
stageisAwaiting Proposal. - Trigger Lead Qualified Webhook with
qualified: trueand verify Send Cal Invite Email sends the booking invite. - Trigger Meeting Booked Webhook and confirm Update Lead to Meeting Booked updates the Stage in your Leads sheet.
- Trigger Client Status Webhook with
project_status: Deliveredand verify Update Client End Duration updates End Date & Time and Time to Deliver. - When all tests pass, toggle the workflow to Active to enable production automation.
Watch Out For
- Google Sheets credentials can expire or need specific permissions. If things break, check the n8n credential status and re-authorize the Google account first.
- If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
- Default prompts in AI nodes are generic. Add your brand voice early or you’ll be editing outputs forever.
Common Questions
About an hour if your Google Sheet is already set up.
Yes, but you will need someone comfortable pasting a Google Apps Script. No “real coding,” yet you do have to connect Google credentials and replace webhook URLs.
Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in Google Workspace limits if your account is heavily restricted.
Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.
You can swap Gmail for Slack by replacing the “Gmail Send Stage Update” and “Send Cal Invite Email” nodes with Slack message nodes. Common tweaks include adding a “Stage = Lost” branch in the stage-check logic, changing the email copy in the “Assemble Email Fields” step, and adding a duplicate-check before “Append Won Client Row” so you don’t create two client records for the same email.
Usually it’s an expired OAuth authorization in n8n. Reconnect your Google Sheets credential, then confirm the workflow is pointing at the correct document ID and tab GIDs, because the wrong gid can look like a “connection” issue when it’s really a target mismatch.
For most small teams, it’s effectively “as many sheet edits as you make.” On n8n Cloud Starter you can run thousands of executions per month, and each stage change or qualification can be one execution. If you self-host, there’s no execution cap, but Google Sheets and Gmail still have API quotas, so bursts of edits can get throttled. If you expect lots of updates at once (importing hundreds of rows), run it in batches and test during low-traffic hours. Day-to-day pipeline updates are usually fine.
Often, yes. This setup relies on branching logic (Qualified vs Awaiting Proposal vs Won vs Delivered), and n8n handles that without turning every “if” into another paid step. You also get the option to self-host, which matters when your pipeline grows and you don’t want pricing surprises. Zapier and Make can still be simpler if you only need one trigger and one email. If you’re unsure, Talk to an automation expert and we’ll help you pick the right approach.
Your sheet stays simple, but it starts behaving like a real system. Set this up once, then let follow-ups, client logging, and delivery tracking run in the background.
Need Help Setting This Up?
Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.
