YouTube to Google Sheets, competitor metrics logged

Checking competitor channels by hand is the kind of “quick task” that quietly eats your week. You bounce between tabs, copy titles, grab view counts, paste into a sheet, then realize you missed five uploads.

This YouTube Sheets automation hits content marketers first, but solo creators and small agency teams feel it too. You get a clean, consistent spreadsheet of titles, views, likes, descriptions, URLs, plus a simple engagement rate, without babysitting YouTube.

Below, you’ll see exactly what the workflow collects, how it turns a channel name into rows in Google Sheets, and what you can tweak so it matches how you plan content.

How This Automation Works

The full n8n workflow, from trigger to final output:

n8n Workflow Template: YouTube to Google Sheets, competitor metrics logged

Click to explore

flowchart LR

    subgraph sg0["Form Entry Flow"]
        direction LR
        n0["<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/form.svg' width='40' height='40' /></div><br/>Form Entry Trigger"]
        n1@{ icon: "mdi:swap-vertical", form: "rounded", label: "Assign Input Variables", 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/httprequest.dark.svg' width='40' height='40' /></div><br/>Retrieve Channel Identifier"]
        n3["<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/>Parse Channel Identifier"]
        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 Video Identifiers"]
        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/code.svg' width='40' height='40' /></div><br/>Parse Video Identifiers"]
        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/>Retrieve Video Details"]
        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/>Map Video Metrics"]
        n8["<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/>Create Hook Snippet"]
        n9["<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/>Compute Engagement Rate"]
        n10@{ icon: "mdi:database", form: "rounded", label: "Append Sheet Records", pos: "b", h: 48 }
        n5 --> n6
        n4 --> n5
        n2 --> n3
        n6 --> n7
        n1 --> n2
        n9 --> n10
        n3 --> n4
        n7 --> n8
        n0 --> n1
        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 n10 database
    class n2,n4,n6 api
    class n3,n5,n7,n8,n9 code
    classDef customIcon fill:none,stroke:none
    class n0,n2,n3,n4,n5,n6,n7,n8,n9 customIcon

The Problem: Competitor tracking turns into endless busywork

You want real data before you commit to your next video. So you open a competitor’s channel, scan recent uploads, and start collecting titles and view counts. Then you do it again for a second channel. Then a third. By the time your spreadsheet is “updated,” the numbers are already stale, the formatting is inconsistent, and you’re not even sure you captured the right URL for that one video that popped off last week. Honestly, the worst part is the mental load. You’re doing clerical work when you should be planning hooks, thumbnails, and angles.

It adds up fast. Here’s where it breaks down in day-to-day use.

Manually collecting titles, views, and likes across a few channels can burn about 2 hours a week, and that’s before you do any analysis.
You end up with messy rows (different columns, missing URLs), which makes comparisons feel unreliable.
When you copy numbers from the UI, it’s easy to misread or paste the wrong metric into the wrong cell.
Without a repeatable process, you can’t spot trends early, so you react late instead of planning ahead.

The Solution: Log competitor YouTube metrics to Google Sheets automatically

This workflow turns competitor research into a simple input and a reliable output. You submit a YouTube channel name through an n8n form, and the automation takes over. First, it finds the channel’s identifier using the YouTube Data API, then pulls a list of recent video IDs from that channel. After that, it requests detailed stats for each video, maps the fields you actually care about (title, views, likes, description, URL), and computes a basic engagement rate so you can compare videos faster. Finally, it appends everything as neat rows in Google Sheets, so each run adds fresh data without wrecking your structure.

The workflow starts with a form entry. It then moves through “find channel,” “fetch videos,” and “enrich each video with metrics,” and ends by writing consistent records to Google Sheets. No scraping, no copy-paste, no “wait, which tab was that?”

What You Get: Automation vs. Results

What This Workflow Automates

Results You’ll Get

Accepting a channel name from a simple n8n form.
Looking up the channel ID and collecting recent video IDs via HTTP requests.
Pulling video titles, views, likes, descriptions, and building the video URL.
Generating a hook snippet and calculating an engagement rate before saving.

Most teams get about 2 hours back each week once this runs on schedule.
You can compare channels with consistent columns and consistent rows.
Trend-spotting becomes a spreadsheet filter, not a research session.
Fewer errors, because the data is pulled from the API, not your clipboard.
A repeatable log you can use for content planning meetings and briefs.

Example: What This Looks Like

Say you track 5 competitor channels and log the last 20 videos for each one. Manually, even at about 2 minutes per video to copy the title, views, likes, and URL, that’s roughly 200 minutes (over 3 hours) every time you “update the sheet.” With this workflow, you submit the channel name once, let n8n fetch and map the metrics, then it appends rows automatically. The hands-on time drops to a couple minutes, and the waiting happens in the background.

What You’ll Need

n8n instance (try n8n Cloud free)
Self-hosting option if you prefer (Hostinger works well)
Google Sheets for storing competitor video rows
YouTube Data API to fetch channel and video metrics
YouTube Data API key (get it from Google Cloud Console)

Skill level: Beginner. You’ll connect Google Sheets, paste an API key into credentials, and match your sheet columns.

Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).

