YouTube Transcript Summarizer

Overview

Useful information can be difficult to revisit when a long YouTube video holds it. You need to search, quote, or share the substance without replaying the source each time. This workflow gives you a concise written summary in Markdown and HTML. It is the written option for research notes and reference material, not an audio conversion. Get YouTube Transcript retrieves the available captions, then Write Summary turns that transcript into the two readable artifacts. You can inspect and adapt the same node handoffs in visual workflows.

Pipeline

1. Get YouTube Transcript receives one YouTube video URL or ID and returns its available captions.
2. Write Summary receives the transcript and returns the written summary in Markdown and HTML.

Inputs

• Source video. A YouTube video URL or ID. The default scope is one video per run.
• Summary instructions. The guidance in the Write Summary node. Keep the built-in concise written-summary instructions for the first run, then edit them when you need a different focus or structure.

Outputs

• Markdown summary. A written summary file for notes, editing, or version control.
• HTML summary. A browser-readable rendering of the same written summary.

Integrations

• Get Transcript. Reads the available caption track for the source video.
• AI. Converts the returned transcript into the written summary.
• Visual workflows. Let you inspect and edit the handoff between transcript retrieval and summary writing.

Sample output

The artifacts below are illustrative. They show the written output shape, not a completed run.

summary.md

# Video summary
 
## Main idea
 
Small, reversible releases shorten the feedback loop between a code change and evidence from production.
 
## Key points
 
- Keep each release narrow enough to review and reverse.
- Observe the result before sending the next change.
- Record the decision and its outcome for the next release.

summary.html

<h1>Video summary</h1>
<h2>Main idea</h2>
<p>Small, reversible releases shorten the feedback loop between a code change and evidence from production.</p>
<h2>Key points</h2>
<ul>
  <li>Keep each release narrow enough to review and reverse.</li>
  <li>Observe the result before sending the next change.</li>
  <li>Record the decision and its outcome for the next release.</li>
</ul>

FAQ

Does the source video need captions?

Yes. Get YouTube Transcript depends on a caption track that is available for the video. Without captions, the Write Summary node has no transcript to process.

Does this workflow produce an audio file?

No. Its output is a written summary in Markdown and HTML. Use the podcast workflow when you need a rewritten script and an MP3.

Can I change the written summary structure?

Yes. Edit the instructions in Write Summary when you want a different focus or structure. Keep the existing instructions when the default concise summary is sufficient.

Can I submit a playlist?

This page documents one video URL or ID per run. Submit one video in each run unless you change the graph to accept a list.

Related workflows

• YouTube Transcript to Podcast when you need a spoken script and MP3 instead of a written summary.
• Scrape and Summarize Webpages when your source is a set of web pages instead of YouTube captions.
• Daily AI News Digest when you want a recurring feed digest instead of a summary of one selected video.