Google Trends + Google Sheets: ideas logged clean
Your content research probably starts the same way every time. You check what’s trending, open a few articles, take messy notes, then lose half of it in tabs, bookmarks, and “I’ll clean this up later.”
This Google Trends Sheets automation hits content strategists hardest, honestly. But SEO leads and small marketing teams feel it too, because the same “quick research” task keeps coming back. The outcome is simple: trend ideas get logged cleanly with summaries you can search, sort, and turn into a plan.
Below you’ll see how the workflow pulls Google Trends topics, grabs related articles, summarizes what matters, and saves everything into Google Sheets so your editorial planning stops relying on memory.
How This Automation Works
The full n8n workflow, from trigger to final output:
n8n Workflow Template: Google Trends + Google Sheets: ideas logged clean
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:cog", form: "rounded", label: "XML", pos: "b", h: 48 }
n2["<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/>GoogleTrends"]
n3@{ icon: "mdi:swap-vertical", form: "rounded", label: "CONFIG", pos: "b", h: 48 }
n4@{ icon: "mdi:database", form: "rounded", label: "Get saved keywords", pos: "b", h: 48 }
n5@{ icon: "mdi:swap-vertical", form: "rounded", label: "Loop Over Items", pos: "b", h: 48 }
n6@{ icon: "mdi:swap-vertical", form: "rounded", label: "Mapping", pos: "b", h: 48 }
n7@{ icon: "mdi:database", form: "rounded", label: "Google Sheets", pos: "b", h: 48 }
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/code.svg' width='40' height='40' /></div><br/>New keywords"]
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/>content1"]
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/httprequest.dark.svg' width='40' height='40' /></div><br/>content2"]
n11["<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/>content3"]
n12@{ icon: "mdi:play-circle", form: "rounded", label: "Start every hour past 11 min..", pos: "b", h: 48 }
n13@{ icon: "mdi:swap-horizontal", form: "rounded", label: "If we have scraped min 1 url..", pos: "b", h: 48 }
n14@{ icon: "mdi:cog", form: "rounded", label: "All scraping node failed. Do..", pos: "b", h: 48 }
n1 --> n8
n3 --> n4
n6 --> n13
n9 --> n10
n10 --> n11
n11 --> n5
n2 --> n1
n8 --> n5
n5 --> n6
n5 --> n9
n4 --> n2
n12 --> n3
n0 --> n3
n13 --> n7
n13 --> n14
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,n12 trigger
class n13 decision
class n4,n7 database
class n2,n9,n10,n11 api
class n8 code
classDef customIcon fill:none,stroke:none
class n2,n8,n9,n10,n11 customIcon
The Problem: Trend Research Turns Into Tab Chaos
Trend research is supposed to be the fast part. In reality, it’s a constant loop of “find a topic, open three sources, skim, copy a quote, paste into a doc, forget what you pasted, repeat.” If you’re doing this a few times a week, you’re burning hours on work that doesn’t create anything customer-facing. Worse, your notes rarely end up structured the same way, which makes it hard to compare ideas or hand them off to someone else without extra explaining.
The friction compounds. Here’s where it breaks down most often.
- You find a trend, but you don’t capture the context fast enough, so the idea goes stale by the time you return to it.
- Links get saved without summaries, which means you have to re-open and re-skim later.
- Everyone on the team tracks ideas differently, so your “content backlog” isn’t really searchable.
- Manual copy-paste introduces small errors (wrong source, mixed titles), and those errors cause bigger confusion later.
The Solution: Auto-Log Trends + Summaries to Google Sheets
This workflow watches Google Trends via an RSS feed, pulls out trending keywords, then collects three related article links per trend. For each of those articles, it fetches the page content, strips away the noisy HTML, and turns what’s left into a concise, readable summary using an AI summarization step (Jina AI, with an OpenAI Chat Model available in the workflow stack). Then it maps everything into clean fields like keyword, traffic estimate, publication date, sources, images, and one combined abstract. Finally, it appends the whole record into a pre-formatted Google Sheet so every idea lands in the same place, in the same structure, every time.
The workflow starts on a schedule (or a manual run when you want it). It checks what you already stored in Google Sheets, filters out repeats, scrapes the three related articles, generates the summary, and only saves results that meet a minimum “usable length” check. No more half-empty rows.
What You Get: Automation vs. Results
| What This Workflow Automates | Results You’ll Get |
|---|---|
|
|
Example: What This Looks Like
Say you review trends three times a week and log 10 promising topics each session. Manually, even a “quick pass” looks like 10 topics × 3 articles × maybe 5 minutes to skim and write a usable note, which is about 2.5 hours per session. With this workflow, your time becomes “review the sheet and pick winners,” often 15–20 minutes, because the scraping and summarizing runs in the background. That’s roughly 6 hours back in a normal week, and your notes are consistent instead of improvised.
What You’ll Need
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Google Sheets for storing your trend + summary log
- Google Sheets API access to let n8n write rows
- Jina.ai API key (get it from your Jina AI dashboard)
Skill level: Intermediate. You’ll connect accounts, paste an API key, and make sure your Google Sheet columns match the workflow fields.
Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).
How It Works
A schedule (or manual run) kicks things off. The workflow can run every minute on a schedule trigger, or you can start it yourself when you want a fresh batch of ideas.
Google Trends topics are fetched, then compared to what you’ve already logged. It pulls the RSS feed, converts it into usable data, and checks your Google Sheet so repeats get filtered out before any scraping happens.
Related articles are scraped and cleaned. For each new keyword, the workflow follows up to three article links, grabs the page content via HTTP request, and removes the clutter so the summarizer isn’t working with menus, footers, and junk text.
AI produces a summary, and only “good” rows get saved. A summary field is created, its length is checked, empty outputs get skipped, and the final structured record is appended to Google Sheets.
You can easily modify the RSS source to focus on a region or category based on your needs. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Schedule Trigger
Set up how this workflow starts, with both scheduled and manual runs feeding into the same setup parameters.
- Open Scheduled Minute Trigger and set the Cron Expression to
11 */1 * * *to run every minute at second 11. - Confirm Manual Run Launcher is present for on-demand testing and troubleshooting.
- Verify both Scheduled Minute Trigger and Manual Run Launcher connect to Setup Parameters.
Step 2: Connect Google Sheets
Link your Google Sheets so stored keywords are loaded and new summaries are appended.
- Open Retrieve Stored Keywords and select the target Document and Sheet.
- Credential Required: Connect your googleSheetsOAuth2Api credentials in Retrieve Stored Keywords.
- Open Append to Sheets and select the same Document and Sheet.
- Credential Required: Connect your googleSheetsOAuth2Api credentials in Append to Sheets.
Step 3: Set Up Parameter Defaults
Define thresholds and API keys used throughout the pipeline.
- Open Setup Parameters and set min_traffic to
500. - Set max_results to
3. - Set jina_key to your Jina AI API key (leave blank only if your endpoint doesn’t require authorization).
Authorization headers.Step 4: Configure Trend Fetching and Filtering
Pull Google Trends RSS, convert it to JSON, and filter new keywords against your sheet.
- Open Google Trends Fetch and set URL to
https://trends.google.it/trending/rss?geo=IT. - Keep XML to JSON Parser options as-is; it normalizes RSS to JSON for later parsing.
- In Filter New Keywords, confirm the JavaScript references Setup Parameters, Retrieve Stored Keywords, and XML to JSON Parser to filter by traffic and remove duplicates.
- Verify execution flow: Retrieve Stored Keywords → Google Trends Fetch → XML to JSON Parser → Filter New Keywords.
Step 5: Build the Scrape and Summary Pipeline
Loop through filtered keywords, scrape related articles, and construct summary fields.
- In Iterate Keyword Batches, keep defaults to process items one batch at a time.
- Iterate Keyword Batches outputs to both Map Summary Fields and Scrape Article One in parallel, so keep both connections intact.
- In Scrape Article One, set URL to
=https://r.jina.ai/{{ $('Filter New Keywords').item.json.news_item_url1 }}and keep headers likeAuthorization,X-Remove-Selector, andX-Return-Format. - Repeat the same URL structure for Scrape Article Two and Scrape Article Three with
news_item_url2andnews_item_url3. - In Map Summary Fields, keep summary mapped to
={{ $('Scrape Article One').item.json.data.text.replaceAll('\n', ' ').trim() }} --- {{ $('Scrape Article Two').item.json.data.text.replaceAll('\n', ' ').trim() }} --- {{ $('Scrape Article Three').item.json.data.text.replaceAll('\n', ' ').trim() }}and map keyword fields from Filter New Keywords.
Step 6: Add Summary Validation and Output Mapping
Ensure summaries are long enough before appending them to your sheet.
- Open Check Summary Length and keep the condition as
={{ $json.summary.length > 100 }}. - Leave the false branch connected to Skip Empty Summaries to safely drop short outputs.
- In Append to Sheets, keep Operation set to
appendand map fields like abstract to={{ $json.abstract.replaceAll(' ', '').substring(0, 49999) }}and trending_keyword to={{ $json.trending_keyword }}.
Step 7: Test and Activate Your Workflow
Run a test to verify Google Trends fetching, filtering, scraping, and Sheets output.
- Click Execute Workflow and run via Manual Run Launcher.
- Confirm Filter New Keywords outputs a list of items and Scrape Article One through Scrape Article Three return text content.
- Check that Append to Sheets adds new rows with trending_keyword, approx_traffic, and summary fields populated.
- Activate the workflow to let Scheduled Minute Trigger run automatically in production.
Common Gotchas
- Google Sheets credentials can expire or need specific permissions. If things break, check the n8n credentials screen and the Google Cloud console OAuth consent/scopes first.
- If you’re using Wait nodes or external processing, timing varies. Bump up the wait duration if downstream nodes fail on empty responses after scraping.
- Default prompts in AI nodes are generic. Add your editorial style (tone, length, “include why it matters”) early or you will be editing summaries forever.
Frequently Asked Questions
About an hour if your Google Sheets access is ready.
No. You’ll mostly connect accounts and paste an API key. The only “technical” part is making sure your sheet columns match the workflow fields.
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 Jina.ai API usage, which depends on how many articles you summarize.
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 tweaks to make. Update the RSS source used in the “Google Trends Fetch” part of the workflow to point at the region/category you care about. You can also adjust the “Setup Parameters” values to control what gets stored, and change the summary prompt so the abstract focuses on your niche (for example, “SaaS marketing angle” or “local news implications”).
Usually it’s expired OAuth credentials or missing Google Sheets permissions. Reconnect Google Sheets in n8n, then confirm the spreadsheet is shared with the same Google account you authenticated. Also check that the Sheet ID and tab name match exactly, because one wrong character can make the append step look “broken” even though the connection is fine.
A lot, but you’ll feel limits in API quotas and your n8n plan before you hit a hard “row limit.” On n8n Cloud Starter, you’re capped by monthly executions; self-hosting removes that cap, and the real constraint becomes your server and the time it takes to scrape and summarize three articles per keyword. Practically, most teams start with a few dozen keywords per day, then increase once they’re happy with summary quality and sheet organization.
Often, yes. This workflow needs multi-step scraping, filtering out duplicates, and “only save if the summary is usable,” which is where n8n tends to feel less cramped. Zapier or Make can still do it, but you may end up stitching together extra steps (and paying more once you add branching and looping). If you just want “RSS to Google Sheets” with no summaries, those tools are fine. If you want the full research pipeline, n8n is a safer bet. Talk to an automation expert if you’re on the fence.
Set it up once, and your trend research becomes a living spreadsheet instead of a recurring chore. The workflow handles the repetitive parts so you can spend your time choosing angles and publishing.
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.
