Google Sheets + Google Suggest, keywords ready to use
Keyword research gets messy fast. You start with a seed list, then it’s tabs on tabs, copying suggestions, clicking results, and trying to remember why a phrase looked promising in the first place.
SEO specialists feel it when they’re building topic clusters. Marketers run into it during campaign planning. And if you publish content weekly, you will recognize the grind. This Google Suggest keywords automation turns a simple Google Sheet into a steady stream of usable ideas, with SERP context attached.
Below, you’ll see exactly what the workflow does, what you get out of it, and how teams use it to keep content pipelines full without spending half a day “researching.”
How This Automation Works
The full n8n workflow, from trigger to final output:
n8n Workflow Template: Google Sheets + Google Suggest, keywords ready to use
flowchart LR
subgraph sg0["Manual Flow"]
direction LR
n0@{ icon: "mdi:play-circle", form: "rounded", label: "Manual Trigger", pos: "b", h: 48 }
n1@{ icon: "mdi:database", form: "rounded", label: "Fetch Keyword List (Google S..", 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/code.svg' width='40' height='40' /></div><br/>Select Keyword of the Day"]
n3@{ icon: "mdi:swap-vertical", form: "rounded", label: "Set Selected Keyword", 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/>Fetch Autocomplete Suggestio.."]
n5@{ icon: "mdi:code-braces", form: "rounded", label: "Extract Suggestion Keywords", pos: "b", h: 48 }
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/httprequest.dark.svg' width='40' height='40' /></div><br/>Search Keywords (Google Cust.."]
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/code.svg' width='40' height='40' /></div><br/>Format Search Results"]
n0 --> n1
n3 --> n4
n2 --> n3
n5 --> n6
n1 --> n2
n6 --> n7
n4 --> n5
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 database
class n4,n6 api
class n2,n5,n7 code
classDef customIcon fill:none,stroke:none
class n2,n4,n6,n7 customIcon
The Problem: Keyword Research That Never Stays “Clean”
You don’t usually lose time to one big task. It’s the tiny steps. Open the sheet. Pick a seed keyword. Paste it into Google. Copy the Suggest ideas somewhere. Click a few results. Paste titles and snippets into a doc. Then do it again tomorrow because your content calendar doesn’t care that you already did “research” last week. And honestly, manual keyword research is where mistakes creep in: duplicates, outdated SERP notes, and half-finished lists that nobody trusts enough to publish from.
The friction compounds. Here’s where it breaks down.
- You waste about 1–2 hours a week just collecting autocomplete ideas and copying SERP notes into something reusable.
- Two people can research the “same” keyword and walk away with completely different context, so planning meetings drag on.
- Without a rotation system, the same seed terms get picked repeatedly while other good topics sit untouched in the sheet.
- Lists fill up with suggestions, but no one captures what’s ranking, which means the ideas aren’t ready to brief or write.
The Solution: Daily Keyword Discovery from Sheets + SERP Context
This n8n workflow takes the keyword list you already maintain in Google Sheets and turns it into a daily “keyword packet” you can actually use. You start with a sheet column labeled Title or Keyword. When the workflow runs, it selects one seed term for the day (rotating through your list automatically). Then it calls Google Suggest to pull the autocomplete variations people are actively searching. For each of those suggestions, it queries the Google Custom Search API, grabs the top results, and returns structured JSON with titles, links, and snippets. Instead of a vague list of ideas, you end up with a research-ready output that can feed briefs, content outlines, or even AI content generation safely.
The workflow starts with your Google Sheet. It picks the “daily keyword” based on how many days have passed since a set start date, then expands that seed into suggestions and attaches real SERP context. Finally, everything is shaped into a clean JSON object you can store, forward, or plug into the next workflow.
What You Get: Automation vs. Results
| What This Workflow Automates | Results You’ll Get |
|---|---|
|
|
Example: What This Looks Like
Say you publish 3 SEO articles a week and you want one solid keyword cluster ready before each draft. Manually, you might spend about 20 minutes picking a seed from Sheets, 20 minutes collecting Google Suggest ideas, and another 30 minutes clicking results and saving snippets, so roughly 1 hour per article. That’s about 3 hours a week. With this workflow, you run it once per day, skim the JSON output, and you’re usually done in about 10 minutes. The SERP context is already attached, so your “research” turns into simple decision-making.
What You’ll Need
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Google Sheets to store your seed keyword list.
- Google Custom Search API to pull top results and snippets.
- API key + cx (get both from Google Cloud and Custom Search Engine settings)
Skill level: Intermediate. You’ll connect Google credentials and paste API variables safely (no hardcoding).
Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).
How It Works
You trigger the run (manual, or scheduled daily). The workflow is built with a manual trigger, which is perfect for testing. Once it’s working, most teams schedule it to run once per day.
Your Google Sheet provides the seed list. n8n reads the sheet and looks for a column named Title or Keyword, so you don’t need a complicated template. Keep it simple.
A “daily selector” chooses one keyword automatically. A small code step rotates through your list based on the number of days since a chosen start date (July 4, 2025 in this version). That keeps the output fresh without random chaos.
Google Suggest expands the seed, then Google Custom Search adds context. The workflow requests autocomplete ideas, cleans them into usable items, and queries the search API to pull titles, links, and snippets for each suggestion. Finally, it formats everything into structured JSON for easy reuse.
You can easily modify the start date logic to randomize selection or to match a campaign cycle based on your needs. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Manual Trigger
Start the workflow with a manual test trigger so you can validate the keyword pipeline end-to-end.
- Add Manual Launch Trigger as the starting node.
- Leave all settings at their defaults.
- Confirm the connection flow: Manual Launch Trigger → Retrieve Keyword Sheet.
Step 2: Connect Google Sheets
Pull the keyword list from your spreadsheet so the workflow can choose the daily seed keyword.
- Add Retrieve Keyword Sheet after Manual Launch Trigger.
- Set Document to the target spreadsheet ID:
[YOUR_ID]. - Set Sheet to
Sheet1(valuegid=0). - Credential Required: Connect your googleSheetsOAuth2Api credentials.
Tip: Ensure your sheet has a Title or Keyword column, as Daily Keyword Selector checks those fields.
Step 3: Set Up the Keyword Selection and Autocomplete Pipeline
Calculate today’s keyword, assign it to a field, and fetch autocomplete suggestions from Google Suggest.
- Add Daily Keyword Selector and paste the provided JS Code exactly as-is.
- Add Assign Chosen Keyword and set seed_keyword to
={{ $json.keyword }}. - Add Request Autocomplete Ideas and set URL to
https://suggestqueries.google.com/complete/search. - In Request Autocomplete Ideas, set query parameters: client to
firefoxand q to={{$json.keyword}}. - Connect the execution flow: Retrieve Keyword Sheet → Daily Keyword Selector → Assign Chosen Keyword → Request Autocomplete Ideas.
⚠️ Common Pitfall: If the sheet has no rows, Daily Keyword Selector will fail when calculating the index. Add at least one keyword row before testing.
Step 4: Query Search Results and Shape the Output
Parse the autocomplete response, query Google Custom Search for each suggestion, then reshape the output into a clean structure.
- Add Parse Suggestion Terms and paste the provided Function Code to transform the API response into keyword items.
- Add Query Search Results with URL set to
https://www.googleapis.com/customsearch/v1. - Enable Send Query and set the query parameter q to
={{ $json.keyword }}. - Credential Required: Connect your httpBasicAuth credentials in Query Search Results.
- Add Shape Result Output and paste the provided JS Code to map
title,link, andsnippet. - Connect the execution flow: Request Autocomplete Ideas → Parse Suggestion Terms → Query Search Results → Shape Result Output.
⚠️ Common Pitfall: Ensure your Custom Search API credentials and engine configuration support the queries you are sending, or Query Search Results may return empty items.
Step 5: Test and Activate Your Workflow
Run a manual test to confirm the workflow selects a keyword, retrieves suggestions, and returns search results.
- Click Execute Workflow to run Manual Launch Trigger and observe the data flow through each node.
- Verify that Assign Chosen Keyword outputs a
seed_keywordvalue and Request Autocomplete Ideas returns suggestion data. - Confirm Shape Result Output returns structured items with
title,link, andsnippet. - When satisfied, toggle the workflow to Active for production use.
Common Gotchas
- Google Sheets credentials can expire or be missing access to the specific spreadsheet. If things break, check the Google connection in your n8n credentials and confirm the sheet is shared with the right account.
- If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
- Google Custom Search can fail silently when the API key, cx, or API restrictions are wrong. Check your Google Cloud API console for quota errors and confirm you’re using credential variables, not hardcoded values.
Frequently Asked Questions
About 30 minutes if your Google accounts and API access are ready.
No. You’ll mostly connect accounts and paste in your API variables. The only “code” is already included in the workflow, and you can leave it as-is.
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 Google Custom Search API costs, which are usually a small monthly charge once you pass the free tier.
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 change the selection logic in the “Daily Keyword Selector” code node so it picks 7 keywords per run (or randomly samples). Common tweaks include switching the start date, selecting based on a “last used” column in Google Sheets, and pushing outputs to Telegram for review instead of returning JSON only.
Usually it’s an OAuth permission issue or the sheet isn’t accessible to the connected Google account. Reconnect Google Sheets in n8n, then confirm the spreadsheet ID is correct and the file is shared with that account. If it still fails, check if your workspace admin restricts third-party app access.
A few hundred seed keywords is fine for most setups.
Often, yes, because this workflow needs looping over suggestions, shaping JSON, and handling API nuances without turning into a fragile multi-Zap chain. n8n also gives you a self-hosted path, which matters if you want to run daily without watching task limits. Zapier or Make can still work if you simplify the scope (for example, Suggest ideas only, no SERP context). But once you add Custom Search and structured output, n8n is usually the calmer option. Talk to an automation expert if you want help choosing based on volume and budget.
Once this is running, keyword discovery becomes a background habit instead of a weekly scramble. The workflow handles the repetitive collection so you can spend your time picking winners and shipping content.
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.
