HumationHuman + Automation
Back to Catalog

🎦🚀 YouTube video comment analysis agent

Joseph LePageJoseph LePage
4860 views
2/3/2026
shopifyecommercegoogle driveautomationcsv
Official Page

🎦🚀 YouTube Video Comment Analysis Agent

This n8n workflow is designed to help YouTube creators analyze video details and comments to generate a comprehensive and actionable report. The workflow provides insights into video performance, audience engagement, and viewer feedback, helping creators identify trends, interests, and opportunities for future content creation.

✨ Key Features

  1. Video Performance Analysis: Extracts metrics like views, likes, and comments to evaluate the video's success.
  2. Comment Sentiment Analysis: Determines the tone of comments (positive, neutral, or negative) to understand audience sentiment.
  3. Recurring Themes Detection: Identifies common topics or questions in comments to highlight viewer interests.
  4. Engagement Drivers: Pinpoints what aspects of the video resonated most with viewers.
  5. Actionable Recommendations: Offers strategies for creating follow-up content or improving future videos.
  6. Keyword Suggestions: Extracts frequently mentioned terms for better discoverability on YouTube.
  7. Collaboration Opportunities: Suggests potential partnerships based on viewer feedback or related channels.

🛠️ How to Use

  1. Set Up Workflow Variables:

    • Add your GOOGLE_API_KEY and the VIDEO_ID of the YouTube video you want to analyze in the "Workflow Variables" node.
    • Ensure your Google API key has access to the YouTube Data API.

  2. Run the Workflow:

    • Trigger the workflow manually or through another workflow using the "Execute Workflow Trigger" node.
    • The workflow will fetch video details and comments using pagination to ensure all data is captured.

  3. Generate Insights:

    • The workflow processes video details and comments to create a detailed report with actionable insights.
    • Outputs include sentiment analysis, engagement drivers, content opportunities, and audience profiling.

  4. View or Share Results:

    • The report is converted into Markdown and can be emailed via Gmail or saved to Google Drive as a document.

🌟 Value from This Workflow

  • Gain a deeper understanding of your audience's preferences and feedback.
  • Identify trends and engagement drivers to replicate success in future videos.
  • Discover new content opportunities based on viewer questions and suggestions.
  • Improve discoverability by leveraging keyword suggestions extracted from comments.
  • Build stronger connections with your audience by addressing their needs effectively.

YouTube Video Comment Analysis Agent

This n8n workflow acts as an AI agent to analyze comments from a YouTube video, summarize them, and potentially save the analysis to Google Drive or send it via Gmail. It's designed to automate the process of understanding public sentiment or key discussion points within a video's comment section.

What it does

This workflow automates the following steps:

  1. Trigger: It can be triggered manually or by another workflow.
  2. Fetch YouTube Comments: It makes an HTTP request to a specified URL (likely a YouTube API endpoint or a custom service) to retrieve video comments.
  3. Process Comments: It then uses a Code node to process the raw comment data.
  4. AI Analysis: The core of the workflow uses an "AI Agent" (likely powered by LangChain and an OpenAI Chat Model) to analyze the comments. This agent is configured to use tools like "HTTP Request," "Google Drive," and "Gmail" for its operations.
  5. Summarize: The AI agent's output is then summarized using a Markdown node.
  6. Data Aggregation: An "Aggregate" node is used to combine data, and a "Split Out" node is used to process individual items, indicating flexible data handling before or after AI processing.
  7. Output Options: The final analysis can be:
    • Saved to Google Drive.
    • Sent as an email via Gmail.
    • Presented as a Markdown summary.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running instance of n8n.
  • OpenAI API Key: For the "OpenAI Chat Model" used by the AI Agent. This will require an OpenAI credential in n8n.
  • Google Drive Account: If you intend to save the analysis to Google Drive. This will require a Google Drive credential in n8n.
  • Gmail Account: If you intend to send the analysis via Gmail. This will require a Gmail credential in n8n.
  • YouTube Video ID/URL: The specific YouTube video whose comments you want to analyze. This will be an input to the workflow.
  • HTTP Request Configuration: The "HTTP Request" node needs to be configured correctly to fetch comments. This might involve a YouTube Data API key or a custom endpoint.

