YouTube + Google Sheets: email comment insights
YouTube comments are useful, but reading them one-by-one is a time sink. Then you try to summarize them for a client, a boss, or your own next video idea, and the “quick scan” turns into a whole task.
This YouTube insights automation hits marketing managers hardest, but creators and agency teams feel it too. You get a clean email report with sentiment, themes, and viewer questions without living inside the comments tab.
You’ll see what the workflow does, what you need to run it, and how the moving parts fit together so you can tweak it for your own reporting rhythm.
How This Automation Works
Here’s the complete workflow you’ll be setting up:
n8n Workflow Template: YouTube + Google Sheets: email comment insights
flowchart LR
subgraph sg0["Pick Video Ids from Google sheet Flow"]
direction LR
n0@{ icon: "mdi:cog", form: "rounded", label: "Limit", pos: "b", h: 48 }
n1@{ icon: "mdi:robot", form: "rounded", label: "AI Agent", pos: "b", h: 48 }
n2@{ icon: "mdi:swap-horizontal", form: "rounded", label: "If", pos: "b", h: 48 }
n3@{ icon: "mdi:swap-vertical", form: "rounded", label: "Set Video Details", pos: "b", h: 48 }
n4@{ icon: "mdi:cog", form: "rounded", label: "Get Youtube Video Details", 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/>Get Youtube Video Comments"]
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/>Prepare Comments Data"]
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/>Prepare HTML for Email"]
n8@{ icon: "mdi:message-outline", form: "rounded", label: "Gmail Account Configuration", pos: "b", h: 48 }
n9@{ icon: "mdi:database", form: "rounded", label: "Update Status on Google Sheet", pos: "b", h: 48 }
n10@{ icon: "mdi:play-circle", form: "rounded", label: "Pick Video Ids from Google s..", pos: "b", h: 48 }
n11@{ icon: "mdi:brain", form: "rounded", label: "Azure OpenAI Chat Model", pos: "b", h: 48 }
n2 --> n0
n0 --> n3
n1 --> n7
n3 --> n4
n6 --> n1
n7 --> n8
n11 -.-> n1
n4 --> n5
n5 --> n6
n8 --> n9
n10 --> n2
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 n10 trigger
class n1 ai
class n11 aiModel
class n2 decision
class n9 database
class n5 api
class n6,n7 code
classDef customIcon fill:none,stroke:none
class n5,n6,n7 customIcon
Why This Matters: Turning Comment Noise into Decisions
Comments are where your audience tells you what’s landing and what’s not. The problem is volume and messiness. You’ll get praise, confusion, time-stamped bug reports, feature requests, and the occasional argument thread that has nothing to do with your video. If you’re tracking multiple videos (or multiple clients), the manual routine becomes predictable: open video, scroll, copy a few “good” comments, miss half the patterns, then write a summary from memory. Honestly, it’s the kind of work that feels busy, not valuable.
The friction compounds. Here’s where it breaks down.
- You end up sampling comments instead of analyzing them, so your “insights” are biased toward whatever you happened to notice first.
- Copy-pasting quotes into docs is slow, and it’s easy to misread tone when you’re rushing.
- Reporting becomes inconsistent across videos, which makes it hard to spot real shifts in audience sentiment week to week.
- Without a “done” status in your tracker, the same video gets reviewed twice or forgotten entirely.
What You’ll Build: Automated YouTube Comment Insight Emails
This workflow turns a simple Google Sheet into a comment-insights pipeline. You keep a list of YouTube video IDs in a sheet. Every minute, n8n checks for items that still need processing, pulls the latest video details and top comments via the YouTube API, and packages that data into something an AI model can actually analyze. From there, GPT-4o (via an Azure OpenAI Chat Model node) classifies sentiment, surfaces recurring themes, pulls out viewer questions, and suggests improvement ideas you can act on. Finally, it builds an HTML email report and sends it through Gmail. When the email is sent, the workflow updates the row to “Mail Sent” so you don’t get duplicates.
The flow starts in Google Sheets, where the sheet acts like your lightweight job queue. YouTube and HTTP Request nodes fetch the raw material, the AI Agent turns it into insights, and Gmail delivers a report you can forward as-is.
What You’re Building
| What Gets Automated | What You’ll Achieve |
|---|---|
|
|
Expected Results
Let’s say you publish 5 videos a week and you want a consistent insights email for each one. Manually, even a “quick” review can be about 45 minutes per video once you read, filter, and write up themes, which is roughly 4 hours a week. With this workflow, you add the video ID to Google Sheets (maybe 2 minutes), wait for n8n to fetch comments and run the analysis, and you get the email in your inbox. You still review it, but the heavy lift is already done.
Before You Start
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Google Sheets for tracking video IDs and statuses.
- Gmail to deliver the insight report email.
- YouTube API key (create it in Google Cloud Console).
- OpenAI/Azure OpenAI credentials (from your Azure OpenAI resource or OpenAI provider setup).
Skill level: Intermediate. You’ll connect credentials, verify a YouTube API setup, and map a few fields in Sheets.
Want someone to build this for you? Talk to an automation expert (free 15-minute consultation).
Step by Step
Google Sheets triggers the run. The workflow checks your tracking sheet every minute and looks for video IDs that haven’t been marked “Mail Sent.” That status field is what keeps things tidy.
Branching and throttling prevent chaos. An If node routes only the rows that need work, and a throttle/limit step controls how many items process at once, so you don’t accidentally blast through quotas when you add a backlog.
YouTube data and comments are pulled in. The workflow retrieves basic metadata (title, channel, stats) and fetches top comments via HTTP Request. Then a processing step reshapes that payload into a consistent structure for analysis.
An AI Agent produces the insights and email content. The Azure OpenAI chat model powers sentiment and theme detection, then the workflow builds HTML markup and sends the report through Gmail. After a successful send, Google Sheets updates the row status so it won’t run again.
You can easily modify the report format to match your brand voice or internal template based on your needs. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Google Sheets Trigger
Start by setting up the workflow trigger that watches your spreadsheet and kicks off the processing chain from Monitor Sheet Video IDs to Branch Logic.
- Add and open Monitor Sheet Video IDs.
- Select the spreadsheet and worksheet that contain the video IDs you want to monitor.
- Set the trigger options to capture new or updated rows based on your monitoring preference.
- Confirm the output connects to Branch Logic, as the execution flow begins with Monitor Sheet Video IDs → Branch Logic.
Credential Required: Connect your Google Sheets credentials in Monitor Sheet Video IDs.
Step 2: Connect Google Sheets
Set up the spreadsheet update step and ensure the branching logic can continue to downstream nodes like Throttle Items and Configure Video Info.
- Open Modify Sheet Status and configure the target sheet and update range to mark processed rows.
- Confirm the flow continues from Send Gmail Report → Modify Sheet Status.
- Keep Branch Logic connected to Throttle Items to ensure the processing chain starts after the trigger.
Credential Required: Connect your Google Sheets credentials in Modify Sheet Status.
Step 3: Set Up Insight Agent
Configure the AI analysis path so comment data flows into Insight Agent with the Azure model connected, then into Build Email Markup.
- Open Insight Agent and define the prompt/instructions for summarizing comment sentiment and insights.
- Connect Azure Chat Model as the language model to Insight Agent (already linked via
ai_languageModel). - Ensure the flow follows Process Comment Payload → Insight Agent → Build Email Markup.
Credential Required: Connect your Azure OpenAI credentials in Azure Chat Model.
Step 4: Configure Output and Action Nodes
Complete the data retrieval, transformation, and report delivery steps that build the insight email and update your sheet.
- In Configure Video Info, map the incoming sheet row fields to the structure expected by downstream YouTube requests.
- Configure Retrieve Video Metadata to look up video details, then pass results to Fetch Video Comments.
- Set up Fetch Video Comments to call the comments API and return raw comment data to Process Comment Payload.
- In Process Comment Payload, parse and normalize comments for the AI summary input.
- In Build Email Markup, format the AI output into HTML or structured email content for Send Gmail Report.
- Configure Send Gmail Report with recipient, subject, and body mapping from Build Email Markup, then verify it routes to Modify Sheet Status.
Credential Required: Connect your YouTube credentials in Retrieve Video Metadata.
Credential Required: Connect your Gmail credentials in Send Gmail Report.
⚠️ Common Pitfall: If Fetch Video Comments calls a protected endpoint, add appropriate authentication in the node or the request will fail silently.
Final Step: Test and Activate Your Workflow
Run a manual test to confirm the full path from the sheet trigger to the emailed insight report and status update.
- Use Monitor Sheet Video IDs and click Test step to pull a sample row.
- Verify the chain executes through Branch Logic → Throttle Items → Configure Video Info → Retrieve Video Metadata → Fetch Video Comments → Process Comment Payload → Insight Agent → Build Email Markup → Send Gmail Report → Modify Sheet Status.
- Confirm a Gmail message is delivered and the sheet status is updated for the processed row.
- Once verified, toggle the workflow to Active for production use.
Troubleshooting Tips
- YouTube credentials can expire or lack the right API access. If calls fail, check your Google Cloud Console project, enabled YouTube Data API, and quota/errors log first.
- If you’re using Wait nodes or external processing, timing can vary. Bump up the wait duration if downstream nodes fail on empty responses.
- AI prompts ship generic by default. Add your brand voice and what “good insights” mean for you inside the Agent prompt, or you will keep rewriting summaries.
Quick Answers
About 30 minutes if your APIs are ready.
No. You’ll mostly connect accounts and paste in API credentials. The workflow already contains the logic for fetching, analyzing, and emailing.
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 YouTube API usage (usually free at small volumes) and AI usage (often a few cents per report, depending on comment volume).
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. Most people customize the “Insight Agent” instructions (tone, what to extract, how long summaries should be) and the “Build Email Markup” step to match an internal report template. You can also change the Google Sheet fields (for example, add a “Client” column and include it in the email subject). If you want Slack instead of email, the Gmail send step is the swap.
Usually it’s an API key issue or the YouTube Data API isn’t enabled for the Google Cloud project you’re using. Check quota limits too, especially if you’re processing backlogs. If the video is private or comments are disabled, the fetch step can also fail or return an empty payload, which then breaks the analysis.
On n8n Cloud you’re mainly limited by your execution allowance and your API quotas, while self-hosting is mostly limited by your server. In practical terms, this workflow handles “a lot” for small teams because it processes one sheet row at a time and throttles requests. If you plan to run hundreds of videos in a short window, expect to increase throttling and watch YouTube quota usage.
Often, yes. n8n is better when you need branching logic, custom payload shaping, and AI prompting in the same flow without paying extra per “path.” It also gives you self-hosting, which is a big deal if you run frequent checks (like every minute) and don’t want costs to climb. Zapier or Make can be quicker for a tiny two-step automation, but this is more than that. If you’re unsure, Talk to an automation expert and explain your volume and reporting needs.
The workflow reads the comments, pulls the patterns, and sends the report. You get your time back, and your content decisions stop being guesswork.
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.
