Workflows

What people build with YouTube transcripts

Concrete recipes — each with a copy-paste agent prompt and the equivalent API calls. Study notes from a course, competitor briefs, RAG corpora, show notes, and more.

Education

YouTube playlist → study notes

A 20-lecture course is ten hours of video and about ninety minutes of reading. This workflow turns the…

Lectures → flashcards & quizzes

Rewatching lectures is the least effective revision there is. Testing yourself on what was actually…

Marketing

Competitor channels → weekly brief

Watching three competitors’ channels is a part-time job. Checking what they published and reading only…

Developers

Playlist → RAG corpus

Video knowledge bases fail because nobody re-watches videos. Chunked transcripts with timestamps make a…

Content

YouTube video → blog post

The difference between “write a post about this video” and a post built from the transcript is…

One video → a week of posts

The video already contains the hooks — the sharpest lines someone said out loud. The transcript is…

Automation

New uploads → summarized alerts

“Did they post this week?” should not require opening YouTube. The check is free; credits are spent…

Research

Channel archive → cited quotes

“He said it in some video” is not a citation. This workflow finds where, quotes it verbatim, and links…

Creators

Episode → show notes & chapters

Show notes written from memory miss half the episode. Notes written from the transcript catch every…

Teams

Whole channel → knowledge base

The answer exists — in minute 34 of a video nobody will rewatch. As text, the same archive is…

Bring your own idea

Every workflow here is built from seven tools: transcripts (single or batch), YouTube search, channel search, channel/playlist listings, and free upload tracking. Anything that starts with "what was said in these videos" is buildable — the docs cover every call.