YouTube to Google Sheets, comment ideas ready to use
You know the feeling: you find a goldmine of YouTube comments, then lose an hour copying them into a doc, trying to spot patterns, and still walking away with “maybe” ideas.
This YouTube comment automation hits creators and content marketers first. But strategy leads and small agency teams feel it too, because the backlog is always hungry and your time is not.
This workflow pulls comments from any YouTube video, filters the ones worth turning into content, then writes research-backed topics, hooks, and outlines directly into Google Sheets. You’ll learn what it does, why it’s useful, and how to set it up without getting buried in tech details.
How This Automation Works
Here’s the complete workflow you’ll be setting up:
n8n Workflow Template: YouTube to Google Sheets, comment ideas ready to use
flowchart LR
subgraph sg0["Chat Intake Flow"]
direction LR
n0@{ icon: "mdi:play-circle", form: "rounded", label: "Chat Intake Trigger", pos: "b", h: 48 }
n1["<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/>Retrieve Video Comments"]
n2@{ icon: "mdi:robot", form: "rounded", label: "Assess Comment Relevance", pos: "b", h: 48 }
n3@{ icon: "mdi:swap-horizontal", form: "rounded", label: "Filter Viable Ideas", pos: "b", h: 48 }
n4@{ icon: "mdi:database", form: "rounded", label: "Log Raw Comments", pos: "b", h: 48 }
n5@{ icon: "mdi:swap-vertical", form: "rounded", label: "Iterate Comment Records", pos: "b", h: 48 }
n6@{ icon: "mdi:robot", form: "rounded", label: "Derive Topics & Research", pos: "b", h: 48 }
n7@{ icon: "mdi:wrench", form: "rounded", label: "Web Research Tool", pos: "b", h: 48 }
n8@{ icon: "mdi:robot", form: "rounded", label: "Craft Hook & Outline", pos: "b", h: 48 }
n9@{ icon: "mdi:database", form: "rounded", label: "Update Enriched Sheet", pos: "b", h: 48 }
n5 --> n6
n4 --> n5
n3 --> n4
n7 -.-> n6
n2 --> n3
n0 --> n1
n1 --> n2
n9 --> n5
n6 --> n8
n8 --> n9
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 n2,n6,n8 ai
class n7 ai
class n3 decision
class n4,n9 database
class n1 api
classDef customIcon fill:none,stroke:none
class n1 customIcon
Why This Matters: Turning comment chaos into repeatable content
YouTube comments are basically free audience research. People tell you what confused them, what they disagree with, what they tried, what failed, and what they want next. The problem is the workflow around it is messy. You open a video, scroll forever, copy chunks into notes, and later you can’t remember which comment came from where. Then you try to “summarize the vibe” in your head, which is how good ideas quietly slip through the cracks.
It adds up fast. Here’s where it breaks down.
- Copy-pasting comments into a doc takes long enough that you do it once, then avoid it for weeks.
- You end up chasing the loudest comments, not the most useful ones, because there’s no consistent way to filter ideas.
- Without a spreadsheet log, you can’t track which topics you’ve used, which hooks worked, or which video the insight came from.
- “AI ideas” can feel flimsy if they aren’t grounded in real comments and fresh research, so you spend extra time rewriting anyway.
What You’ll Build: YouTube comments to research-backed video ideas
You’ll set up an n8n workflow that starts with a simple input: a YouTube URL pasted into a chat-style trigger inside n8n. From there, Apify scrapes the video’s comments and basic metadata through an HTTP request, so you’re not manually hunting and copying anything. Each comment gets assessed by GPT‑4.1‑mini, which decides if it can inspire a real content idea (a clean “Yes/No,” not a vague maybe). Every comment is logged to Google Sheets first, so you keep a complete source-of-truth dataset. Then the “Yes” comments get enriched: Tavily pulls fresh context from the web, and GPT generates a topic, a strong hook, and a simple outline. Finally, the workflow updates the exact same row in your sheet with the new fields, keeping everything organized and searchable.
The flow starts with one link. It scrapes comments, filters them, and saves them. Then it adds research plus ready-to-use writing (topic, hook, outline) back into the same spreadsheet row so your backlog stays tidy.
What You’re Building
| What Gets Automated | What You’ll Achieve |
|---|---|
|
|
Expected Results
Say you review comments from 3 competitor videos each week. Manually, you might spend about 40 minutes per video collecting comments, then another hour trying to turn the best ones into usable angles, so call it roughly 3 to 4 hours weekly. With this workflow, you paste each URL (a minute), let Apify pull the comments, and let GPT + Tavily generate topics, hooks, and outlines while you do other work. In practice, most teams get the same “idea backlog” in about 30 minutes of hands-on time.
Before You Start
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Apify to scrape YouTube comments at scale.
- Google Sheets to store, sort, and track ideas.
- OpenAI API key (get it from the OpenAI API dashboard).
- Tavily API key (get it from your Tavily account settings).
Skill level: Beginner. You’ll connect accounts, paste a few IDs/keys, and point the Google Sheets nodes to the right spreadsheet.
Want someone to build this for you? Talk to an automation expert (free 15-minute consultation).
Step by Step
Paste a YouTube link to trigger the run. The workflow starts from a chat intake trigger in n8n, where you drop in a YouTube URL you want to mine for ideas.
Pull the comments automatically. An HTTP request calls Apify to retrieve comments plus useful metadata (like author and likes), so you’re working with structured data rather than a messy scroll.
Decide what’s worth keeping. GPT‑4.1‑mini reads each comment and labels it as a potential idea or not. The workflow logs everything to Google Sheets, so you can audit the decisions later (honestly, this is underrated).
Enrich the “Yes” comments with real context. For comments marked “Yes,” Tavily pulls current web research, and GPT turns that into a clear topic, a hook you can open with, and a simple outline. Then the workflow updates the same Google Sheets row with those new fields.
You can easily modify the filter strictness to capture more (or fewer) ideas based on your needs. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Chat Trigger
Set up the workflow entry point so a chat message provides the YouTube URL used to fetch comments.
- Add Chat Intake Trigger as the trigger node (chatTrigger).
- Leave the default Options as configured unless you need a custom chat setup.
- Confirm the trigger outputs
{{$json.chatInput}}which will be used downstream.
Step 2: Connect the Comment Source
Retrieve comments using the Apify endpoint and pass the chat input URL as the target.
- Add Retrieve Video Comments after Chat Intake Trigger.
- Set Method to
POSTand URL tohttps://api.apify.com/v2/acts/mExYO4A2k9976zMfA/run-sync-get-dataset-items. - Enable Send Body, Send Headers, and set Specify Body to
json. - Set JSON Body to
={ "customMapFunction": "(object) => { return {...object} }", "maxItems": 100, "sort": "top", "startUrls": [ "{{ $json.chatInput }}" ] }. - In Header Parameters, set Accept to
application/jsonand Authorization toBearer [CONFIGURE_YOUR_TOKEN].
[CONFIGURE_YOUR_TOKEN] with your Apify API token, or the request will fail.Step 3: Set Up Comment Relevance Scoring
Use AI to determine whether each comment is a viable content idea, then filter out non-viable results.
- Add Assess Comment Relevance after Retrieve Video Comments.
- Credential Required: Connect your
openAiApicredentials. - Confirm JSON Output is enabled and the message uses
{{ $json.text }}for comment content. - Add Filter Viable Ideas after Assess Comment Relevance.
- Set the filter condition Left Value to
{{ $json.choices[0].message.content.output }}and Right Value toYes.
Step 4: Connect Google Sheets
Log filtered comments to a sheet and prepare records for enrichment.
- Add Log Raw Comments after Filter Viable Ideas.
- Credential Required: Connect your
googleSheetsOAuth2Apicredentials. - Set Operation to
appendOrUpdate. - Set Document ID and Sheet Name to your target spreadsheet and tab (replace
[YOUR_ID]placeholders). - Map columns using the expressions, for example id to
{{ $('Retrieve Video Comments').item.json.id }}and contentIdea to{{ $json.choices[0].message.content.output }}. - Add Iterate Comment Records after Log Raw Comments to process each row in batches.
Step 5: Configure AI Research and Outline Creation
Generate topics, run web research, and craft a hook and outline for each viable comment.
- Add Derive Topics & Research after Iterate Comment Records.
- Credential Required: Connect your
openAiApicredentials. - Ensure the message references the comment with
{{ $json.text }}. - Connect Web Research Tool to Derive Topics & Research as an AI tool and set its URL to
https://api.tavily.com/search. - Set the JSON Body to
{ "query": "{searchTerm}", "topic": "general", "search_depth": "advanced", "chunks_per_source": 3, "max_results": 1, "time_range": null, "days": 7, "include_answer": true, "include_raw_content": false, "include_images": false, "include_image_descriptions": false, "include_domains": [], "exclude_domains": [] }. - Because Web Research Tool is an AI tool node, add its credentials to Derive Topics & Research (the parent). Set the tool headers to include
Authorization: Bearer [CONFIGURE_YOUR_TOKEN]andContent-Type: application/json. - Add Craft Hook & Outline after Derive Topics & Research and ensure it reads
{{ $json.choices[0].message.content.topic }}and{{ $json.choices[0].message.content.research_overview }}. - Credential Required: Connect your
openAiApicredentials for Craft Hook & Outline.
Step 6: Configure the Enriched Output Sheet
Write the topic, research, hook, and outline back to the spreadsheet row that matches the original comment.
- Add Update Enriched Sheet after Craft Hook & Outline.
- Credential Required: Connect your
googleSheetsOAuth2Apicredentials. - Set Operation to
update. - Set Document ID and Sheet Name to match the same spreadsheet used in Log Raw Comments.
- Map columns using expressions such as id to
{{ $('Iterate Comment Records').item.json.id }}, hook to{{ $json.choices[0].message.content.hook }}, and topic to{{ $('Derive Topics & Research').item.json.choices[0].message.content.topic }}.
Step 7: Test and Activate Your Workflow
Run an end-to-end test to verify comment ingestion, filtering, and enrichment before going live.
- Click Execute Workflow and send a chat input containing a YouTube video URL.
- Verify that Retrieve Video Comments returns comment items and Filter Viable Ideas passes only
Yesresults. - Confirm that Log Raw Comments writes rows and Update Enriched Sheet fills topic, research, hook, and outline.
- When satisfied, toggle the workflow to Active for production use.
Troubleshooting Tips
- Apify tokens can fail if the actor permissions changed or the token was rotated. If scraping suddenly stops, check your Apify token in n8n Credentials first, then confirm the actor run succeeds in Apify.
- If you’re using Wait-style timing (or Apify runs take longer than usual), processing times vary. Bump up any wait duration and rerun if downstream steps act like they received empty comment data.
- Google Sheets updates often break when headers don’t match. Make sure your sheet columns are in this exact order: id, text, author, likes, isIdea, topic, research, hook, outline.
Quick Answers
About 15–25 minutes if you already have your API keys ready.
No. You’ll connect Apify, OpenAI, Tavily, and Google Sheets, then paste in your sheet ID and credentials.
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 OpenAI, Tavily, and Apify usage costs, which depend on how many comments you process.
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 should. You can tighten or loosen the GPT filter in the “Assess Comment Relevance” step, and you can change the enrichment output by adjusting the “Craft Hook & Outline” prompt to generate Shorts scripts, blog angles, or poll questions instead. If you want deeper context, switch Tavily’s search depth in the “Web Research Tool” step. You can also swap the notification/output by adding Slack or email once a comment is marked “Yes.”
Usually it’s permissions or a mismatched spreadsheet setup. Make sure the Google account you connected has edit access to the target sheet, then confirm the worksheet/tab name matches what the node expects. If only the update step fails, it’s often because the workflow can’t find the row to update (wrong ID mapping) or your headers are out of order.
Plenty for most teams. The practical limit is usually API cost and how many comments Apify returns, not n8n itself. On n8n Cloud, higher plans handle higher monthly executions, and on self-hosting there’s no hard execution limit (your server resources become the constraint). If you’re processing thousands of comments at once, use batching and keep an eye on OpenAI/Tavily rate limits.
Often, yes. This workflow uses looping/batching, row updates in Google Sheets, and multiple AI steps, which is where Zapier and Make can get expensive or awkward. n8n also gives you more control over what gets logged first (raw comments) versus what gets enriched later, which matters when you want traceability. If you self-host, you can run as many executions as your server can handle, which changes the economics for high-volume scraping. Zapier or Make can still be fine for a simple “new row → send message” type of flow. Talk to an automation expert if you want a quick recommendation.
Once this is running, your comment research stops being a “someday” task and turns into a system. The workflow handles the repetitive parts so you can focus on choosing the best ideas and making them yours.
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.