How It Works

Form submission trigger. You enter a channel name (or handle) in an n8n form, which means anyone on your team can run the tracker without touching the workflow.

Channel lookup and video discovery. n8n sends an HTTP request to the YouTube Data API to find the channel identifier, then requests a list of recent video IDs from that channel.

Metrics enrichment plus light analysis. For each video ID, the workflow pulls details, maps the fields into a clean structure, creates a “hook snippet” from the content, and calculates engagement rate so the sheet is analysis-ready.

Google Sheets logging. The final node appends records into your spreadsheet, keeping a consistent row format (Title, Views, Likes, Description, URL, plus your computed fields).

You can easily modify which metrics are captured to match your reporting style. See the full implementation guide below for customization options.

Step-by-Step Implementation Guide

Step 1: Configure the Form Trigger

Set up the form input that starts the workflow and collects channel search parameters.

Add the Form Entry Trigger node as your workflow trigger.
Set Form Title to YouTube Channel Analyzer.
Set Form Description to Fetch trending videos from a specific channel.
Configure form fields for Format (dropdown with short, medium, long), Number of Videos (number), and Channel Name (text).
Connect Form Entry Trigger to Assign Input Variables.

Tip: Make sure the form field labels match exactly: Format, Number of Videos, and Channel Name, since downstream expressions reference them.

Step 2: Connect Google Sheets

Configure the output destination for storing video metrics in a spreadsheet.

Add the Append Sheet Records node.
Credential Required: Connect your googleSheetsOAuth2Api credentials.
Set Operation to append.
Choose the target spreadsheet in Document and the worksheet in Sheet Name (e.g., Sheet1).
Map the columns using the expressions provided, including {{$json.hook}}, {{$json.title}}, {{$json.videoURL}}, {{$json.likeCount}}, {{$json.thumbnail}}, {{$json.viewCount}}, {{$json.description}}, {{$json.performance}}, {{$json.channelTitle}}, and {{$json.commentCount}}.

⚠️ Common Pitfall: The sheet must already contain headers matching the mapped column IDs (e.g., channelTitle, title, description, viewCount, etc.).

Step 3: Set Up Input Variables and YouTube API Requests

Collect the form inputs, assign the API key, and fetch the channel and video identifiers from YouTube.

In Assign Input Variables, set api_key to [CONFIGURE_YOUR_API_KEY].
Set format to {{$json.Format}}, videoLimit to {{$json['Number of Videos']}}, and channel_name to {{$json['Channel Name']}}.
In Retrieve Channel Identifier, set URL to https://www.googleapis.com/youtube/v3/search and enable Send Query.
Configure Query Parameters in Retrieve Channel Identifier: part=snippet, type=channel, q={{ $json.channel_name }}, key=[CONFIGURE_YOUR_API_KEY].
In Fetch Video Identifiers, set URL to https://www.googleapis.com/youtube/v3/search and Send Query to true.
Configure Query Parameters in Fetch Video Identifiers: part=snippet, maxResults={{ $json.videoLimit || 5 }}, order=viewCount, channelId={{ $json.channelId }}, type=video, videoDuration={{ $json.format }}, key=[CONFIGURE_YOUR_API_KEY], regionCode=US.

⚠️ Common Pitfall: YouTube API credentials are not configured as node credentials here—replace [CONFIGURE_YOUR_API_KEY] with your actual API key in Assign Input Variables, Retrieve Channel Identifier, Fetch Video Identifiers, and Retrieve Video Details.

