HumationHuman + Automation
Back to Catalog

YouTube comment scraper & analyzer with GPT-4o + email summary report

Amit MehtaAmit Mehta
2571 views
2/3/2026
Date ComparisonConditional LogicSlackSchedulerAutomation
Official Page

How it Works

This workflow automates the collection and analysis of YouTube comments from a video and sends a summary report via email, using Google Sheets, the YouTube API, OpenAI (GPT-4o), and Gmail.

Whether you're a content creator, brand manager, or social media analyst, this workflow helps you automate sentiment analysis and receive insights directly in your inbox — all triggered from a simple spreadsheet.

🎯 Use Case

Ideal for:

  • YouTubers monitoring audience sentiment
  • Marketing teams analyzing campaign feedback
  • Community managers summarizing engagement

Setup Instructions

1. Upload the Spreadsheet

  • File name: Youtube_Video
  • Sheet structure: | ID | Video Title | YouTube Video ID | Status |
  • Add video IDs and set their Status as Pending

2. Configure Google Sheets Nodes

Connect your Google account to:

  • Pick Video IDs from Google Sheet
  • Update Status on Google Sheet

3. Add API Credentials

  • YouTube API Key → for comment + video scraping nodes
  • OpenAI API Key → for analyzing comments
  • Gmail Account → for sending the summary email

4. Activate the Workflow

Once live, the workflow will:

  1. Watch for new or updated rows in the spreadsheet
  2. Scrape comments using the YouTube API
  3. Analyze sentiment and key themes via GPT-4o
  4. Send a formatted HTML email with the summary
  5. Update the spreadsheet status to Mail sent

🔁 Workflow Logic

  1. Trigger: New/updated row in Google Sheet
  2. Retrieve: YouTube video metadata + comments
  3. Analyze: Comments using GPT-4o
  4. Email: Summary report via Gmail
  5. Update: Spreadsheet status to Mail sent

🧩 Node Descriptions

| Node Name | Description | |-----------|-------------| | Pick Video IDs from Google Sheet | Watches the spreadsheet and retrieves pending video IDs | | If | Checks whether status is 'Pending' | | Limit | Restricts the number of processed rows | | Set Video Details | Prepares video info (e.g., title, channel) | | Get YouTube Video Details | Fetches metadata (title, channel, etc.) | | Get YouTube Video Comments | Pulls top-level comments using YouTube API | | Prepare Comments Data | Formats comment text for OpenAI | | AI Agent | Summarizes comments using OpenAI's GPT-4o | | Prepare HTML for Email | Converts summary into HTML for email body | | Gmail Account Configuration | Sends the email report via Gmail | | Update Status on Google Sheet | Marks the row as 'Mail sent' |

🛠️ Customization Tips

  • Change the AI prompt for tone, length, or custom metrics
  • Send results to Slack or Telegram instead of Gmail
  • Export summaries to Notion, Airtable, or PDF
  • Schedule it daily/weekly for recurring analysis

📒 Suggested Sticky Notes for Workflow

| Node/Section | Sticky Note Content | |--------------|---------------------| | Pick Video IDs from Google Sheet | "Triggers on new YouTube videos in your spreadsheet" | | AI Agent | "Uses OpenAI to generate an analysis summary – customize prompt as needed" | | Gmail | "Sends summary report – you can update subject, recipients, or style" | | Update Status | "Marks video as processed to avoid duplicate runs" |

📎 Required Files

| File Name | Purpose | |-----------|---------| | Youtube_Video | Google Sheet to hold YouTube video IDs and status | | Youtube_Comment_Scraper.json | Main n8n workflow export for this automation |

🧪 Testing Tips

  • Add one test video with a valid YouTube video ID and status = Pending
  • Monitor the workflow logs to confirm API responses
  • Confirm summary delivery in your inbox
  • Verify that status updates in the sheet

🏷 Suggested Tags & Categories

  • #YouTube
  • #OpenAI
  • #Automation
  • #Marketing
  • #Email
  • #Analytics

YouTube Comment Scraper & Analyzer with GPT-4o and Email Summary Report

This n8n workflow automates the process of scraping YouTube comments from a specified video, analyzing them using an AI agent (GPT-4o), and then compiling a summary report that is sent via email. It's designed to provide insights into public sentiment or common themes within a video's comment section.

What it does

  1. Triggers on new Google Sheet row: The workflow starts when a new row is added to a designated Google Sheet. This row is expected to contain the YouTube Video ID.
  2. Scrapes YouTube Comments: It fetches all comments from the YouTube video corresponding to the provided Video ID.
  3. Limits Comments (Optional): It processes a limited number of comments (defaulting to 100) to manage API usage and processing time.
  4. Analyzes Comments with AI: Each comment is then sent to an AI agent (configured with GPT-4o) for analysis. The AI agent is prompted to identify the sentiment (positive, negative, neutral) and extract key topics or themes.
  5. Formats AI Output: The AI's response for each comment is parsed to extract the sentiment and topics into a structured format.
  6. Stores Raw and Analyzed Data: The original comment, its author, and the AI-generated sentiment and topics are appended as new rows to a Google Sheet.
  7. Generates Summary Report: It constructs a comprehensive summary of the analysis, including the total number of comments, a breakdown of sentiments, and a list of the most frequent topics.
  8. Sends Email Report: Finally, the workflow sends an email containing this summary report to a specified recipient.

