Google Sheets + Gmail: personalized outreach sent fast
Your lead list is sitting in Google Sheets, but sending truly personal outreach still turns into a slow grind. You Google. You open LinkedIn. You copy details into a draft. Then you do it again. And again.
This Sheets Gmail outreach automation hits marketing managers first, but founders doing their own sales and agency operators feel it too. You’ll go from “research + writing” to consistent, ready-to-send drafts without losing the personal touches that get replies.
Below you’ll see how the workflow enriches each lead with Apify, generates a tailored email through OpenRouter, and sends it via Gmail. Then you’ll learn what to customize so it matches your offer and tone.
How This Automation Works
Here’s the complete workflow you’ll be setting up:
n8n Workflow Template: Google Sheets + Gmail: personalized outreach sent fast
flowchart LR
subgraph sg0["When clicking ‘Execute workflow’ Flow"]
direction LR
n0@{ icon: "mdi:play-circle", form: "rounded", label: "When clicking ‘Execute workf..", pos: "b", h: 48 }
n1@{ icon: "mdi:cog", form: "rounded", label: "Aggregate", pos: "b", h: 48 }
n2@{ icon: "mdi:swap-horizontal", form: "rounded", label: "Only People Links", pos: "b", h: 48 }
n3@{ icon: "mdi:cog", form: "rounded", label: "Aggregate1", pos: "b", h: 48 }
n4["<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/httprequest.dark.svg' width='40' height='40' /></div><br/>Get LinkedIn Person"]
n5@{ icon: "mdi:swap-horizontal", form: "rounded", label: "Only Company Links", pos: "b", h: 48 }
n6@{ icon: "mdi:swap-horizontal", form: "rounded", label: "Current Company Exists?", pos: "b", h: 48 }
n7["<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/httprequest.dark.svg' width='40' height='40' /></div><br/>Google Search for Company Li.."]
n8["<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/httprequest.dark.svg' width='40' height='40' /></div><br/>Google Search for Person Lin.."]
n9["<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/httprequest.dark.svg' width='40' height='40' /></div><br/>Get LinkedIn Company"]
n10@{ icon: "mdi:database", form: "rounded", label: "Get Leads", pos: "b", h: 48 }
n11@{ icon: "mdi:swap-vertical", form: "rounded", label: "Set Company URL", pos: "b", h: 48 }
n12@{ icon: "mdi:swap-vertical", form: "rounded", label: "Set Company URL1", pos: "b", h: 48 }
n13@{ icon: "mdi:robot", form: "rounded", label: "Generate Personalized Email", pos: "b", h: 48 }
n14@{ icon: "mdi:brain", form: "rounded", label: "OpenRouter Chat Model", pos: "b", h: 48 }
n15@{ icon: "mdi:message-outline", form: "rounded", label: "Gmail", pos: "b", h: 48 }
n16@{ icon: "mdi:robot", form: "rounded", label: "Structured Output Parser", pos: "b", h: 48 }
n17@{ icon: "mdi:swap-vertical", form: "rounded", label: "Loop Over Items", pos: "b", h: 48 }
n18@{ icon: "mdi:swap-vertical", form: "rounded", label: "Set Data", pos: "b", h: 48 }
n15 --> n17
n18 --> n13
n1 --> n4
n10 --> n17
n3 --> n12
n17 --> n8
n11 --> n9
n12 --> n9
n2 --> n1
n5 --> n3
n4 --> n6
n9 --> n18
n14 -.-> n13
n6 --> n11
n6 --> n7
n16 -.-> n13
n13 --> n15
n8 --> n2
n7 --> n5
n0 --> n10
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 n13,n16 ai
class n14 aiModel
class n2,n5,n6 decision
class n10 database
class n4,n7,n8,n9 api
classDef customIcon fill:none,stroke:none
class n4,n7,n8,n9 customIcon
Why This Matters: Personalization That Doesn’t Eat Your Day
Personalized outreach works, but the manual version is honestly exhausting. One lead turns into five tabs: a quick Google search, a LinkedIn profile scan, a company page check, a notes doc, and finally Gmail. Somewhere in that mess, you misread a job title, paste the wrong company name, or forget what you wanted to say in the first place. The real cost is the context-switching. It drains focus and makes “just send 20 emails today” feel like an all-afternoon project.
The friction compounds. Here’s where it usually breaks down.
- Researching LinkedIn profiles lead-by-lead can easily burn about 10 minutes per person.
- Company context gets skipped when you’re in a rush, which makes emails sound generic.
- Copy-paste personalization creates avoidable mistakes (wrong name, wrong company, wrong role).
- Your tone drifts over time because every draft is written from scratch.
What You’ll Build: Sheets-to-Gmail Enriched Outreach
This workflow starts with a simple source of truth: your Google Sheet of leads. For each row, it runs a Google-style search through Apify to find likely LinkedIn results for the person, then follows up by fetching the best matching profile for richer details. Next, it pulls company context too. If the person’s current company is already visible on LinkedIn, the workflow uses that URL directly; if not, it does a separate company search to find the right page. Once it has both “person” and “company” context, it sends that info to an LLM via OpenRouter with a prompt built for personalized outreach. Finally, a Gmail node creates and sends the email, so you’re not manually assembling drafts all day.
The workflow begins by retrieving leads from Google Sheets and iterating through them in batches. Apify handles the searching and profile fetching, then OpenRouter generates the email text based on your prompt and company details. Gmail delivers the final message automatically, so you’re not stuck doing the repetitive parts.
What You’re Building
| What Gets Automated | What You’ll Achieve |
|---|---|
|
|
Expected Results
Say you send 25 cold emails a day from a Google Sheet. Manually, if you spend about 10 minutes finding the right LinkedIn profile and another 5 minutes writing a decent draft, that’s about 6 hours of work. With this workflow, you might spend 15 minutes updating your sheet and skimming outputs, then let the enrichment and writing run in the background. You still review what matters, but you get most of that day back.
Before You Start
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Google Sheets to store and manage lead rows.
- Gmail to send messages from your inbox.
- Apify account + token (get it from Apify Console → Settings → Integrations).
- OpenRouter API key (get it from OpenRouter dashboard).
Skill level: Intermediate. You’ll connect accounts, paste API keys, and adjust a prompt plus a few mapping fields.
Want someone to build this for you? Talk to an automation expert (free 15-minute consultation).
Step by Step
Leads come from your Google Sheet. The workflow retrieves your lead rows, then uses “split in batches” so you can process 10, 50, or more without overwhelming your connected services.
LinkedIn discovery happens automatically. For each lead, it runs a search request through Apify, filters results down to person links, and fetches the best matching LinkedIn profile for extra detail you can reference in the email.
Company context is added before writing. If the profile already includes a current company URL, the workflow uses it. If not, it searches for the company separately, then fetches the company profile so the email has something real to say.
OpenRouter generates the outreach and Gmail sends it. The “Compose Custom Email” chain uses your prompt and mapped fields, then a Gmail node sends the finished message so you’re not copying text between tools.
You can easily modify the prompt and mapped fields to match your offer, industry, and compliance needs. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Manual Trigger
This workflow starts manually so you can control outreach runs and validate lead data first.
- Add or verify the Manual Start Trigger node at the start of the workflow.
- Connect Manual Start Trigger to Retrieve Lead Sheet to follow the execution flow.
Step 2: Connect Google Sheets
Pull lead records from your spreadsheet so each row can be processed and emailed.
- Open Retrieve Lead Sheet and select your spreadsheet in Document ID.
- Set Sheet Name to your target tab (e.g., the list entry labeled
Leads Sheet). - Credential Required: Connect your googleSheetsOAuth2Api credentials.
- Ensure the output of Retrieve Lead Sheet connects to Iterate Records.
Step 3: Build the Search and LinkedIn Enrichment Pipeline
This section searches Google for LinkedIn profiles, filters results, and enriches leads with LinkedIn data.
- In Iterate Records, keep the default batch behavior to process one lead at a time.
- Configure Search Person on Google with URL set to
https://api.apify.com/v2/acts/apify~rag-web-browser/run-sync-get-dataset-itemsand the query body{{ `${$json['First Name']} ${$json['Last Name']} ${$json['Company']} site:linkedin.com` }}. - Credential Required: Connect your httpHeaderAuth credentials in Search Person on Google.
- In Filter Person Links, keep the regex condition on Left Value set to
{{ $json.searchResult.url }}with^https:\/\/www\.linkedin\.com\/in\/[a-zA-Z0-9\-_%]+\/?$. - In Collect Search Results, set Fields to Include to
searchResultand Destination Field Name toresults. - Configure Fetch LinkedIn Profile with URL
https://api.apify.com/v2/acts/apimaestro~linkedin-profile-detail/run-sync-get-dataset-itemsand Body Parameterusernameset to{{ $json.results.first().searchResult.url }}. - Credential Required: Connect your httpHeaderAuth credentials in Fetch LinkedIn Profile.
Check Company Presence splits the flow: if {{ $json.basic_info.current_company_url }} exists, it goes to Map Company URL; otherwise it goes to Search Company on Google to find a company LinkedIn URL.
- In Map Company URL, keep JSON Output set to
{ "company_url": "{{ $json.basic_info.current_company_url }}" }. - Configure Search Company on Google with URL
https://api.apify.com/v2/acts/apify~rag-web-browser/run-sync-get-dataset-itemsand query body{{ `${$json['Company']} site:linkedin.com` }}. - Credential Required: Connect your httpHeaderAuth credentials in Search Company on Google.
- In Filter Company Links, keep the regex condition on Left Value set to
{{ $json.searchResult.url }}with^https:\/\/www\.linkedin\.com\/company\/[a-zA-Z0-9\-_%]+\/?$. - In Collect Company Results, set Fields to Include to
searchResultand Destination Field Name toresults. - In Map Company URL 2, set JSON Output to
{ "company_url": "{{ $json.results.first().searchResult.url }}" }. - Configure Fetch LinkedIn Company with URL
https://api.apify.com/v2/acts/apimaestro~linkedin-company-detail/run-sync-get-dataset-itemsand Body Parameteridentifierset to{{ [$json.company_url] }}. - Credential Required: Connect your httpHeaderAuth credentials in Fetch LinkedIn Company.
Check Company Presence outputs to Map Company URL or Search Company on Google based on whether a company URL exists, then both paths converge on Fetch LinkedIn Company.
⚠️ Common Pitfall: If the regex filters are too strict, no LinkedIn URLs will pass through. Keep the provided regex patterns unchanged unless you need different LinkedIn URL formats.
Step 4: Set Up AI Email Composition
Use the AI chain to craft a personalized subject and body based on enriched LinkedIn data.
- In Assign Company Details, set your brand values: company_name to
YourCompany, email_address to[YOUR_EMAIL], company_info to your service description, and sender_name toTeam at YourCompany. - Open Compose Custom Email and keep the Text input set to
INPUT: ... {{ $('Fetch LinkedIn Profile').item.json.toJsonString() }} ... {{ $('Fetch LinkedIn Company').item.json.toJsonString() }}. - Verify the AI prompt in Compose Custom Email includes your company context and the expected JSON output format with
subjectandbody. - Structured Result Parser is connected as the output parser for Compose Custom Email—add credentials to the parent node only if your AI service requires it (none are required on the parser itself).
- Credential Required: Connect your openRouterApi credentials in OpenRouter Chat Engine (this is the language model powering Compose Custom Email).
Step 5: Configure Gmail Delivery
Send the AI-generated email to each lead from the sheet.
- In Send Email via Gmail, set Send To to
{{ $('Retrieve Lead Sheet').item.json.Email }}. - Set Subject to
{{ $json.output.subject }}and Message to{{ $json.output.body }}. - Set Reply To to
{{ $('Assign Company Details').item.json.email_address }}and Sender Name to{{ $('Assign Company Details').item.json.sender_name }}. - Credential Required: Connect your gmailOAuth2 credentials in Send Email via Gmail.
- Ensure Compose Custom Email connects to Send Email via Gmail, and Send Email via Gmail connects back to Iterate Records to continue batching.
⚠️ Common Pitfall: If Email is missing from the Google Sheet, Send Email via Gmail will fail. Confirm your sheet has an Email column with valid addresses.
Step 6: Test and Activate Your Workflow
Run a full manual test with a small batch before enabling production outreach.
- Click Execute Workflow from Manual Start Trigger to run the full pipeline.
- Confirm that Retrieve Lead Sheet outputs rows and Iterate Records starts the batch loop.
- Verify that Compose Custom Email produces
output.subjectandoutput.bodyin the expected JSON format. - Check your inbox to confirm Send Email via Gmail sends a formatted email to the lead.
- Once validated, switch the workflow to Active for production use.
Troubleshooting Tips
- Google Sheets credentials can expire or lack access to the right spreadsheet. If leads don’t load, check the n8n credential, then confirm the sheet is shared with that Google account.
- If you’re using Wait nodes or external enrichment, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
- OpenRouter prompts ship generic by default, and generic emails get ignored. Add your positioning and examples in the “Compose Custom Email” prompt so the output actually sounds like you.
Quick Answers
About 45 minutes if your accounts and keys are ready.
No. You’ll connect services, map a few fields, and tweak 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 Apify usage plus OpenRouter model costs (usually a few cents per email, depending on the model and prompt length).
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 you probably should. Most people start by updating the “Set My Data” node (your company, offer, and positioning), then adjusting the “Compose Custom Email / Generate Personalized Email” prompt. You can also swap the sending step: keep Gmail for 1:1 outreach, or route the generated copy into a review step before sending. If your leads are already enriched, you can skip parts of the Apify lookup and generate emails straight from the sheet.
Usually it’s the wrong Google account or the sheet isn’t shared with the account tied to your n8n credential. Reconnect Google Sheets in n8n, then double-check the spreadsheet ID and tab name in the “Retrieve Lead Sheet” node. If it still fails, look for Google security prompts (some workspaces require admin approval) and confirm you didn’t hit quota limits by pulling huge ranges repeatedly.
It depends on your n8n plan and how aggressive your batching is. On n8n Cloud Starter, many teams comfortably run a few thousand executions per month; self-hosting removes execution caps and shifts the limit to your server. Practically, Apify and Gmail become the bottlenecks, so start with small batches (like 10–25 leads), confirm quality, then scale up gradually. If you send too fast, Gmail can throttle you.
Often, yes, because this workflow isn’t just “move data.” You’re doing multi-step enrichment, filtering, branching (like the company URL check), and structured AI output parsing, which tends to get messy and expensive on simpler automation tools. n8n also gives you more control over batching, retries, and how you handle partial failures, which matters when one bad LinkedIn lookup shouldn’t stop the whole run. Zapier or Make can still work if you only want a lightweight version, like “Sheet row → AI draft → Gmail draft.” But for end-to-end enrichment plus sending, n8n is usually the calmer option. If you want a second opinion before you build, Talk to an automation expert.
Once this is running, outreach stops being a daily research project. You’ll still steer the message, but the workflow handles the repetitive digging and drafting so you can focus on replies and real conversations.
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.