Step 4: Set Up Processing Nodes (Parsing, Metrics, and Hooks)

Process identifiers, fetch video details, and compute metrics before outputting to Google Sheets.

In Parse Channel Identifier, keep the JavaScript code as provided to output channelId.
In Parse Video Identifiers, keep the JavaScript code that extracts videoid from the search results.
In Retrieve Video Details, set URL to https://www.googleapis.com/youtube/v3/videos and include query parameters part=snippet,statistics, id={{ $json.videoid }}, and key=[CONFIGURE_YOUR_API_KEY].
In Map Video Metrics, keep the JavaScript code that maps channelTitle, title, description, viewCount, likeCount, commentCount, videoURL, and thumbnail.
In Create Hook Snippet, keep the JavaScript code that extracts the first 15 words from description into hook.
In Compute Engagement Rate, keep the JavaScript code that calculates performance from views, likes, and comments.

Tip: This workflow uses 5 code nodes. Keep the scripts as-is unless you need to modify the data schema sent to Append Sheet Records.

Step 5: Test and Activate Your Workflow

Verify that the workflow returns video data and appends it to your spreadsheet.

Click Execute Workflow and submit the Form Entry Trigger with a valid channel name.
Confirm that Assign Input Variables outputs your API key and inputs correctly.
Check that Retrieve Channel Identifier and Fetch Video Identifiers return valid results from YouTube.
Verify that Append Sheet Records appends rows containing title, videoURL, performance, and hook values.
Once successful, toggle the workflow Active to enable production use.

🔒

Unlock Full Step-by-Step Guide

Get the complete implementation guide + downloadable template

Common Gotchas

YouTube Data API credentials can expire or be restricted by project settings. If things break, check your Google Cloud Console API key restrictions and quota first.
If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
Default prompts in AI nodes are generic. Add your brand voice early or you’ll be editing outputs forever.

Frequently Asked Questions

How long does it take to set up this YouTube Sheets automation automation?

About 30 minutes if your API key and sheet are ready.

Do I need coding skills to automate YouTube Sheets automation?

No. You’ll mostly connect accounts and paste your YouTube API key into the right credential field.

Is n8n free to use for this YouTube Sheets automation workflow?

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 Data API usage (it’s quota-based inside Google Cloud).

Where can I host n8n to run this automation?

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.

Can I customize this YouTube Sheets automation workflow for tracking comments and publish dates?

Yes, but you’ll make a small change. You can extend the Code nodes that parse video details (like “Map Video Metrics”) to include publish date and comment count, then add new columns in Google Sheets so the Append step writes them. Many teams also filter by keywords during the “Parse Video Identifiers” stage so they only log videos related to a topic. If you want richer analysis, you can tweak the “Create Hook Snippet” logic to produce a summary or angle, not just a snippet.

Why is my YouTube Data API connection failing in this workflow?

Usually it’s an API key restriction or quota issue in Google Cloud Console, not n8n itself. Regenerate the key, confirm YouTube Data API v3 is enabled, then verify the key is allowed to call that API. Also check that the workflow isn’t sending a channel “handle” where the API expects a different identifier format, because that can look like a connection problem when it’s really a lookup failure.

How many videos can this YouTube Sheets automation automation handle?

It depends more on your YouTube API quota than n8n. On self-hosted n8n there’s no execution limit, but each run can consume quota quickly if you pull a lot of videos across multiple channels, so most people start with “recent uploads only” and scale up.

Is this YouTube Sheets automation automation better than using Zapier or Make?

Often, yes, because this kind of workflow needs multiple API calls, data parsing, and some logic before it’s ready for Sheets. n8n handles branching and code steps cleanly, and self-hosting can make high-volume tracking affordable. Zapier or Make can still work if you keep it simple, but you may hit limits when you try to process lots of videos or reshape the data. Another practical point: with n8n, your workflow is easier to audit when numbers look off, because you can inspect each node’s output. If you’re unsure, Talk to an automation expert and get a recommendation based on how many channels you track.

Competitor research should feel like a dashboard, not a chore. Set this up once, and your sheet stays ready for planning whenever you are.

YouTube to Google Sheets, competitor metrics logged

How This Automation Works

n8n Workflow Template: YouTube to Google Sheets, competitor metrics logged

The Problem: Competitor tracking turns into endless busywork