Slack + Google Sheets: approve YouTube summaries fast
YouTube uploads happen fast. Keeping up with summaries, approvals, and posting without letting quality slip is where things usually break, especially once you’re monitoring more than one channel.
Marketing managers feel it when “we’ll post it later” turns into a backlog. Content leads see it in inconsistent voice. And agency teams juggling client channels need Slack Sheets approvals so publishing doesn’t depend on one person being online.
This workflow turns new YouTube uploads into AI-written summaries, routes them through Slack for a quick approve/reject decision, and logs the final result in Google Sheets. You’ll see exactly what it does, why it matters, and how to customize it without getting buried in technical details.
How This Automation Works
Here’s the complete workflow you’ll be setting up:
n8n Workflow Template: Slack + Google Sheets: approve YouTube summaries fast
flowchart LR
subgraph sg0["YouTube RSS Flow"]
direction LR
n0@{ icon: "mdi:play-circle", form: "rounded", label: "YouTube RSS Trigger", pos: "b", h: 48 }
n1["<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/>Extract Channel ID"]
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/>Fetch Video Details"]
n3@{ icon: "mdi:robot", form: "rounded", label: "Summarize Agent", pos: "b", h: 48 }
n4@{ icon: "mdi:brain", form: "rounded", label: "OpenAI GPT Summary Model", pos: "b", h: 48 }
n5@{ icon: "mdi:database", form: "rounded", label: "Store results to Google Sheet", pos: "b", h: 48 }
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/slack.svg' width='40' height='40' /></div><br/>Send Summary for Approval"]
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/discord.svg' width='40' height='40' /></div><br/>Post Approved Summary"]
n3 --> n5
n1 --> n2
n2 --> n3
n0 --> n1
n4 -.-> n3
n6 --> n7
n5 --> n6
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 n3 ai
class n4 aiModel
class n5 database
class n2 api
class n1 code
classDef customIcon fill:none,stroke:none
class n1,n2,n6,n7 customIcon
Why This Matters: YouTube content gets stuck in “review limbo”
Summarizing new YouTube videos sounds simple until you’re doing it every day. Someone has to notice the upload, copy the link, grab a description, write a clean summary, and then chase an approval in Slack. Meanwhile the “easy” tracking sheet becomes a mess of half-filled rows, missing links, and duplicate entries because everyone’s working from memory. The real cost isn’t just time. It’s momentum. If your process is manual, consistency quietly dies when the team gets busy.
The friction compounds. Here’s where it breaks down in real teams.
- New uploads get missed because nobody is actively monitoring the channel RSS feed.
- Summaries vary wildly depending on who wrote them and how rushed they were.
- Approvals happen in scattered Slack threads, so it’s hard to know what’s “ready to post.”
- Your Google Sheet turns into an afterthought, which means reporting and reuse become painful later.
What You’ll Build: an approval-driven YouTube summary pipeline
This n8n workflow watches a YouTube channel via RSS and reacts the moment a new video goes live. It extracts the video URL and key metadata, then uses an OpenAI Chat Model (via an AI Agent) to generate a concise, human-readable summary based on the video’s description and context. Next, it sends that summary into Slack as an approval request so a real person can quickly approve or reject it before anything gets published. Once approved, the workflow logs the final summary in Google Sheets for clean tracking and reuse, and can distribute the approved content onward (the workflow includes Discord posting, and it also includes LinkedIn nodes for extension).
It starts with discovery (RSS), moves into writing (AI), then switches into a simple human gate (Slack). After that, it becomes record-keeping and distribution (Google Sheets plus your outbound channels). No more chasing updates, no more “did anyone post this?”
What You’re Building
| What Gets Automated | What You’ll Achieve |
|---|---|
|
|
Expected Results
Say you track one channel that posts 5 videos a week. Manually, you might spend about 10 minutes noticing the upload and grabbing details, another 15 minutes writing a usable summary, and 5–10 minutes chasing approval and updating your sheet. That’s roughly 2–3 hours a week of stop-and-start work. With this workflow, the video gets detected automatically, the AI draft arrives in Slack, and your human time is mostly the approval decision and minor edits, often about 10 minutes per video. You get your week back in small chunks, which honestly is the best kind.
Before You Start
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Slack for approvals and team visibility.
- Google Sheets to log summaries and decisions.
- OpenAI API key (get it from your OpenAI account dashboard).
Skill level: Intermediate. You’ll connect accounts, set a few IDs/URLs, and adjust an AI prompt without breaking the workflow.
Want someone to build this for you? Talk to an automation expert (free 15-minute consultation).
Step by Step
A new YouTube upload triggers the workflow. The workflow monitors a YouTube channel through its RSS feed, so it can react quickly without anyone “checking YouTube” manually.
Video details get collected and cleaned. Using HTTP requests plus a bit of formatting logic (Function, Set, Merge, and If steps), the workflow extracts the video URL/ID and prepares a tidy bundle of metadata for the AI to work with.
AI drafts a summary you can actually approve. An AI Agent with an OpenAI Chat Model turns the description into a concise summary. This is the point where your prompt matters a lot: structure, tone, and what to include can all be enforced here.
Slack becomes the quality gate, then Google Sheets becomes the record. The summary is sent into Slack for approve/reject. Based on that decision, the workflow logs the outcome in Google Sheets and can continue distribution (the provided workflow includes Discord posting, and can be extended to other platforms).
You can easily modify the approval rules to route certain channels, keywords, or video types to different reviewers. See the full implementation guide below for customization options.
Troubleshooting Tips
- Slack credentials can expire or need specific permissions. If things break, check your Slack app scopes and the connected account inside n8n’s Credentials section first.
- If you’re using Wait nodes or external processing, timing can vary. Increase the wait duration if downstream steps fire before the AI response or video metadata is fully available.
- Default prompts in AI nodes are generic. Add your brand voice early (length, tone, what to avoid), or you’ll be editing outputs forever.
Quick Answers
About 30–60 minutes if your Slack, Sheets, and OpenAI accounts are ready.
No. You’ll mainly connect credentials and adjust a few fields and prompts inside n8n.
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 costs (often a few cents per summary, depending on your model and prompt size).
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. You can swap the OpenAI Chat Model to your preferred model, adjust the AI Agent prompt to force a specific structure (like “3 bullets + 1 CTA”), and change the Slack approval routing so certain keywords go to a different reviewer. Many teams also add a filter step (an If condition) to skip videos that are too short, off-topic, or missing descriptions.
Most of the time it’s expired credentials or missing Slack app scopes. Reconnect the Slack credential in n8n and confirm the bot is allowed to post in the target channel. If approvals rely on interactive buttons, make sure your Slack app interactivity settings and request URL match your n8n webhook configuration. Also check rate limits if you’re processing many videos at once.
For one or a few channels, it’s usually plenty on a basic setup.
Often, yes, because the approval logic and branching are where n8n shines. Zapier and Make can absolutely do “YouTube to Slack,” but once you add AI summarization, conditional routing, and reliable logging, costs and complexity creep up fast. n8n also gives you the self-hosting option, which can matter if you want unlimited executions or tighter control. The tradeoff is that you’ll spend a bit more time setting it up. Talk to an automation expert if you want a quick recommendation for your exact situation.
Once this is live, new uploads stop being a scramble. You get clean approvals in Slack, a reliable log in Google Sheets, and summaries that don’t depend on someone having a “free hour” that never shows up.
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.
