Google Trends to Gmail, clean summaries sent fast
Pulling insights out of Google Trends sounds simple until you’re staring at messy pages, half-structured snippets, and notes scattered across docs and tabs. Then you still have to rewrite it into something your team will actually read. Every week.
SEO analysts feel this when keyword interest shifts overnight. A content strategist needs clean takeaways for next week’s plan. And if you run an agency, Trends Gmail automation is the difference between “we’ll send it later” and consistent updates that make you look sharp.
This workflow turns a Google Trends page into a clear AI summary, then emails it through Gmail and pushes it to a webhook. You’ll see what it does, what you need, and how to adapt it for your own reporting.
How This Automation Works
The full n8n workflow, from trigger to final output:
n8n Workflow Template: Google Trends to Gmail, clean summaries sent fast
flowchart LR
subgraph sg0["When clicking ‘Test workflow’ Flow"]
direction LR
n0@{ icon: "mdi:play-circle", form: "rounded", label: "When clicking ‘Test workflow’", pos: "b", h: 48 }
n1@{ icon: "mdi:robot", form: "rounded", label: "Markdown to Textual Data Ext..", pos: "b", h: 48 }
n2@{ icon: "mdi:swap-vertical", form: "rounded", label: "Set URL and Bright Data Zone", pos: "b", h: 48 }
n3["<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/>Initiate a Webhook Notificat.."]
n4@{ icon: "mdi:brain", form: "rounded", label: "Google Gemini Chat Model for..", 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/httprequest.dark.svg' width='40' height='40' /></div><br/>Perform Bright Data Web Requ.."]
n6@{ icon: "mdi:code-braces", form: "rounded", label: "Create a binary data", pos: "b", h: 48 }
n7@{ icon: "mdi:robot", form: "rounded", label: "Structured Data Extractor", pos: "b", h: 48 }
n8@{ icon: "mdi:robot", form: "rounded", label: "Summarize Google Trends", pos: "b", h: 48 }
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/>Initiate a Webhook Notificat.."]
n10@{ icon: "mdi:cog", form: "rounded", label: "Write the file to disk", pos: "b", h: 48 }
n11@{ icon: "mdi:brain", form: "rounded", label: "Google Gemini Chat Model for..", pos: "b", h: 48 }
n12@{ icon: "mdi:brain", form: "rounded", label: "Google Gemini Chat Model for..", pos: "b", h: 48 }
n13@{ icon: "mdi:message-outline", form: "rounded", label: "Send Summary to Gmail", pos: "b", h: 48 }
n6 --> n10
n8 --> n9
n8 --> n13
n7 --> n6
n7 --> n8
n2 --> n5
n5 --> n1
n0 --> n2
n1 --> n3
n1 --> n7
n4 -.-> n1
n11 -.-> n8
n12 -.-> n7
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 n1,n7,n8 ai
class n4,n11,n12 aiModel
class n3,n5,n9 api
class n6 code
classDef customIcon fill:none,stroke:none
class n3,n5,n9 customIcon
The Problem: Google Trends insights are a weekly time sink
Google Trends is great at showing movement, but it’s not built to hand you a decision-ready summary. You copy sections into a doc, reformat weird chunks, try to explain what matters, then send an email that still feels a little fuzzy. Do that for a few topics or regions and you’ve burned most of a morning. The worst part is the mental load: you’re doing low-value cleaning work while the actual opportunity (new content angles, quick reactions, budget shifts) is getting colder by the hour.
It adds up fast. Here’s where it breaks down.
- You spend about 30–60 minutes per report just turning messy page content into readable text.
- Manual summaries drift in style and quality, so stakeholders stop trusting the “weekly trends email.”
- Copy-paste mistakes happen, especially when you’re comparing multiple regions or time windows.
- If someone asks for the raw output later, you often can’t find what you used or how you interpreted it.
The Solution: Google Trends pages in, clean summaries out
This n8n workflow takes a Google Trends URL, pulls the content through Bright Data’s Web Unlocker, and converts it into clean text you can actually work with. From there, it extracts structured information (so the AI isn’t guessing what’s important), then asks Google Gemini to generate a clear, human-readable summary with key takeaways. Finally, it sends that summary via Gmail and posts it to a webhook for whatever your team uses next. It also writes the structured output to disk, which is quietly valuable when you need an audit trail or want to build a trend archive over time.
The workflow starts when you run it (manual trigger by default) and sets the target URL and Bright Data zone. Bright Data fetches the page, n8n converts the content to plain text, and the AI steps extract structure and generate a summary. Gmail delivers the final write-up, and the webhook pushes the same summary into your other systems.
What You Get: Automation vs. Results
| What This Workflow Automates | Results You’ll Get |
|---|---|
|
|
Example: What This Looks Like
Say you publish a “weekly trends” email covering 5 topics. Manually, you might spend about 20 minutes per topic to extract, clean, and rewrite, plus another 30 minutes to format and send, which is roughly 2 hours each week. With this workflow, you drop in 5 URLs (or run it 5 times), let the scraper + AI process, and you mainly review the summaries before they go out. That’s usually closer to 20 minutes total, not a whole working block.
What You’ll Need
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Bright Data Web Unlocker to reliably scrape Trends pages.
- Google Gemini to extract structure and write the summary.
- Bright Data token (get it from your Web Unlocker zone settings).
Skill level: Intermediate. You’ll connect credentials, paste a webhook URL, and tweak prompts without breaking the flow.
Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).
How It Works
A run begins with a URL. The workflow starts from a manual trigger in n8n, then assigns the Google Trends page URL you want to analyze along with your Bright Data zone name.
The page is fetched and cleaned. Bright Data Web Unlocker pulls the page content, then n8n converts markdown/HTML into plaintext. That “clean text” step matters because AI summaries get weird when the input is full of layout junk.
AI turns raw text into usable insight. An information extractor produces structured fields, then the summarization chain asks Google Gemini for key takeaways in a readable format. This is where you tune the prompt to match your brand voice and the kind of insights you want.
Distribution and archiving happen automatically. The summary is sent via Gmail, posted to your webhook endpoint, and the structured output is written to a file so you can audit, compare, or reuse it later.
You can easily modify the input source to read from Google Sheets instead of a single URL based on your needs. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Manual Trigger
Set up the manual trigger to start the workflow on demand for testing or one-off runs.
- Add the Manual Start Trigger node to your workflow (or keep it if already present).
- Leave Manual Start Trigger with default settings since it requires no configuration.
- Optionally keep Flowpast Branding as a visual note block (no configuration required).
Step 2: Connect Bright Data and Set the Target
Define the Google Trends URL and zone, then send it to Bright Data for markdown retrieval.
- In Assign Target URL & Zone, set url to
https://trends.google.com/trends/explore?gprop=youtube&hl=en-US. - In Assign Target URL & Zone, set zone to
web_unlocker1. - Open Bright Data API Request and set URL to
https://api.brightdata.com/request. - Set Method to
POST, Send Body totrue, and Send Headers totrue. - In Body Parameters, set zone to
{{ $json.zone }}and url to{{ $json.url }}?product=unlocker&method=api. - Add format =
rawand data_format =markdownin the body parameters. - Credential Required: Connect your httpHeaderAuth credentials in Bright Data API Request.
Step 3: Set Up AI Processing and Extraction
Convert the markdown to text, parse structured trend data, and generate summaries using Gemini-powered AI.
- In Markdown Text Converter, set Text to
=You need to analyze the below markdown and convert to textual data. Please do not output with your own thoughts. Make sure to output with textual data only with no links, scripts, css etc. {{ $json.data }}. - Ensure Markdown Text Converter uses the Gemini model connected via Gemini Chat for Extraction.
- Credential Required: Connect your googlePalmApi credentials in Gemini Chat for Extraction (credentials must be added to the parent Gemini node, not the chain node).
- In Structured Info Parser, set Text to
=Extract the Google Trend Data in JSON. Here's the content: {{ $json.text }}. - In Structured Info Parser, set Schema Type to
manualand Input Schema to{ "type": "array", "properties": { "topics": { "type": "string" },"desc": { "type": "string" } } }. - Ensure Structured Info Parser uses the Gemini model connected via Gemini Chat for Struct Parse.
- Credential Required: Connect your googlePalmApi credentials in Gemini Chat for Struct Parse (credentials must be added to the parent Gemini node, not the extractor node).
- In Generate Trend Summary, set Chunking Mode to
advanced. - Ensure Generate Trend Summary uses the Gemini model connected via Gemini Chat for Summary.
- Credential Required: Connect your googlePalmApi credentials in Gemini Chat for Summary (credentials must be added to the parent Gemini node, not the summarization node).
Markdown Text Converter outputs to both Send Markdown Text Webhook and Structured Info Parser in parallel.
Structured Info Parser outputs to both Build Binary Payload and Generate Trend Summary in parallel.
Generate Trend Summary outputs to both Post Summary Webhook and Email Summary via Gmail in parallel.
Step 4: Configure Output Delivery and Storage
Send raw markdown, save structured JSON, post summaries to a webhook, and email results.
- In Send Markdown Text Webhook, set URL to
https://webhook.site/3c36d7d1-de1b-4171-9fd3-643ea2e4dd76and keep Send Body enabled. - In Send Markdown Text Webhook, set the body content to
{{ $json.text }}. - In Build Binary Payload, keep the Function Code as provided to encode JSON into a binary payload.
- In Write Output File, set Operation to
writeand File Name tod:\google-trends.json. - In Post Summary Webhook, set URL to
https://webhook.site/3c36d7d1-de1b-4171-9fd3-643ea2e4dd76and set the body content to{{ $json.response.text }}. - In Email Summary via Gmail, set Send To to
[YOUR_EMAIL], Subject toGoogle Trends Summary, and Message to{{ $json.response.text }}. - Credential Required: Connect your gmailOAuth2 credentials in Email Summary via Gmail.
⚠️ Common Pitfall: The file path in Write Output File is Windows-specific. Update File Name if your n8n instance runs on Linux or macOS.
Step 5: Test and Activate Your Workflow
Verify the complete execution path and then enable the workflow for regular use.
- Click Execute Workflow on Manual Start Trigger to run a test.
- Confirm Bright Data API Request returns markdown and Markdown Text Converter outputs clean text.
- Verify Structured Info Parser emits JSON, Write Output File creates
d:\google-trends.json, and Post Summary Webhook receives the summary. - Check your inbox for the email from Email Summary via Gmail.
- When successful, toggle the workflow to Active for production use.
Common Gotchas
- Bright Data credentials can expire or need specific permissions. If things break, check your Web Unlocker zone token and header auth credential in n8n first.
- If you’re using Wait nodes or external processing, timings vary. Bump up the wait duration if downstream steps run before the scrape or AI response is actually ready.
- Default Gemini prompts are generic. Add your preferred summary format and tone early or you will be editing outputs every week.
Frequently Asked Questions
About 30 minutes if you already have Bright Data and Gemini ready.
No. You’ll mostly paste credentials, set the URL, and adjust the Gemini 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 Bright Data usage and Gemini API costs based on how often you run summaries.
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 you’ll want to change the input. Replace the “Assign Target URL & Zone” step with a Google Sheets read so each row is a Trends URL, then keep the same extraction and summarization steps. Common tweaks include adding a “Weekly Google Trends Summary – {{date}}” subject line in Gmail, sending to a mailing list, and adjusting the Gemini prompt to output “Key shifts, why it matters, content ideas.”
Usually it’s an expired token or the wrong header format in n8n credentials. Confirm your Web Unlocker zone is active, then regenerate the token and update the Header Auth value (it should look like a Bearer token). If it still fails, check whether the target URL is blocked or redirecting, because that can change what the scraper returns. Rate limiting can also show up when you run many URLs back-to-back.
On n8n Cloud’s Starter plan, you can run a few thousand workflow executions per month, which is plenty for weekly reporting. If you self-host, there’s no execution cap, so it mainly depends on your server and your Bright Data/Gemini quotas. Practically, most teams run anywhere from a handful of URLs to a few dozen per week without issues once prompts and rate limits are tuned.
For this use case, usually yes. You’re combining scraping, text cleanup, structured extraction, summarization, file writing, and multi-channel delivery, and n8n handles that kind of “real workflow” logic without getting fragile or expensive. Zapier and Make can work, but the moment you add branching, retries, or storage, it gets awkward. Also, self-hosting is a big deal if you want unlimited runs. If you want help choosing, Talk to an automation expert and you’ll get a straight answer.
Once this is running, your “weekly trends” doesn’t depend on someone having a spare hour and the patience to format. The workflow handles the repetitive parts, so you can focus on what the trend means and what to do next.
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.
