Google Sheets to Gmail, CPL reports sent ready to share
Your lead data is in Google Sheets, your ad spend is somewhere else, and your “weekly CPL update” lives in a half-finished doc you keep rewriting. It’s not hard work. It’s just constant work.
Marketing managers usually get stuck stitching the story together. Agency owners feel it when client reporting day hits. And founders end up making budget decisions off numbers they frankly don’t fully trust. This CPL report automation fixes the messy middle and gives you a clean email you can forward in seconds.
Below you’ll see how the workflow turns raw lead rows into a weekly, executive-ready CPL summary (with AI-written insights), then sends it out through Gmail automatically.
How This Automation Works
The full n8n workflow, from trigger to final output:
n8n Workflow Template: Google Sheets to Gmail, CPL reports sent ready to share
flowchart LR
subgraph sg0["Schedule Flow"]
direction LR
n0@{ icon: "mdi:play-circle", form: "rounded", label: "Schedule Trigger", pos: "b", h: 48 }
n1@{ icon: "mdi:message-outline", form: "rounded", label: "Send Follow-up Email1", pos: "b", h: 48 }
n2@{ icon: "mdi:database", form: "rounded", label: "Get row(s) in sheet", pos: "b", h: 48 }
n3@{ icon: "mdi:robot", form: "rounded", label: "Basic LLM Chain", pos: "b", h: 48 }
n4@{ icon: "mdi:brain", form: "rounded", label: "Azure OpenAI Chat Model1", 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/code.svg' width='40' height='40' /></div><br/>Code"]
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/code.svg' width='40' height='40' /></div><br/>Code1"]
n5 --> n3
n6 --> n5
n3 --> n1
n0 --> n2
n2 --> n6
n4 -.-> n3
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 n3 ai
class n4 aiModel
class n2 database
class n5,n6 code
classDef customIcon fill:none,stroke:none
class n5,n6 customIcon
The Problem: CPL Reporting Turns Into Spreadsheet Archaeology
CPL reporting sounds simple until you actually do it every week. Leads show up in Sheets with inconsistent source names, ad spend lives in another export, and the “final report” ends up being a bunch of screenshots and copy-pasted totals. Then someone asks, “Why did LinkedIn CPL spike?” and you’re back in the sheet, filtering, double-checking, and realizing last week’s numbers used slightly different columns. The cost isn’t only time. It’s confidence. If the report feels fragile, you hesitate to act on it.
The friction compounds fast. Here’s where it breaks down in real life.
- Pulling new lead submissions and cleaning the data can burn about 2 hours each week, especially when sources and UTMs aren’t standardized.
- CPL math gets re-done manually, which means a small mistake quietly becomes “the truth” in the next client or leadership meeting.
- Reporting tone varies by who wrote it, so stakeholders get numbers without context or get context without clear numbers.
- Sharing is annoying because the report isn’t consistently formatted, so people copy parts into Slack, email, and docs anyway.
The Solution: Google Sheets → AI CPL Summary → Gmail Delivery
This workflow watches for new lead data, aggregates it by source/UTM, calculates CPL per channel, then turns the numbers into a polished HTML email that reads like a real weekly performance update. It starts from the system you already use (Google Sheets), normalizes the messy bits (column names and source values), and merges the results into a single dataset ready for analysis. Then an AI agent (using an OpenAI chat model, typically Azure OpenAI GPT-4o-mini) generates the written narrative: what changed, what’s working, and what to look at next. Finally, n8n sends the full report through Gmail, so the output is instantly shareable.
The workflow runs on a schedule (hourly is common) or can be triggered by events like a webhook or Gmail trigger, depending on how your leads enter the system. From there it groups performance by channel, computes CPL, and produces a clean email you can forward to clients or leadership without rewriting a thing.
What You Get: Automation vs. Results
| What This Workflow Automates | Results You’ll Get |
|---|---|
|
|
Example: What This Looks Like
Say you run weekly reporting for 6 channels (Google Ads, LinkedIn, Instagram, referral, email, and organic). Manually, you might spend about 10 minutes per channel pulling counts and checking sources (about 1 hour), then another hour writing a summary and formatting it for email. With this workflow, you spend maybe 5 minutes confirming the sheet structure once, then the hourly run does the aggregation and sends the HTML report automatically. You get roughly 2 hours back every week, and the numbers don’t drift from one report to the next.
What You’ll Need
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Google Sheets for your lead submission dataset
- Gmail to send reports to stakeholders
- Azure OpenAI API key (get it from the Azure OpenAI portal)
Skill level: Intermediate. You’ll connect accounts, map fields, and make sure your sheet columns match what the workflow expects.
Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).
How It Works
Scheduled run or event trigger. Most teams run it hourly with n8n’s scheduler so new leads get processed without anyone remembering to “pull a report.” If your setup is different, a webhook or Gmail trigger can also kick it off.
Data cleanup and grouping. The workflow fetches lead rows from Google Sheets, standardizes column names, and groups submissions by source/UTM so “LinkedIn,” “linkedin,” and “LI” don’t become three separate channels.
CPL calculation and merging. Using simple logic nodes (If, Merge, and Set/Edit Fields), it combines lead counts with spend inputs to compute CPL per channel, then prepares a single structured payload for reporting.
AI-written HTML report delivered by Gmail. An AI agent generates insights and recommendations based on your aggregated metrics, and n8n formats it into a professional HTML email sent via Gmail. It lands ready to forward.
You can easily modify the channels you group by to include campaign, ad group, or creative based on your needs. See the full implementation guide below for customization options.
Common Gotchas
- Google Sheets credentials can expire or need specific permissions. If things break, check the Google connection in n8n’s Credentials menu 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.
Frequently Asked Questions
About 30 minutes if your sheet and accounts are ready.
No. You’ll mostly connect tools and map a few fields in n8n.
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 Azure OpenAI usage costs for the AI-written report.
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, but expect a little mapping work. You can group by additional UTM fields (like campaign or ad group) by adjusting the Google Sheets field mappings and the aggregation logic (the Set/Edit Fields nodes plus the Merge/If logic). You’ll also want to update the AI prompt so the narrative references the new breakdown. Common tweaks include adding “Top campaigns,” flagging sudden CPL spikes, and including lead quality notes if you track them.
Usually it’s expired credentials or the connected Google account lost access to the spreadsheet. Reconnect the Google Sheets credential in n8n, then confirm the sheet is shared to that account. If it only fails sometimes, check for renamed tabs or changed column headers because this workflow depends on consistent field names.
A few thousand rows per run is typically fine, and if you self-host you can scale it up by giving n8n more server resources.
Often, yes. n8n is more comfortable when you need branching logic, merging datasets, and reformatting output into a real HTML report (not just “send values A, B, C”). Self-hosting is also a big deal if you run this hourly and don’t want to count every execution. Zapier or Make can still win for very simple two-step zaps, especially if you never need custom logic. If you’re on the fence, Talk to an automation expert and we’ll sanity-check your use case.
Once this is running, your weekly CPL update stops being a recurring task and becomes a reliable system. The workflow handles the repetitive parts, and you spend your time making the calls that actually move performance.
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.
