Monitor New YouTube Creators Appearing in a Niche

Creator markets change continuously: established channels move into a topic, smaller channels become active, and YouTube search rankings shift. A scheduled YouTube Creator Finder Task can reveal channels newly discovered by a stable query set without mixing videos and playlists into the results.

Keep the query and filters stable

Changes are interpretable only when the collection settings are comparable.

{
  "searchTerms": [
    "data engineering tutorials",
    "modern data stack",
    "analytics engineering"
  ],
  "maxCreatorsPerSearch": 100,
  "maxTotalCreators": 300,
  "minVideos": 5,
  "uploadedWithinDays": 365,
  "languageHint": "en",
  "countryHint": "US"
}

Save the input as an Apify Task and schedule it weekly. Daily runs may add cost without useful movement for a narrow professional niche. Record run ID, time, input version, and result count.

Detect newly discovered channels

Maintain a channel table keyed by channelId and an observation table keyed by channel plus scrape time.

for creator in creators:
    channel_id = creator["channelId"]
    if channel_id not in known_channels:
        known_channels[channel_id] = {
            "firstSeenAt": creator["scrapedAt"],
            "firstQuery": creator.get("discoveryQuery"),
            "firstRank": creator.get("discoveryRank"),
        }
        notify_newly_discovered(creator)

    save_observation(
        {
            "channelId": channel_id,
            "observedAt": creator["scrapedAt"],
            "subscribers": creator.get("subscriberCount"),
            "videos": creator.get("videoCount"),
            "latestVideoId": (creator.get("latestVideo") or {}).get("videoId"),
            "query": creator.get("discoveryQuery"),
            "rank": creator.get("discoveryRank"),
        }
    )

Call it firstSeenAt, not createdAt. Search is not a complete registry, and ranking changes can surface a long-established channel for the first time.

Track meaningful changes

Useful alerts include a new channel crossing the audience minimum, a previously dormant creator publishing again, a new public website, or a large ranking move repeated across several runs. Subscriber changes derived from rounded public labels should use material thresholds; do not alert on tiny apparent differences.

Handle gaps honestly

A zero-result run can reflect filters, source changes, or a transient fetch problem. Monitor run status and compare a stable fixture query before concluding the niche disappeared. Search output varies by locale and time, and YouTube can change internal payloads.

This workflow monitors public channels, not individuals' private activity. Store only what the research needs, review contact use separately, honor deletion and opt-out obligations where applicable, and avoid profiling sensitive traits from channel content.