Triage YouTube comments into bugs, features, and FAQs
Sort new YouTube comments into buckets every four hours, file bugs and feature requests in Linear, auto-reply to common questions, and post a recap to Slack.
YouTube
Linear
SlackProductCustomer SupportFeedback TriageNotifications & AlertsDaily DigestsBuild an agent workflow that triages YouTube comments on my own channel into actionable engineering and content work so nothing gets buried.
Trigger: cron, every 4 hours.
On each run, the agent should:
1. Use YouTube List Channels with mine=true to get my channel and its uploads playlist ID.
2. Use YouTube List Playlist Items on the uploads playlist to collect videos published in the last 30 days.
3. For each of those videos, use YouTube List Comment Threads to pull top-level comments. Only process comments newer than the last run by remembering the most recent comment id (or publishedAt) per video between runs so the same comment is never processed twice.
4. Classify every new comment into exactly one bucket: bug report, feature request, content suggestion, FAQ, or noise. Be conservative: when unsure between FAQ and noise, choose noise.
5. For each comment classified as bug report or feature request, use Linear Create Issue in the team configured at setup. Title should be a short summary of the comment. Description should include the full comment text, the video URL, the commenter handle, and the bucket. Tag bugs and feature requests with distinct labels so they are easy to filter later.
6. For each comment classified as FAQ, match it against a small set of pre-approved question and answer templates supplied at setup. If a template clearly matches, use YouTube Reply to Comment to post the templated answer. If no template matches confidently, treat it as noise for that run and surface it in the Slack recap instead. Never invent an answer.
7. After processing all videos, use Slack Send a Message to post a single recap to a configured channel with the totals per bucket (bugs, features, content suggestions, FAQs auto-replied, FAQs surfaced for review, noise), links to every Linear issue created on this run, and a short list of any FAQ candidates that did not match a template.
Configuration the workflow should ask for at setup: the Linear team (or per-bucket team mapping if the user wants to split bugs and features), the Slack channel for the recap, the list of FAQ templates, and an option to disable auto-reply entirely.
Keep the loop quota-aware: prefer cheap list and get calls, batch where possible, and skip videos with no new comments.
Additional information
What does this prompt do?
- Pulls new comments from videos you posted in the last 30 days, every four hours.
- Classifies each comment as a bug report, feature request, content suggestion, FAQ, or noise.
- Opens a Linear issue for every bug and feature request with the comment, commenter, and video link.
- Posts a templated reply on common questions so viewers get an answer without you typing it.
- Drops a Slack summary with the bucket counts and links to every Linear issue created.
What do I need to use this?
- A YouTube account that owns the channel you want monitored.
- A Linear workspace and the team you want issues created in.
- A Slack workspace and the channel where the recap should land.
- A short list of pre-approved replies for the questions you answer most often.
How can I customize it?
- Change how often it runs (every two hours, once a day, only on weekday mornings).
- Edit the categories or add your own buckets, like sponsorship inquiries or transcription fixes.
- Swap which Linear team or project receives each kind of issue, or route features to a different board than bugs.
- Update the templated replies, or turn off auto-reply entirely and just log everything to Linear and Slack.
Frequently asked questions
Will this reply to every single comment?
What happens to comments that are just spam or compliments?
Can I send bugs and feature requests to different Linear teams?
Will it process the same comment twice?
What if I do not want to reply to anything automatically?
Related templates
Every Friday, get a ready-to-read preview of your league's weekend matches, with positions, form, scorers to watch, and predicted results, posted to Slack.
Every Monday morning, finance leadership gets a clear recap of last week's Braintree sales, refunds, and disputes by email and Slack.
Every morning we check your list of IP addresses for abusive activity, update your spreadsheet, and alert your team only about the risky ones.
Every time you ship to Heroku, we post a clear summary to Slack listing what changed, who deployed it, and whether it was a rollback.
Every morning, check each ClickHouse service against its own backup schedule, get a Slack summary, and a Linear ticket for anything stale or failed.
Every weekday morning, your team gets one Slack briefing on who's flying today, their live flight status, and any delays or cancellations to act on.
Stop letting your best feedback get buried under YouTube comments.
Connect YouTube, Linear, and Slack once, and every new comment lands in the right place automatically.