Prerequisites/Requirements

  • n8n Instance: A running n8n instance.
  • Google Account:
    • Access to Google Sheets for triggering the workflow and storing data.
    • Gmail account for sending the summary report.
    • YouTube API access (configured via Google OAuth 2.0 credentials in n8n) to scrape comments.
  • OpenAI API Key: An OpenAI API key with access to GPT-4o or a similar large language model. This needs to be configured as a credential in n8n for the "OpenAI Chat Model" node.
  • Google Sheets Trigger Configuration: You will need to configure the Google Sheets Trigger node to listen for new rows in your specific spreadsheet and sheet.
  • Google Sheets Node Configuration: You will need to configure the Google Sheets node to append data to your specific spreadsheet and sheet.
  • Gmail Node Configuration: You will need to configure the Gmail node with the recipient email address and sender details.
  • AI Agent Configuration: The AI Agent node is pre-configured to use the OpenAI Chat Model. Ensure your OpenAI credentials are set up correctly.

Setup/Usage

  1. Import the workflow: Download the provided JSON and import it into your n8n instance.
  2. Configure Credentials:
    • Set up your Google OAuth 2.0 credentials for Google Sheets, Gmail, and YouTube.
    • Set up your OpenAI API Key credential.
  3. Configure Google Sheets Trigger:
    • In the "Google Sheets Trigger" node, select your Google Sheet and the specific sheet where you will add YouTube Video IDs.
    • Ensure the "Operation" is set to "On New Row".
  4. Configure Google Sheets (Append) Node:
    • In the "Google Sheets" node (ID 18, named "Google Sheets"), select your Google Sheet and the sheet where you want to store the raw comments and AI analysis.
    • Map the input fields to the appropriate columns in your sheet (e.g., {{ $json.comment }}, {{ $json.author }}, {{ $json.sentiment }}, {{ $json.topics }}).
  5. Configure Gmail Node:
    • In the "Gmail" node, specify the "To" email address for the summary report.
    • Adjust the "Subject" and "Body" of the email if needed. The current body uses data generated by the AI analysis.
  6. Activate the workflow: Once configured, activate the workflow.
  7. Trigger the workflow: To run the workflow, add a new row to your configured Google Sheet with a YouTube Video ID in the designated column. The workflow will then automatically scrape comments, analyze them, store the results, and send an email summary.

This workflow provides a powerful way to gain automated insights from YouTube comments, which can be invaluable for content creators, marketers, or researchers.

Related Templates

Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets

This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitor’s webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger — Manually start the workflow or schedule it to run periodically. Input Setup — Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) — Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring — Clean and convert GPT output into JSON format. Data Storage (Google Sheets) — Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the “Set Input Fields” node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors → Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection → Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report → Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization → Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs → Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting It’s a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.

Ranjan DailataBy Ranjan Dailata
161

Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax

Spark your creativity instantly in any chat—turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. 📋 What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing 🔧 Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation 🔑 Required Credentials OpenAI API Setup Go to platform.openai.com → API keys (sidebar) Click "Create new secret key" → Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai → Dashboard → API Keys Generate a new API key → Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) ⚙️ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflow—chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions

Daniel NkenchoBy Daniel Nkencho
601

Automate invoice processing with OCR, GPT-4 & Salesforce opportunity creation