Setup/Usage

  1. Import the Workflow: Import the provided JSON into your n8n instance.
  2. Configure Credentials:
    • Set up an OpenAI API Key credential for the "OpenAI Chat Model" node.
    • Set up a Google Drive credential for the "Google Drive" node (if used).
    • Set up a Gmail credential for the "Gmail" node (if used).
  3. Configure HTTP Request:
    • Edit the "HTTP Request" node (Node ID 19) to correctly fetch comments from your target YouTube video. This will likely involve setting the URL and any necessary authentication (e.g., YouTube Data API key).
  4. Configure AI Agent:
    • Review the "AI Agent" node (Node ID 1119) and "OpenAI Chat Model" node (Node ID 1153) to ensure the desired AI model and agent configuration are set.
  5. Run the Workflow:
    • You can execute the workflow manually by clicking "Execute workflow" on the "Manual Trigger" node.
    • Alternatively, if configured, it can be triggered by another workflow using the "Execute Workflow Trigger" node.
  6. Review Output: Check the output of the "Markdown" node for the summarized analysis, or verify if the analysis was saved to Google Drive or sent via Gmail as configured.

Related Templates

Two-way property repair management system with Google Sheets & Drive

This workflow automates the repair request process between tenants and building managers, keeping all updates organized in a single spreadsheet. It is composed of two coordinated workflows, as two separate triggers are required — one for new repair submissions and another for repair updates. A Unique Unit ID that corresponds to individual units is attributed to each request, and timestamps are used to coordinate repair updates with specific requests. General use cases include: Property managers who manage multiple buildings or units. Building owners looking to centralize tenant repair communication. Automation builders who want to learn multi-trigger workflow design in n8n. --- ⚙️ How It Works Workflow 1 – New Repair Requests Behind the Scenes: A tenant fills out a Google Form (“Repair Request Form”), which automatically adds a new row to a linked Google Sheet. Steps: Trigger: Google Sheets rowAdded – runs when a new form entry appears. Extract & Format: Collects all relevant form data (address, unit, urgency, contacts). Generate Unit ID: Creates a standardized identifier (e.g., BUILDING-UNIT) for tracking. Email Notification: Sends the building manager a formatted email summarizing the repair details and including a link to a Repair Update Form (which activates Workflow 2). --- Workflow 2 – Repair Updates Behind the Scenes:\ Triggered when the building manager submits a follow-up form (“Repair Update Form”). Steps: Lookup by UUID: Uses the Unit ID from Workflow 1 to find the existing row in the Google Sheet. Conditional Logic: If photos are uploaded: Saves each image to a Google Drive folder, renames files consistently, and adds URLs to the sheet. If no photos: Skips the upload step and processes textual updates only. Merge & Update: Combines new data with existing repair info in the same spreadsheet row — enabling a full repair history in one place. --- 🧩 Requirements Google Account (for Forms, Sheets, and Drive) Gmail/email node connected for sending notifications n8n credentials configured for Google API access --- ⚡ Setup Instructions (see more detail in workflow) Import both workflows into n8n, then copy one into a second workflow. Change manual trigger in workflow 2 to a n8n Form node. Connect Google credentials to all nodes. Update spreadsheet and folder IDs in the corresponding nodes. Customize email text, sender name, and form links for your organization. Test each workflow with a sample repair request and a repair update submission. --- 🛠️ Customization Ideas Add Slack or Telegram notifications for urgent repairs. Auto-create folders per building or unit for photo uploads. Generate monthly repair summaries using Google Sheets triggers. Add an AI node to create summaries/extract relevant repair data from repair request that include long submissions.

Matt@VeraisonLabsBy Matt@VeraisonLabs
208

Send WooCommerce cross-sell offers to customers via WhatsApp using Rapiwa API

