Before you run
An Apify Actor is a cloud tool with an input form, a Run button, logs, and a result Dataset. For this first test, you need an Apify account and one current public YouTube video URL or 11-character video ID. You do not need to install code or provide a YouTube login.
Choose the question before the Actor
A generic export is rarely the useful endpoint. Pick the smallest workflow that directly answers your question.
| Your question | Use this workflow | Launch price |
|---|---|---|
| Did the video materially change? | Engagement Change Monitor. First run is a free baseline. | $20 / 1,000 events |
| Did a sponsor or affiliate disclosure change? | Commercial Disclosure Monitor. First run is a free baseline. | $25 / 1,000 events |
| Is there direct sponsor or affiliate evidence? | Sponsor Link Intelligence. | $20 / 1,000 analyses |
| Which chapters are explicitly listed? | Chapter Timestamp Extractor. | $12 / 1,000 results |
| Can I create a source-only content brief? | Content Brief Intelligence. | $25 / 1,000 briefs |
Run one video
- Open the bounded one-video content brief Task.
- Select Try for free or open its Input tab.
- Keep the starter video or replace it with one current public URL or ID.
- Click Start. When the run succeeds, open the Dataset tab.
{
"videoUrlsOrIds": ["c347oYQO57A"],
"maxResults": 1
}The same videoUrlsOrIds input works for sponsor-link, chapter, brief, and monitor workflows. Each monitor also requires a stable, customer-specific monitorKey and a maximum event cap; the engagement monitor additionally uses minimumViewDelta.
Inspect the output
A complete source-only brief should include these fields. Missing or failed source fetches must not become a paid row.
| Field | What to verify |
|---|---|
videoId, videoUrl | The exact public source and stable identifier. |
title, channelId | The public video and channel identity returned by the source. |
publishDate, durationSeconds, viewCount | Typed public metadata suitable for sorting or comparison. |
description, keywords, externalDomains | Source fields used to build the brief. Inspect them before drawing a conclusion. |
contentSignals | Must show sourceFieldsOnly: true and watchedOrTranscribed: false. |
analysisHash | A deterministic fingerprint for deduplication and downstream checks. |
Understand the cost
The five launch prices range from $12 to $25 per 1,000 complete results or meaningful events. A one-row retained result therefore costs $0.012-$0.025 in Actor PPE. The monitor baseline, unchanged observations, diagnostics, duplicates, incomplete fetches, empty classifications, and unsupported inferences are not billable. Your Apify account may separately show platform usage; check the live Pricing tab and account plan before scheduling larger runs.
Monitor safely
The first monitor run creates a free baseline. Later runs compare the same videos and threshold against customer-isolated state. Use a new monitorKey when you intentionally change the video set or threshold.
{
"videoUrlsOrIds": ["dQw4w9WgXcQ"],
"monitorKey": "campaign-video-daily",
"minimumViewDelta": 10000,
"maxEvents": 10,
"maxResults": 1
}An unchanged run saves no paid event. A failed fetch, changed configuration under the same key, or event count above your cap does not advance state.
Troubleshooting
The run failed before producing a Dataset
Confirm the video is public and current, then retry once with one exact URL or ID. The Actor fails closed when public metadata is incomplete rather than saving a misleading partial row.
The sponsor or chapter workflow returned no row
That can be correct. Sponsor analysis requires direct disclosure language plus a public link. Chapter extraction requires explicit timestamp lines in the description. Unclear or absent evidence is not billed.
Does this download or transcribe the video?
No. These workflows use public video metadata and description fields. They do not promise captions, transcripts, comments, private content, or creator contacts.
Can I schedule the monitor?
Yes, after validating one baseline. Use an Apify Task and schedule, keep the same input and monitor key, and send webhook output only when a meaningful event is saved.
Next workflow
Use engagement or disclosure monitoring when only meaningful changes should create rows, sponsor or chapter analysis when direct evidence is mandatory, and the content brief when a downstream research or RAG workflow needs structured source fields without transcript claims.
Compare all five workflows
Choose by buyer question, paid unit, evidence rule, and bounded public Task.
Open the YouTube intelligence hub