automations / Make · updated 2026-07-20
YouTube videos → transcript rows (Make)
The transcript job as a Make blueprint: one HTTP module runs the batch, an Iterator fans it out one bundle per video, and a router splits billed transcript rows from unbilled failure rows on filters — so a captionless video flows past your destination instead of erroring the scenario.
A 50-video batch costs about $0.15 (50 × $0.003 plus a $0.00005 start fee) — videos that can't deliver a transcript are $0.
What's inside
- 1.Get transcripts (HTTP → Make a request → run-sync-get-dataset-items, Parse response ON — one call per batch)
- 2.One bundle per video (Flow control → Iterator over the HTTP module's Data)
- 3.Router with two filtered routes: success = true and success = false
- 4.Transcript row (billed route: video_id, title, segments)
- 5.Failure row (unbilled route: video_id, code, request_id — the scenario run stays green)
Set it up
Open the blueprint on GitHub (button above), click Raw and save the file, then in the Make scenario editor: ⋯ (More) → Import Blueprint — Make imports blueprints from a file, not a URL. Open Get transcripts and replace YOUR_APIFY_TOKEN in the Authorization header; put your own IDs in videoIds (up to 50 per run). The token comes from Apify Console → Settings → API tokens; the free tier works, and the run bills per delivered row on your Apify account.
Ways to extend it
- Replace the Transcript row module with your real destination — Sheets, Notion, Slack — keeping the route's success filter.
- Join the transcript segments into plain text in your destination's field with Make's map() and join() functions.
- For batches that outgrow run-sync's ~5-minute wait, switch to the async pair — POST /runs, then fetch the dataset — as shown in the Make guide.
Going deeper: the Make guide — the same scenario built by hand, plus the async pattern for big batches. Actor pricing: what a YouTube Transcript Scraper run costs. Error codes the failure branch can carry: the error-code reference.