Skool Group Leads — Community Owner Contact Enrichment | PPE

Skool Group Leads

Enrich a list of Skool.com community ("group") URLs with member stats, category, description, owner identity and social links — plus a best-effort contact email resolved only from signals that are already public, never guessed or invented.

Why this actor

Skool.com hosts thousands of paid and free online communities. The best-known existing Skool scraper reliably returns member counts and descriptions, but its own live-tasted output has two confirmed gaps:

• Owner contact email — the field is present in the data model but comes back empty for essentially every group when viewed as a logged-out visitor.
• Monthly price — filled for only a small minority of sampled groups, because Store discovery mostly surfaces free communities.

This actor is built around closing the first gap honestly (see Contact-email wedge below) and reporting the second gap for what it actually is, rather than papering over it.

Features

• Rich group profile — name, slug, URL, member count, online-member count, admin count, post/course/module counts, human-readable category names, plan tier, membership model, privacy setting, logo/cover images, creation/update timestamps.
• Owner identity — name, bio, location, and every social link Skool exposes (website, Twitter/X, Instagram, LinkedIn, Facebook, YouTube).
• Contact-email wedge — see below.
• No login required — every field comes from Skool's own public, anonymous-visitor "about" page.
• Pay per group delivered — PPE pricing; a run that finds nothing charges nothing.

Contact-email wedge — how it works, and the honest fill rate

Skool's own owner-profile object has an email slot, but it is always blank for an anonymous visitor — this is a structural gap in the source, not something any scraper can extract around without a login the buyer would have to supply (which this actor never asks for). Instead, this actor looks for contact signals that are already sitting in public view:

1. The group's own about page — scanned for a visible mailto: link first, then a plain email-looking string in the page text (excluding Skool's own support address, which shows up on every page's footer regardless of which group you're looking at).
2. One extra hop, only if step 1 finds nothing — if the group owner has linked their own external website (not another Skool page), that ONE page is fetched and scanned the same way. No further links on that page are followed — this is a single hop, not a crawl.

Confirmed fill rate from a real 5-group cloud test run (2026-07-20): 1/5 groups (20%) yielded a real, verified contact email this way — found via the external-site hop (connect@evelyn-weiss.com, matching the real owner's name, from her linked coaching-site landing page). 0/5 had a mailto/email visible directly on the Skool about page itself. This is genuinely better than the champion's ~0% (structural email field always blank), but it will not be 100% — most group owners simply haven't put a public email anywhere reachable in one hop. The field is left empty rather than guessed whenever nothing is found; contact_email_source and contact_email_confidence always tell you exactly where a filled value came from.

Known, confirmed gap: monthly_price

Live testing across multiple groups (free and a known high-revenue paid mastermind) found no server-side field anywhere in the anonymous "about" page payload that carries the actual membership price — Skool renders join pricing client-side, after a paywall check, for logged-out visitors. monthly_price is always returned as null by this actor. This matches (does not improve on) the champion's own confirmed weak spot on this specific field; we report it honestly rather than fabricate a number. Everything else in this actor's output is at or above the champion's field depth.

Access note: why groups are supplied by URL, not by category browsing

Skool's discovery/category browsing pages are protected by a bot-detection challenge that cannot be solved without a full browser (out of scope for this actor's zero-cost build). Individual group "about" pages are not behind this protection at all — they load cleanly and instantly. So this actor takes an explicit list of group URLs or slugs (competitor communities you already know about, or a list gathered from your own research/Google/YouTube/etc.) rather than crawling Skool's own directory.

How to Use

1. Open the actor in Apify Store and click Try for free.
2. Set groupUrls — a list of Skool group URLs or bare slugs, e.g. ["https://www.skool.com/educate/about", "make-money"].
3. Leave resolveContactEmail on (default) to run the contact-email wedge, or turn it off for a faster run if you only need group stats.
4. Adjust maxItems to cap output.
5. Leave the proxy on the default Apify RESIDENTIAL group — required for reliable access.
6. Click Start and collect results from the Dataset tab.

Input Example

{
  "groupUrls": ["https://www.skool.com/educate/about", "make-money", "skoolers"],
  "maxItems": 100,
  "resolveContactEmail": true,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["RESIDENTIAL"]
  }
}

Output Example

{
  "slug": "make-money",
  "group_url": "https://www.skool.com/make-money/about",
  "group_name": "make-money",
  "display_name": "Skool Growth Free Training Hub",
  "description": "All my free Skool trainings, strategies, templates & resources in one place...",
  "member_count": 8904,
  "category_names": ["Admin & Help"],
  "plan_tier": "pro",
  "monthly_price": null,
  "owner_name": "evelyn",
  "owner_bio": "Running Meta Ads for Skool & Skool creators...",
  "owner_link_website": "https://www.coachgrowthhub.com/cgh-259676031",
  "contact_email": "connect@evelyn-weiss.com",
  "contact_email_source": "external_site_mailto",
  "contact_email_confidence": "high",
  "scraped_at": "2026-07-20T09:50:20Z"
}

(Real, non-synthetic record — one of the 5 pulled in the pre-publish cloud test run.)

Pricing

Informational only — pricing is set separately by the Store listing, not by this actor's code.

Proposed: $0.049 per group record delivered (group-lead event) — a charm-undercut against the known champion actor's $0.05/result price point, for a comparable-or-richer field set plus the contact-email wedge the champion doesn't have.

Use Cases

• Lead generation — find and contact owners of communities in your niche for partnerships, sponsorships, or cross-promotion.
• Competitive research — track member counts, categories, and growth signals of rival communities over time.
• Market mapping — build a directory of active Skool communities in a given topic area.
• Outreach list building — combine with the contact-email wedge to build a warm outreach list of community owners who have a public contact path.

FAQ

Does this actor need a Skool account or login? No. Every field comes from Skool's own public, logged-out "about" page.

Will I get a contact email for every group? No — see the honest fill-rate disclosure above. About 1 in 5 groups yields a real public email through this method; the rest are left empty, never guessed.

Why isn't monthly_price filled in? Skool doesn't expose it to logged-out visitors anywhere server-side — confirmed across both free and high-revenue paid groups. See the dedicated section above.

Can I browse Skool's discovery/category pages with this actor? Not in this version — see "Access note" above. Supply the group URLs you want enriched directly.

Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.

Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.

Only these fields are recorded:

• schema version, Actor name and build number;
• UTC start and finish hour (not a precise timestamp);
• run duration, number of results and time to the first result, each as a coarse range;
• whether the result was empty, the end status, and an error type from a fixed list;
• memory setting and counts of charged events;
• names of the input fields you set, never their values;
• the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

Additional fields (Phase 2)

This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.

The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.

Run-outcome signals (v2)

To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:

• the result limit you asked for (a range, when the input has one) and what share of it was delivered;
• results delivered per input item you listed (a range);
• output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
• how the run was started (console, API, schedule, webhook, another Actor);
• how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
• if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
• a short code made from the names of the input fields you set, never their values.

Repeat-run fingerprint (v2)

When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and disableUsageStats: true turns it off.