🎓 Skool Group Scraper — Discover Communities, Pricing, Owners & Landing-Page Data

Browse Skool's discovery pages and turn them into a structured dataset. Every community comes back with its name, description, monthly and annual pricing, member count, privacy and membership model, landing-page content — and a full owner profile including bio, location, website and social links.

Point it at a discovery URL, set a cap, and you have a competitive map of the Skool ecosystem.

---

What you get

🏫 Community	💰 Pricing & access	👤 Owner
Name, display name, group ID	Monthly price + currency	Name, first/last name, ID
Description	Annual price + currency	Bio and location
Landing-page description	Membership model	Website URL
Support e-mail	Privacy setting	Instagram, YouTube, Facebook, X, LinkedIn
Total members, admins, posts	Plan	Profile and bubble pictures
Courses and modules count	Landing-page access type	Online status and last-offline time
Rules count		Activity status
Logo, big logo, cover, favicon		Personality/DISC fields where published
Enabled tabs (classroom, calendar, map, audio chat)		Created / updated timestamps
Landing-page attachments (images, video)

---

Key features

• Real pricing data, parsed properly. Monthly and annual prices are extracted with their currencies and normalised into numbers — so you can sort, compare and average across the whole ecosystem instead of eyeballing price tags.
• Full owner profile on every community. Bio, location, website, Instagram, YouTube, Facebook, X and LinkedIn — this is the field set that turns market research into an outreach list.
• Support e-mail extraction with fallback. The owner's contact e-mail is used when available; if not, the Actor scans the landing-page description for an address. That fallback recovers contacts most tools miss entirely.
• Community health metrics. Total members, admins, posts, rules, courses and modules give you a real picture of activity, not just a headline member count.
• Feature detection. Which tabs each community has enabled — classroom, calendar, map, audio chat — tells you how a group is actually run.
• Landing-page attachments. Images and video used on the landing page are returned with their file references, useful for competitive creative research.
• Concurrent enrichment. After discovery, each community is enriched in parallel, so large exports stay fast.
• Live streaming output with an optional Apify Proxy for tougher runs.

---

Use cases

• Competitive research — map every community in your niche with its price, size and positioning.
• Pricing strategy — compare monthly and annual prices across communities of similar size before setting your own.
• Creator and partner outreach — owner e-mails, websites and social handles make direct contact straightforward.
• Market sizing — total members across a category shows how big the opportunity really is.
• Affiliate and sponsorship prospecting — find large communities in a niche and approach their owners.
• Trend research — which topics are attracting new communities and members.
• Course and content benchmarking — course and module counts reveal how much material top communities ship.
• Investment and acquisition screening — price × members gives a first-pass revenue estimate.

---

How it works

1. You supply one or more Skool discovery URLs and a per-URL cap.
2. The discovery page is loaded and every listed community is collected from the page's embedded data.
3. Each community is mapped into a flat record with pricing, metadata and media.
4. Records are enriched concurrently — landing-page description, owner profile, social links, support e-mail, member and content metrics, and enabled tabs.
5. Rows stream into the dataset as each community finishes enrichment.

---

Quick start

1. Open the Actor. The default URL is Skool's main discovery page — keep it or paste your own.
2. Set How many communities max (start with 10–20 to preview).
3. Click Start, then export the Output tab as JSON (recommended) or CSV.

Minimal input

{
  "urls": ["https://www.skool.com/discovery"],
  "maxItems": 25
}

---

Input configuration

Field	Type	Default	Description
urls	array	— (required)	Skool discovery page URLs, one per line. Category and filtered discovery URLs work too — copy them from your browser.
maxItems	integer	10	Maximum communities to collect per discovery URL. Keep it small to preview, raise it for a full export.
proxyConfiguration	object	off	Optional. Turn on to route through Apify Proxy from the start; otherwise the Actor handles hiccups itself.

---

Output data

One row per community.

Community

id, name, displayName, description, landingPageDescription, supportEmail, privacy, membership, plan, landingPageAccessType, color, initials, createdAt, updatedAt, createdBy.

Pricing

monthlyPrice, monthlyCurrency, annualPrice, annualCurrency, affiliatePercent.

Size & activity

totalMembers, totalOnlineMembers, totalAdmins, totalPosts, totalRules, numCourses, numModules.

Features

classroomVisible, calendarVisible, mapVisible, audioChatVisible, surveyEnabled, surveyQuestions, surveyUpdatedAt, pluginAutoDmEnabled, pluginMinChatLevelEnabled, customLinks.

Media

logoUrl, logoBigUrl, coverSmallUrl, faviconUrl, landingPageAttachments[] (with type, image and video file references).

Owner

ownerId, ownerName, ownerFirstName, ownerLastName, ownerBio, ownerLocation, ownerWebsite, ownerInstagram, ownerYoutube, ownerFacebook, ownerTwitter, ownerLinkedin, ownerPictureProfile, ownerPictureBubble, ownerOnline, ownerLastOffline, ownerActivityStatus, ownerDiscTop, ownerMyersBriggs, ownerCreatedAt, ownerUpdatedAt.

Example output (trimmed)