PDF Invoice Extractor (AI) End-to-end pipeline: Watch Drive ➜ Download PDF ➜ OCR text ➜ AI normalize to JSON ➜ Upsert Buyer (Account) ➜ Create Opportunity ➜ Map Products ➜ Create OLI via Composite API ➜ Archive to OneDrive. --- Node by node (what it does & key setup) 1) Google Drive Trigger Purpose: Fire when a new file appears in a specific Google Drive folder. Key settings: Event: fileCreated Folder ID: google drive folder id Polling: everyMinute Creds: googleDriveOAuth2Api Output: Metadata { id, name, ... } for the new file. --- 2) Download File From Google Purpose: Get the file binary for processing and archiving. Key settings: Operation: download File ID: ={{ $json.id }} Creds: googleDriveOAuth2Api Output: Binary (default key: data) and original metadata. --- 3) Extract from File Purpose: Extract text from PDF (OCR as needed) for AI parsing. Key settings: Operation: pdf OCR: enable for scanned PDFs (in options) Output: JSON with OCR text at {{ $json.text }}. --- 4) Message a model (AI JSON Extractor) Purpose: Convert OCR text into strict normalized JSON array (invoice schema). Key settings: Node: @n8n/n8n-nodes-langchain.openAi Model: gpt-4.1 (or gpt-4.1-mini) Message role: system (the strict prompt; references {{ $json.text }}) jsonOutput: true Creds: openAiApi Output (per item): $.message.content → the parsed JSON (ensure it’s an array). --- 5) Create or update an account (Salesforce) Purpose: Upsert Buyer as Account using an external ID. Key settings: Resource: account Operation: upsert External Id Field: taxid_c External Id Value: ={{ $json.message.content.buyer.tax_id }} Name: ={{ $json.message.content.buyer.name }} Creds: salesforceOAuth2Api Output: Account record (captures Id) for downstream Opportunity. --- 6) Create an opportunity (Salesforce) Purpose: Create Opportunity linked to the Buyer (Account). Key settings: Resource: opportunity Name: ={{ $('Message a model').item.json.message.content.invoice.code }} Close Date: ={{ $('Message a model').item.json.message.content.invoice.issue_date }} Stage: Closed Won Amount: ={{ $('Message a model').item.json.message.content.summary.grand_total }} AccountId: ={{ $json.id }} (from Upsert Account output) Creds: salesforceOAuth2Api Output: Opportunity Id for OLI creation. --- 7) Build SOQL (Code / JS) Purpose: Collect unique product codes from AI JSON and build a SOQL query for PricebookEntry by Pricebook2Id. Key settings: pricebook2Id (hardcoded in script): e.g., 01sxxxxxxxxxxxxxxx Source lines: $('Message a model').first().json.message.content.products Output: { soql, codes } --- 8) Query PricebookEntries (Salesforce) Purpose: Fetch PricebookEntry.Id for each Product2.ProductCode. Key settings: Resource: search Query: ={{ $json.soql }} Creds: salesforceOAuth2Api Output: Items with Id, Product2.ProductCode (used for mapping). --- 9) Code in JavaScript (Build OLI payloads) Purpose: Join lines with PBE results and Opportunity Id ➜ build OpportunityLineItem payloads. Inputs: OpportunityId: ={{ $('Create an opportunity').first().json.id }} Lines: ={{ $('Message a model').first().json.message.content.products }} PBE rows: from previous node items Output: { body: { allOrNone:false, records:[{ OpportunityLineItem... }] } } Notes: Converts discount_total ➜ per-unit if needed (currently commented for standard pricing). Throws on missing PBE mapping or empty lines. --- 10) Create Opportunity Line Items (HTTP Request) Purpose: Bulk create OLIs via Salesforce Composite API. Key settings: Method: POST URL: https://<your-instance>.my.salesforce.com/services/data/v65.0/composite/sobjects Auth: salesforceOAuth2Api (predefined credential) Body (JSON): ={{ $json.body }} Output: Composite API results (per-record statuses). --- 11) Update File to One Drive Purpose: Archive the original PDF in OneDrive. Key settings: Operation: upload File Name: ={{ $json.name }} Parent Folder ID: onedrive folder id Binary Data: true (from the Download node) Creds: microsoftOneDriveOAuth2Api Output: Uploaded file metadata. --- Data flow (wiring) Google Drive Trigger → Download File From Google Download File From Google → Extract from File → Update File to One Drive Extract from File → Message a model Message a model → Create or update an account Create or update an account → Create an opportunity Create an opportunity → Build SOQL Build SOQL → Query PricebookEntries Query PricebookEntries → Code in JavaScript Code in JavaScript → Create Opportunity Line Items --- Quick setup checklist 🔐 Credentials: Connect Google Drive, OneDrive, Salesforce, OpenAI. 📂 IDs: Drive Folder ID (watch) OneDrive Parent Folder ID (archive) Salesforce Pricebook2Id (in the JS SOQL builder) 🧠 AI Prompt: Use the strict system prompt; jsonOutput = true. 🧾 Field mappings: Buyer tax id/name → Account upsert fields Invoice code/date/amount → Opportunity fields Product name must equal your Product2.ProductCode in SF. ✅ Test: Drop a sample PDF → verify: AI returns array JSON only Account/Opportunity created OLI records created PDF archived to OneDrive --- Notes & best practices If PDFs are scans, enable OCR in Extract from File. If AI returns non-JSON, keep “Return only a JSON array” as the last line of the prompt and keep jsonOutput enabled. Consider adding validation on parsing.warnings to gate Salesforce writes. For discounts/taxes in OLI: Standard OLI fields don’t support per-line discount amounts directly; model them in UnitPrice or custom fields. Replace the Composite API URL with your org’s domain or use the Salesforce node’s Bulk Upsert for simplicity.

Le NguyenBy Le Nguyen
942