Build a repeatable upload check

1. Copy the starter input

Use this bounded input for your first run. It is a recipe, not recorded output. Download input JSON

{
  "channels": [
    "@apify"
  ],
  "tab": "videos",
  "sortBy": "newest",
  "maxVideosPerChannel": 20,
  "maxConcurrency": 1,
  "proxyMode": "auto"
}

2. Open the Actor and review your budget

Open the Actor, switch Input to JSON and paste the input above. Review the Pricing tab and set Maximum cost per run before you start. The link does not start a paid run.

Open YouTube Channel Scraper (videos, shorts, live) →

3. Check the result before exporting

Store successful rows by channelId and videoId. Compare with the previous successful dataset; never treat an error row as an empty channel.

Export the successful dataset as JSON, CSV or Excel. Read the full guide for field meanings and the next step.

Know the limits

Scheduling, storing previous results and notifications must be configured separately. A latest-20 window can miss uploads if a channel publishes more than 20 between checks.

Check exported JSON on your computer

Download the local result checker. It requires Node.js 20 or newer, has no dependencies and makes no network requests. Export a JSON array from Apify and keep the file on your computer.

node check-results.mjs youtube current.json

Each row must have a channel ID, video ID, title and HTTP URL. Duplicate IDs and error rows fail the check. This checks exported fields, not the accuracy or completeness of YouTube data. Exit code 0 means the field checks passed; 2 means review the rows; 1 means the file or command could not be read. An empty dataset needs review.

Compare with the previous successful export

node check-results.mjs youtube-diff previous.json current.json

Use the same channels, tab, sort order and limits. Both snapshots must pass before comparison. The report lists newly observed IDs; it does not prove when a video was uploaded or that a missing video was deleted. Keep the previous successful file if a check fails. A bounded latest-video window can miss uploads between checks. Scheduling and notifications remain separate.

Pricing

Apify plan	Per video	Per 1,000
Free plan	$0.0005	$0.50
Starter	$0.0004	$0.40
Scale	$0.00035	$0.35
Business	$0.0003	$0.30
Enterprise	$0.0003	$0.30
Enterprise+	$0.0003	$0.30

Primary event rates from a catalog snapshot; this is not the total price of a run. Additional charge events and Actor Start fees may apply; start fees can scale with memory. Check the Actor's Pricing tab on Apify for all events, conditions and current plan-specific rates, and set a maximum run budget before starting.

Use the input in n8n

Download the manual n8n starter. Import it and select an HTTP Header Auth credential in the HTTP Request node: name Authorization, value Bearer followed by your Apify token. Store it in n8n credentials, never in the exported JSON.

The workflow is inactive and extracts data only. It does not schedule, compare results or send alerts. Import and a live run must be checked in your n8n installation. If the synchronous request times out, check Apify before retrying to avoid duplicate work and charges.