{
  "id": "a1b2c3d4",
  "name": "example-growth-lab",
  "displayName": "Example Growth Lab",
  "description": "A community for founders scaling from $10k to $100k MRR.",
  "landingPageDescription": "Weekly teardowns, live calls and a private directory. Questions? hello@examplegrowthlab.com",
  "supportEmail": "hello@examplegrowthlab.com",
  "monthlyPrice": 49,
  "monthlyCurrency": "USD",
  "annualPrice": 490,
  "annualCurrency": "USD",
  "privacy": "private",
  "membership": "paid",
  "totalMembers": 3182,
  "totalAdmins": 4,
  "totalPosts": 12840,
  "numCourses": 6,
  "numModules": 42,
  "classroomVisible": true,
  "calendarVisible": true,
  "logoUrl": "https://assets.skool.com/…",
  "ownerName": "Example Owner",
  "ownerBio": "Ex-agency founder. Now helping other founders scale.",
  "ownerLocation": "Lisbon, Portugal",
  "ownerWebsite": "https://examplegrowthlab.com",
  "ownerInstagram": "exampleowner",
  "ownerYoutube": "@exampleowner",
  "createdAt": "2024-02-11T09:22:31Z"
}

Illustrative values — a live run returns current Skool data.

---

Usage examples

Snapshot of the discovery page

{
  "urls": ["https://www.skool.com/discovery"],
  "maxItems": 100
}

Several discovery views in one run

{
  "urls": [
    "https://www.skool.com/discovery",
    "https://www.skool.com/discovery?c=business",
    "https://www.skool.com/discovery?c=health"
  ],
  "maxItems": 50
}

Pricing benchmark

Run a large export, then in your spreadsheet compare monthlyPrice against totalMembers to see where your own pricing would sit.

Build an owner outreach list

Filter the export for rows where supportEmail or ownerWebsite is not empty, and sort by totalMembers — the biggest communities with a reachable owner come first.

Track the ecosystem over time

Save the input as a Task, attach a weekly Schedule, and compare totalMembers and monthlyPrice per community across runs.

---

Run it from your own code

Python

from apify_client import ApifyClient

client = ApifyClient("<YOUR_APIFY_API_TOKEN>")

run = client.actor("scraperx/skool-group-scraper").call(run_input={
    "urls": ["https://www.skool.com/discovery"],
    "maxItems": 50,
})

for g in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(g["displayName"], "|", g.get("totalMembers"), "members |",
          g.get("monthlyPrice"), g.get("monthlyCurrency"))

JavaScript

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: '<YOUR_APIFY_API_TOKEN>' });

const run = await client.actor('scraperx/skool-group-scraper').call({
    urls: ['https://www.skool.com/discovery'],
    maxItems: 50,
});

const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

cURL

curl -X POST "https://api.apify.com/v2/acts/scraperx~skool-group-scraper/runs?token=<YOUR_APIFY_API_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{"urls":["https://www.skool.com/discovery"],"maxItems":50}'

Integrations

Send communities into Google Sheets, Airtable, Slack, Make, Zapier, Google Drive or your CRM via webhooks, and use Schedules to keep a rolling view of the ecosystem.

---

Pricing

Pay-per-event: a small Actor-start charge plus a charge per community row delivered to your dataset. You pay for communities, not run time. Current rates are on the Pricing tab of this Actor's page, and Apify shows an estimate before and during every run.

---

Limits & good to know

• Discovery pages only. The Actor collects communities listed on Skool's public discovery views. Unlisted or private communities that never appear there are out of scope.
• maxItems is per discovery URL, so three URLs at 50 each can return up to 150 rows.
• Not every field is published. Owner social links, location and support e-mail depend entirely on what the owner filled in — blanks are genuine absences, not errors.
• Prices are as displayed. Free communities return null prices; the currency reflects what Skool shows on the landing page.
• Enrichment is one extra page load per community, so larger caps take proportionally longer.
• Media URLs point at Skool's CDN and can change over time.
• Default run options are 4 GB memory and a 1-hour timeout — raise the timeout for very large exports.

---

FAQ

Do I need a Skool account? No. The Actor reads publicly accessible discovery pages and community landing pages.

Can I scrape members of a community? No. This Actor covers the community itself — its pricing, metrics and owner — not its member list, which is private.

Do I get community prices? Yes, both monthly and annual, with their currencies, parsed into numbers you can sort and compare.

Where does supportEmail come from? The owner's published contact e-mail. If that is absent, the Actor scans the landing-page description for an address.

Can I filter by category? Yes — apply the filter on Skool's discovery page, copy the resulting URL, and paste it as an input.

Why are some owner fields empty? Because that owner has not filled them in on their public profile.

Which export format should I use? JSON — landingPageAttachments, customLinks and surveyQuestions are nested. CSV works well for the pricing and member-count columns.

Can I run it on a schedule? Yes — save your discovery URLs as a Task and attach an Apify Schedule to track how the ecosystem changes.

---

Legal & responsible use

This Actor collects only publicly visible Skool discovery and landing-page content — the same information any visitor can browse. It does not log in, join communities, or access member-only content. Owner names, bios, locations, e-mails and social handles are personal data: if you process them, ensure you have a lawful basis under GDPR and comparable regulations, honour opt-outs when doing outreach, and comply with Skool's terms and applicable law.

Support

Need extra fields, deeper community data, or a custom research pipeline? Open an issue on the Issues tab of this Actor.