automations / Make · updated 2026-07-20

YouTube video → comments (Make)

The comments job as a Make blueprint: one HTTP module fetches a video's comments, an Iterator fans them out one bundle per comment — author, text, likes — and a video with comments disabled exits on the failure route instead of erroring the scenario.

Get the blueprint on GitHub YouTube Comments Scraper docs

200 comments cost $0.08; a video with comments off costs $0.

What's inside

  1. 1.Get comments (HTTP → Make a request → run-sync-get-dataset-items)
  2. 2.One bundle per comment (Flow control → Iterator)
  3. 3.Router with two filtered routes: success = true and success = false
  4. 4.Comment row (billed route: video_id, author, text, like_count)
  5. 5.Failure row (unbilled route: video_id, code, request_id)

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 comments and replace YOUR_APIFY_TOKEN; set videoUrls to your video (URL or 11-character ID) and flip includeReplies to true if you want reply threads. 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

  • Feed Comment row bundles into a sentiment step and aggregate per video.
  • Add a keyword filter on the text field to alert only on comments that mention your brand.
  • Route failure bundles where code is COMMENTS_DISABLED to a skip-list so you stop re-querying those videos.

Going deeper: the Make guide — the same HTTP + Iterator + filter pattern, step by step. Actor pricing: what a YouTube Comments Scraper run costs. Error codes the failure branch can carry: the error-code reference.