Who Is This For? This n8n workflow enables automated cross-selling by identifying each WooCommerce customer's most frequently purchased product, finding a related product to recommend, and sending a personalized WhatsApp message using the Rapiwa API. It also verifies whether the user's number is WhatsApp-enabled before sending, and logs both successful and unsuccessful attempts to Google Sheets for tracking. What This Workflow Does Retrieves all paying customers from your WooCommerce store Identifies each customer's most purchased product Finds the latest product in the same category as their most purchased item Cleans and verifies customer phone numbers for WhatsApp compatibility Sends personalized WhatsApp messages with product recommendations Logs all activities to Google Sheets for tracking and analysis Handles both verified and unverified numbers appropriately Key Features Customer Segmentation: Automatically identifies paying customers from your WooCommerce store Product Analysis: Determines each customer's most purchased product Smart Recommendations: Finds the latest products in the same category as customer favorites WhatsApp Integration: Uses Rapiwa API for message delivery Phone Number Validation: Verifies WhatsApp numbers before sending messages Dual Logging System: Tracks both successful and failed message attempts in Google Sheets Rate Limiting: Uses batching and wait nodes to prevent API overload Personalized Messaging: Includes customer name and product details in messages Requirements WooCommerce store with API access Rapiwa account with API access for WhatsApp verification and messaging Google account with Sheets access Customer phone numbers in WooCommerce (stored in billing.phone field) How to Use — Step-by-Step Setup Credentials Setup WooCommerce API: Configure WooCommerce API credentials in n8n (e.g., "WooCommerce (get customer)" and "WooCommerce (get customer data)") Rapiwa Bearer Auth: Create an HTTP Bearer credential with your Rapiwa API token Google Sheets OAuth2: Set up OAuth2 credentials for Google Sheets access Configure Google Sheets Ensure your sheet has the required columns as specified in the Google Sheet Column Structure section Verify Code Nodes Code (get paying_customer): Filters customers to include only those who have made purchases Get most buy product id & Clear Number: Identifies the most purchased product and cleans phone numbers Configure HTTP Request Nodes Get customer data: Verify the WooCommerce API endpoint for retrieving customer orders Get specific product data: Verify the WooCommerce API endpoint for product details Get specific product recommend latest product: Verify the WooCommerce API endpoint for finding latest products by category Check valid WhatsApp number Using Rapiwa: Verify the Rapiwa endpoint for WhatsApp number validation Rapiwa Sender: Verify the Rapiwa endpoint for sending messages Google Sheet Required Columns You’ll need two Google Sheets (or two tabs in one spreadsheet): A Google Sheet formatted like this ➤ sample The workflow uses a Google Sheet with the following columns to track coupon distribution: Both must have the following headers (match exactly): | name | number | email | address1 | price | suk | title | product link | validity | staus | | ---------- | ------------- | ----------------------------------------------- | ----------- | ----- | --- | ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------- | -------- | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | verified | sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | unverified | not sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | verified | sent | Important Notes Phone Number Format: The workflow cleans phone numbers by removing all non-digit characters. Ensure your WooCommerce phone numbers are in a compatible format. API Rate Limits: Rapiwa and WooCommerce APIs have rate limits. Adjust batch sizes and wait times accordingly. Data Privacy: Ensure compliance with data protection regulations when sending marketing messages. Error Handling: The workflow logs unverified numbers but doesn't have extensive error handling. Consider adding error notifications for failed API calls. Product Availability: The workflow recommends the latest product in a category, but doesn't check if it's in stock. Consider adding stock status verification. Testing: Always test with a small batch before running the workflow on your entire customer list. Useful Links Dashboard: https://app.rapiwa.com Official Website: https://rapiwa.com Documentation: https://docs.rapiwa.com Support & Help WhatsApp: Chat on WhatsApp Discord: SpaGreen Community Facebook Group: SpaGreen Support Website: https://spagreen.net Developer Portfolio: Codecanyon SpaGreen

RapiwaBy Rapiwa
183

Track SDK documentation drift with GitHub, Notion, Google Sheets, and Slack

📊 Description Automatically track SDK releases from GitHub, compare documentation freshness in Notion, and send Slack alerts when docs lag behind. This workflow ensures documentation stays in sync with releases, improves visibility, and reduces version drift across teams. 🚀📚💬 What This Template Does Step 1: Listens to GitHub repository events to detect new SDK releases. 🧩 Step 2: Fetches release metadata including version, tag, and publish date. 📦 Step 3: Logs release data into Google Sheets for record-keeping and analysis. 📊 Step 4: Retrieves FAQ or documentation data from Notion. 📚 Step 5: Merges GitHub and Notion data to calculate documentation drift. 🔍 Step 6: Flags SDKs whose documentation is over 30 days out of date. ⚠️ Step 7: Sends detailed Slack alerts to notify responsible teams. 🔔 Key Benefits ✅ Keeps SDK documentation aligned with product releases ✅ Prevents outdated information from reaching users ✅ Provides centralized release tracking in Google Sheets ✅ Sends real-time Slack alerts for overdue updates ✅ Strengthens DevRel and developer experience operations Features GitHub release trigger for real-time monitoring Google Sheets logging for tracking and auditing Notion database integration for documentation comparison Automated drift calculation (days since last update) Slack notifications for overdue documentation Requirements GitHub OAuth2 credentials Notion API credentials Google Sheets OAuth2 credentials Slack Bot token with chat:write permissions Target Audience Developer Relations (DevRel) and SDK engineering teams Product documentation and technical writing teams Project managers tracking SDK and doc release parity Step-by-Step Setup Instructions Connect your GitHub account and select your SDK repository. Replace YOURGOOGLESHEETID and YOURSHEET_GID with your tracking spreadsheet. Add your Notion FAQ database ID. Configure your Slack channel ID for alerts. Run once manually to validate setup, then enable automation.

Rahul JoshiBy Rahul Joshi
31