YouTube to Gmail, trend briefs ready to forward
YouTube “trend tracking” usually turns into a messy routine: open ten tabs, skim thumbnails, copy titles into a doc, then still miss the one video everyone’s talking about.
This YouTube Gmail automation hits marketing managers first, honestly. But agency owners chasing content angles and founders keeping an eye on competitors feel the same drag. You will get a clean, forwardable email brief with viral picks, summaries, and clear next actions.
Below, you’ll see how the workflow watches channels, checks performance (likes), generates GPT-written briefs, and sends a Gmail digest your team can use immediately.
How This Automation Works
The full n8n workflow, from trigger to final output:
n8n Workflow Template: YouTube to Gmail, trend briefs ready to forward
flowchart LR
subgraph sg0["Manual Run Flow"]
direction LR
n0@{ icon: "mdi:play-circle", form: "rounded", label: "Manual Run", pos: "b", h: 48 }
n1@{ icon: "mdi:swap-vertical", form: "rounded", label: "Set Channel IDs", pos: "b", h: 48 }
n2@{ icon: "mdi:swap-vertical", form: "rounded", label: "Split Channels", pos: "b", h: 48 }
n3@{ icon: "mdi:cog", form: "rounded", label: "Fetch Latest Videos (RSS)", pos: "b", h: 48 }
n4@{ icon: "mdi:swap-horizontal", form: "rounded", label: "Filter: Published in Last 72h", 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 Video Stats (YouTube API)"]
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/>Classify by Likes (Code)"]
n7@{ icon: "mdi:swap-horizontal", form: "rounded", label: "Branch: Normal", pos: "b", h: 48 }
n8@{ icon: "mdi:swap-horizontal", form: "rounded", label: "Branch: Viral", pos: "b", h: 48 }
n9@{ icon: "mdi:robot", form: "rounded", label: "Write Post (Normal)", pos: "b", h: 48 }
n10@{ icon: "mdi:robot", form: "rounded", label: "Write Post (Viral)", pos: "b", h: 48 }
n11["<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/>Aggregate Posts for Briefing"]
n12@{ icon: "mdi:robot", form: "rounded", label: "Generate Weekly Briefing (HT..", pos: "b", h: 48 }
n13@{ icon: "mdi:message-outline", form: "rounded", label: "Send Weekly Briefing (Gmail)", pos: "b", h: 48 }
n0 --> n1
n8 --> n10
n7 --> n9
n2 --> n3
n1 --> n2
n10 --> n11
n9 --> n11
n6 --> n8
n6 --> n7
n3 --> n4
n11 --> n12
n4 --> n5
n5 --> n6
n12 --> n13
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 n9,n10,n12 ai
class n4,n7,n8 decision
class n5 api
class n6,n11 code
classDef customIcon fill:none,stroke:none
class n5,n6,n11 customIcon
The Problem: YouTube “research” is invisible busywork
Keeping up with YouTube uploads sounds simple until you do it across multiple channels and multiple teammates. Someone checks the feed. Someone else grabs stats. Then you’re copying links into Slack or a doc, and the details get lost (like counts, publish dates, why it matters, what to do next). A week later, you can’t tell what was actually “viral” versus what just looked interesting in the moment. And the worst part? You still have to write the summary, which means your “research” time steals from real work like planning campaigns or producing content.
It adds up fast. Here’s where it breaks down in practice.
- You end up checking the same channels repeatedly, because nobody trusts the last update is complete.
- Video performance gets judged by vibes instead of a simple rule (like “at least 1,000 likes”).
- Summaries are inconsistent, so forwarding the “brief” to a client or teammate feels risky.
- Manual tracking makes it hard to compare week over week, which means trend signals get missed.
The Solution: Auto-classify uploads and email a weekly brief
This workflow monitors a list of YouTube channels, pulls recent uploads, and filters down to what’s actually new (published in the last 72 hours). For each video, it fetches YouTube stats through the API, then classifies the video as “viral” or “normal” based on a clear threshold: 1,000 likes. From there, GPT generates two styles of content: punchy LinkedIn-style notes for viral videos, and a more standard summary for normal ones. Finally, everything gets combined into a Gmail-friendly HTML briefing that arrives as one clean email you can forward to your team or clients.
The workflow starts with a channel list you control. It then pulls new items via RSS, enriches them with API stats, and uses OpenAI to turn raw video data into short, usable briefs. Gmail sends the final digest, so the output lands where your team already works.
What You Get: Automation vs. Results
| What This Workflow Automates | Results You’ll Get |
|---|---|
|
|
Example: What This Looks Like
Say you track 12 competitor and creator channels. Manually, a weekly review often means roughly 10 minutes per channel to scan uploads, open videos, and jot down notes, which is about 2 hours before you’ve even written a digest. Add another 30 minutes to turn notes into something forwardable. With this workflow, you spend maybe 10 minutes once to set your channel IDs and recipients, then the brief shows up in Gmail after it processes. The “research + writing” becomes “read one email,” which is a very different week.
What You’ll Need
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- YouTube Data API v3 for video stats and like counts
- OpenAI (GPT-4 family) to generate summaries and the HTML brief
- Gmail (OAuth2) to send the weekly briefing email
- YouTube API key (create it in Google Cloud Console → APIs & Services)
Skill level: Intermediate. You’ll paste API keys, connect Gmail OAuth, and edit a few fields like channel IDs and recipients.
Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).
How It Works
You decide when it runs. The template is set up for manual execution in n8n, but it’s built so you can run it on a schedule once you’re happy with the output. Weekly is common for briefs, and daily works if your niche moves fast.
New uploads get collected and filtered. n8n reads each channel’s RSS feed, then keeps only videos published within the last 72 hours. That one filter prevents stale content from polluting your brief.
Stats get pulled and the “viral” rule gets applied. For every recent video, the workflow calls the YouTube Data API to fetch snippet and statistics, including likeCount. A small logic step labels each video “viral” when it hits 1,000 likes (you can change the threshold).
GPT writes the parts people actually want to read. Viral videos get a punchier LinkedIn-style angle, normal ones get a more standard summary. Those outputs are merged into one block, then GPT generates a Gmail-robust HTML email that’s clean on desktop and mobile.
You can easily modify the viral threshold to match your niche, or change the writing style to match your brand voice. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Manual Execution Trigger
Start the workflow with a manual trigger so you can test the full briefing pipeline on demand.
- Add the Manual Execution Start node as the trigger for this workflow.
- Ensure Manual Execution Start connects directly to Assign Channel Identifiers.
Step 2: Connect the YouTube Channel Inputs
Define which YouTube channels to monitor and split them into individual items for processing.
- In Assign Channel Identifiers, set the ChannelID array to your channel IDs:
["[YOUR_ID]","[YOUR_ID]","[YOUR_ID]","[YOUR_ID]"]. - In Divide Channel List, set Field to Split Out to
ChannelID. - In Retrieve Recent Videos RSS, set URL to
=https://www.youtube.com/feeds/videos.xml?channel_id={{ $json.ChannelID }}.
Step 3: Filter Recent Videos and Fetch Metrics
Only process videos from the last 72 hours and then retrieve their official metrics from YouTube.
- In Validate 72h Publishing, set the date comparison to keep videos after
{{ new Date(Date.now() - 72*60*60*1000).toISOString() }}using{{ new Date($json.pubDate) }}as the left value. - In Fetch YouTube Video Metrics, set URL to
https://www.googleapis.com/youtube/v3/videos. - In Fetch YouTube Video Metrics, enable Send Query and set query parameters: id to
{{ $json.link.includes('shorts') ? $json.link.split('/shorts/')[1] : $json.link.split('v=')[1].split('&')[0] }}and part tosnippet,statistics. - Credential Required: Connect your httpQueryAuth credentials to Fetch YouTube Video Metrics.
Step 4: Classify and Route Content in Parallel
Classify videos by like count, then route them into viral and normal paths simultaneously.
- In Like-Based Classification, keep the provided JavaScript to categorize videos using the
THRESHOLD = 1000like-count rule. - Confirm Like-Based Classification outputs to both Route Viral Content and Route Normal Content in parallel.
- In Route Viral Content, ensure the Viral Video output uses
{{ $json.classification }}equalsviral. - In Route Normal Content, ensure the Normal Video output uses
{{ $json.classification }}equalsnormal.
unknown, verify the YouTube API response includes statistics.likeCount in Fetch YouTube Video Metrics.Step 5: Generate Posts and Build the Weekly Brief
Compose AI-generated posts for viral and normal videos, then compile them into a single HTML briefing.
- In Compose Viral Post, keep the model set to
gpt-4.1-miniand confirm the prompt references{{ $json.title }},{{ $json.classification }}, and{{ $json.original.snippet.description }}. - Credential Required: Connect your openAiApi credentials to Compose Viral Post.
- In Compose Standard Post, keep the model set to
gpt-4.1-miniand confirm the prompt references{{ $json.title }},{{ $json.classification }}, and{{ $json.original.snippet.description }}. - Credential Required: Connect your openAiApi credentials to Compose Standard Post.
- In Combine Posts for Brief, keep the aggregation logic that builds
weekly_summary_inputfromchoices[0].message.content. - In Create Weekly HTML Brief, keep the model set to
gpt-5and confirm the prompt uses{{ $json.weekly_summary_input }}. - Credential Required: Connect your openAiApi credentials to Create Weekly HTML Brief.
Step 6: Configure the Email Output
Send the compiled HTML brief to your inbox using Gmail.
- In Dispatch Weekly Briefing Email, set Send To to your recipient email address.
- Set Subject to
Weekly AI Briefing. - Set Message to
{{ $json.choices[0].message.content }}. - Credential Required: Connect your gmailOAuth2 credentials to Dispatch Weekly Briefing Email.
Step 7: Test and Activate Your Workflow
Run a manual test to confirm the workflow generates posts and sends the weekly brief, then activate it for ongoing use.
- Click Execute Workflow on Manual Execution Start to run a full test.
- Verify that Compose Viral Post and Compose Standard Post produce text, and Create Weekly HTML Brief outputs HTML starting with
<!DOCTYPE html>. - Confirm the email arrives from Dispatch Weekly Briefing Email with the formatted HTML content.
- Toggle the workflow to Active when you are ready for production use.
Common Gotchas
- YouTube Data API credentials can fail quietly if the key is restricted or missing permissions. If likeCount comes back empty, check your Google Cloud Console API restrictions first.
- If you add Wait nodes or rely on slower external calls, processing times vary. Bump up the wait duration if downstream nodes fail because they received an empty stats response.
- Default prompts in the OpenAI nodes are usable but generic. Add your brand voice and formatting rules early, or you will be editing every briefing before you forward it.
Frequently Asked Questions
About 30 minutes if your API keys and Gmail login are ready.
No. You’ll mostly paste credentials and edit a channel list. The only “code” piece is already included for the viral classification logic.
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 API usage (usually a few dollars a month for weekly briefs) and YouTube Data API quotas.
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 it’s a common tweak. Replace the manual trigger with a schedule trigger, then adjust the “published in last 72 hours” filter down to 24 hours. Many teams also change the email subject line and shorten the GPT output so the daily brief stays scannable.
Usually it’s a YouTube Data API key issue: the key is restricted, the API isn’t enabled in Google Cloud, or the request isn’t pulling statistics so likeCount comes back missing. Regenerate the key if needed, then confirm the workflow request includes part=snippet,statistics. If it works in testing but fails in bulk, you may be hitting quota limits and need to slow down channel volume or run less frequently.
If you self-host n8n, execution volume depends mostly on your server and your YouTube API quota. On n8n Cloud, the limit is based on your plan’s monthly executions, and this workflow can use multiple executions per run if you track lots of channels. In practical terms, many teams run 10–30 channels comfortably, then tune it (batching, scheduling, fewer days in the filter) as they scale.
For this use case, n8n is usually the better fit because you can branch logic (viral vs normal), merge content, and generate a formatted HTML email without paying extra for every “path.” It’s also easier to self-host, which matters if you run this a lot. Zapier and Make can still do it, but you’ll often end up stitching together more steps and living with less control over formatting. If you’re on a tight timeline and don’t want to compare options, Talk to an automation expert and we’ll point you in the right direction.
One good brief can set your whole week up. Set this up once, and the workflow keeps your team ahead without the constant checking and summarizing.
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.
