Google Sheets to Gmail, leads replied and logged
Your leads are coming in. The replies aren’t. Someone has to notice the new row, write a decent first email, send it, then tell the team. And that “someone” is usually you.
This Sheets Gmail automation hits marketing managers and sales reps first, but founders feel it too. The outcome is simple: every new lead gets a fast, personalized first-touch email, while your sheet stays accurate without messy manual updates.
This workflow turns a Google Sheets row into an instant Gmail reply, a Slack heads up, and a clean “sent + labeled + timestamped” record. You’ll see how it works, what you need, and where to tweak it so it matches your brand and routing rules.
How This Automation Works
The full n8n workflow, from trigger to final output:
n8n Workflow Template: Google Sheets to Gmail, leads replied and logged
flowchart LR
subgraph sg0["Sheet Row Flow"]
direction LR
n0@{ icon: "mdi:play-circle", form: "rounded", label: "Sheet Row Trigger", pos: "b", h: 48 }
n1@{ icon: "mdi:cog", form: "rounded", label: "Pause Briefly", pos: "b", h: 48 }
n2@{ icon: "mdi:robot", form: "rounded", label: "Compose Email and Label", pos: "b", h: 48 }
n3@{ icon: "mdi:message-outline", form: "rounded", label: "Dispatch Lead Email", pos: "b", h: 48 }
n4@{ icon: "mdi:database", form: "rounded", label: "Modify Sheet Status", pos: "b", h: 48 }
n5["<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/slack.svg' width='40' height='40' /></div><br/>Alert Team Channel"]
n1 --> n2
n2 --> n3
n2 --> n4
n2 --> n5
n0 --> n1
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 n0 trigger
class n2 ai
class n4 database
classDef customIcon fill:none,stroke:none
class n5 customIcon
The Problem: New leads sit in Sheets too long
Google Sheets is a great intake layer. It’s also where leads go to die. A form submission becomes a new row, and then… nothing happens until someone checks the sheet, copies the details, writes an email, remembers the right tone, and hopes they’re not replying twice. If you wait even a couple hours, that lead is already colder. Worse, the team loses trust in the pipeline because the sheet is never fully up to date, which means follow-ups become guesswork instead of a process.
The friction compounds. Here’s where it breaks down in real life.
- Leads submitted after-hours often don’t get a reply until the next day, which quietly kills conversion.
- People “just replying quickly” results in inconsistent messaging, missing details, and more back-and-forth later.
- Manual deduping is easy to skip, so the same person can get two emails if they submit twice or use a second form.
- Status tracking becomes unreliable because nobody enjoys updating a sheet row after sending an email.
The Solution: Auto-reply from Gmail, classify leads, and log everything
This workflow watches your Google Sheet for new rows coming from any form that writes into it. When a new lead appears, it pauses briefly (to avoid partial writes), validates the key fields, and does light deduplication using email or phone so you don’t send accidental duplicates. Then it sends the lead context to OpenAI to generate a concise, brand-safe first-touch email and to label the lead as High, Medium, or Low based on criteria you define (budget, services, timeline). The email goes out immediately through your connected Gmail (or SMTP). At the same time, your team gets a Slack alert with all the essentials and a deep link to the exact sheet row. Finally, the workflow updates the row with send status, lead type, and a timestamp, so tracking stays clean without extra admin work.
The workflow starts the moment a new row shows up in Google Sheets. OpenAI drafts the email and assigns a lead label, then n8n sends the email via Gmail, posts the Slack heads up, and writes the “sent” details back into the sheet.
What You Get: Automation vs. Results
| What This Workflow Automates | Results You’ll Get |
|---|---|
|
|
Example: What This Looks Like
Say you get 15 new leads a day from two different forms that feed one Google Sheet. Manually, you might spend about 10 minutes per lead to open the row, draft a first email, send it, post a Slack note, and update the sheet, which is roughly 2.5 hours daily. With this workflow, the human time is basically zero after setup: the trigger runs every minute, OpenAI drafts the message, Gmail sends it, and Slack gets the alert automatically. You still review edge cases, but you’re no longer living in the sheet.
What You’ll Need
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Google Sheets for lead intake and tracking fields
- Gmail to send the first-touch email
- Slack to notify the team in real time
- OpenAI API key (get it from your OpenAI dashboard)
Skill level: Intermediate. You’ll connect accounts, map sheet columns, and adjust a couple of prompt rules for tone and lead classification.
Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).
How It Works
A new row appears in Google Sheets. The workflow checks your lead sheet every minute and pulls in the new submission, based on the headers you’re expecting (name, email, budget, timeline, and so on).
A short pause and validation happens. That wait is there for a reason. Some form tools write data in a beat later, so pausing avoids sending an email with missing fields, and it’s also where light dedupe logic can run using email or phone.
OpenAI writes the email and assigns a lead label. Your tone guide, one clear CTA (reply or booking link), and classifier rules shape the output so it stays on-brand. No fluffy essay, just a tight first-touch message your team would actually send.
Gmail sends, Slack gets the heads up, and Sheets is updated. The same lead context powers all three actions. The sheet row gets a send status and timestamp for reporting, and the Slack message includes a deep link back to the exact row for fast follow-up.
You can easily modify the classifier rules to match your offer, or route the Slack alert to different channels based on the lead label. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Sheet Row Trigger
Set up the Google Sheets trigger and add a short delay to ensure new rows are fully written before processing.
- Add the Sheet Row Trigger node and set Event to
rowAdded. - Set Sheet Name to
Form Responses 2and Document ID to[YOUR_ID]. - In Poll Times, choose
everyMinuteto check for new rows on a one-minute interval. - Add the Pause Briefly node and set Unit to
secondsand Amount to1.
Credential Required: Connect your Google Sheets credentials in Sheet Row Trigger.
Step 2: Connect Google Sheets
Configure the update action to write lead tags and status back to the same sheet.
- Add the Modify Sheet Status node and set Operation to
update. - Set Sheet Name to
Form Responses 2and Document ID to[YOUR_ID]. - In Columns, set Tag to
{{ $json.Tag }}and Name to{{ $('Sheet Row Trigger').item.json.Name }}. - Set Status to
{{ $('Sheet Row Trigger').item.json.Name }} was contacted by email on {{ $now.toFormat('MMMM dd, yyyy, h:mm a') }}. The team has also been notified via Slack.and set Matching Columns toName.
Credential Required: Connect your Google Sheets credentials in Modify Sheet Status.
Step 3: Set Up Compose Email and Label
Use AI to generate a personalized email, subject, and lead tag in strict JSON format.
- Add the Compose Email and Label node and set Model to
gpt-4o. - Enable JSON Output by setting it to
true. - Set Messages → Content to the full prompt in
=You are a lead nurturing assistant... Output STRICT JSON ONLY with exactly these keys: {"Subject":"...","Body":"...","Tag":"High-Value Lead|Medium-Value Lead|Low-Value Lead"} ...and keep all embedded expressions like{{ $('Sheet Row Trigger').item.json.Name }}.
Credential Required: Connect your OpenAI credentials in Compose Email and Label.
Step 4: Configure Output/Action Nodes
Send the lead email, update the sheet, and notify the team in Slack. These actions run from the AI output.
Compose Email and Label outputs to both Dispatch Lead Email, Modify Sheet Status, and Alert Team Channel in parallel.
- In Dispatch Lead Email, set Send To to
{{ $('Sheet Row Trigger').item.json['Email Address'] }}, Subject to{{ $json.Subject }}, and Message to{{ $json.Body }}. - Set Email Type to
textin Dispatch Lead Email to match the generated output. - In Alert Team Channel, set Text to
=NEW {{$json.Tag}} Alert!\nName: {{ $('Sheet Row Trigger').item.json.Name }}\nInterest: {{ $('Sheet Row Trigger').item.json['Services Interested In'] }}\nBudget: ${{ $('Sheet Row Trigger').item.json['Budget Range'] }}\nSee the Google Sheet: [YOUR_ID]. - Set Select to
channeland Channel to[YOUR_ID]in Alert Team Channel.
Credential Required: Connect your Gmail credentials in Dispatch Lead Email.
Credential Required: Connect your Slack credentials in Alert Team Channel (authentication: oAuth2).
Step 5: Test and Activate Your Workflow
Validate the full flow with a sample row, then enable the workflow for production use.
- Click Execute Workflow and add a new row to
Form Responses 2with realistic lead data. - Confirm Dispatch Lead Email sends an email with a subject starting
AI Consulting:and a personalized body. - Verify Modify Sheet Status updates the Tag and Status columns for the matching Name.
- Check that Alert Team Channel posts the lead summary message in the selected Slack channel.
- Toggle the workflow to Active to begin processing new lead submissions automatically.
Common Gotchas
- Google Sheets access often breaks due to changed permissions or a moved spreadsheet. If the trigger stops firing, check the n8n Google Sheets credential and confirm the file is still shared to the same Google account.
- If you’re using Wait nodes or external processing, timing can be the culprit. When downstream nodes fail on empty values, increase the wait duration so the row data is fully written before OpenAI runs.
- OpenAI prompts that are too generic will sound generic. Add your tone guide, approved phrases, and the one-line opt-out early, or you’ll be cleaning up every email manually.
Frequently Asked Questions
About 30 minutes if your accounts and sheet headers are ready.
No. You’ll mostly be connecting accounts and mapping Google Sheets columns into the email prompt.
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 OpenAI API costs (often just a few cents per day at low lead volume).
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.
Yes, and it’s one of the best ways to make it feel “yours.” You can edit the Compose Email and Label node to include your booking link, your required questions, and a stricter tone guide. If you want routing, add simple logic after the lead label is created so High leads alert one Slack channel while Low leads go to another. You can also change the Gmail sender or switch to SMTP if you need shared inbox behavior.
Usually it’s permissions or a changed spreadsheet. Reconnect the Google Sheets credential in n8n, confirm the spreadsheet ID hasn’t changed, and make sure the Google account still has access to that file. If it fails only sometimes, you may be hitting Google API limits or the row is being written in two passes, so the wait step needs to be a bit longer.
A lot.
Often, yes, because this flow benefits from “real” logic and clean branching. You’re doing dedupe, AI generation, labeling, multi-step updates, and two destinations (Gmail plus Slack) while writing back to Google Sheets, which is exactly where n8n feels more flexible. Self-hosting also matters if your lead volume grows and you don’t want every extra step to cost more. Zapier or Make can still be fine for a basic “new row → send email” automation, but this is a bit richer than that. If you want a second opinion before you build, Talk to an automation expert.
Once this is live, your sheet becomes a real pipeline instead of a graveyard. The workflow handles the repetitive follow-up work, so you can focus on the conversations that actually close.
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.
