Skool Classroom Media/Video · Posts · Nested Comments
Skool.com posts + nested comments + classroom courses + media files. Date filter for new-content delta runs, storage dedup across runs (no double-billing), tab selector for community/classroom, configurable comment depth. The most thorough Skool content extractor. JSON or CSV.
Publisher description, verbatim
Last 7 dayson this actor
- 3other changes
- 6new rivals on Skool
#3of 102
on Skool, by users in the last 30 days among actors classified to this platform.
Store search presence
6top-10 keywords
best #1 for “classroom”
- classroom#1
- skool#1
- media#6
- 3 more#7–#8
re-crawled daily
| Theme | Sentiment | Said | What they mean |
|---|
| Caps and ceilings | 0 praised · 1 complained | 1 | output capped at 30 members“I’ve been testing the Skool member scraping functionality and ran into a major limitation that isn’t clearly documented. The group we want to scrape has 1,100+ members, but the output consistently returns only 30 members — even when: Max Items is set very high (100,000) Max Page is set high Monitoring mode is disabled “Only scrape members newer than [date]” is left empty From the logs, it appears there is an internal date filter being applied: memberCounter after date filter: 30 However, there is no visible parameter in the UI that clearly explains or controls this behavior. This makes it very confusing to understand why results are capped. Additionally, pagination (?p=106, ?p=107, etc.) loads successfully, but each page returns the same 30 members repeatedly. This suggests either: The crawler is scraping only server-rendered HTML while Skool loads members dynamically via JS/XHR Or there is an internal slicing/filtering limit hardcoded to 30 The current setup makes it impossible to scrape full member lists from larger communities. Suggestions: Expose and document any internal date filtering logic Clarify whether this actor supports JS-rendered member lists Consider switching to Playwright/Puppeteer or directly hitting Skool’s API endpoints Add clear documentation about pagination behavior Right now, the behavior is misleading because the UI suggests full scraping capability, but the actual output is capped at 30 members. Would appreciate clarification from the dev team.” — 3/5 |
|---|
| Does it return everything | 0 praised · 1 complained | 1 | cannot scrape full member lists |
|---|
| Setup and docs | 0 praised · 1 complained | 1 | unclear or missing documentation |
|---|
| What it supports | 0 praised · 1 complained | 1 | JS-rendered member lists handling |
|---|
| Does the publisher answer | 2 praised · 0 complained | 2 | responsive, helpful developer support“This is the only Skool scraper I've found that is well maintained, extremely customizable, and works. The developer is great!” — 5/5 |
|---|
| Does it run | 1 praised · 0 complained | 1 | well-maintained and functioning reliably |
|---|
Caps and ceilings
0 ↑ · 1 ↓ of 1output capped at 30 members“I’ve been testing the Skool member scraping functionality and ran into a major limitation that isn’t clearly documented. The group we want to scrape has 1,100+ members, but the output consistently returns only 30 members — even when: Max Items is set very high (100,000) Max Page is set high Monitoring mode is disabled “Only scrape members newer than [date]” is left empty From the logs, it appears there is an internal date filter being applied: memberCounter after date filter: 30 However, there is no visible parameter in the UI that clearly explains or controls this behavior. This makes it very confusing to understand why results are capped. Additionally, pagination (?p=106, ?p=107, etc.) loads successfully, but each page returns the same 30 members repeatedly. This suggests either: The crawler is scraping only server-rendered HTML while Skool loads members dynamically via JS/XHR Or there is an internal slicing/filtering limit hardcoded to 30 The current setup makes it impossible to scrape full member lists from larger communities. Suggestions: Expose and document any internal date filtering logic Clarify whether this actor supports JS-rendered member lists Consider switching to Playwright/Puppeteer or directly hitting Skool’s API endpoints Add clear documentation about pagination behavior Right now, the behavior is misleading because the UI suggests full scraping capability, but the actual output is capped at 30 members. Would appreciate clarification from the dev team.” — 3/5
Does it return everything
0 ↑ · 1 ↓ of 1cannot scrape full member lists
Setup and docs
0 ↑ · 1 ↓ of 1unclear or missing documentation
What it supports
0 ↑ · 1 ↓ of 1JS-rendered member lists handling
Every count is a review we read.
4 of the 7 said only that they liked it, with nothing specific — those are excluded from the themes above.
Quotes are one reviewer, unedited.Read all 7 →
Recorded changes
showing 3 of 4 in the last 30 days · followers get all 4 by email
- 2026-09-07reviewsNew reviews+1 (23 total)+123 total
- 2026-09-02qualityQuality grade changedC → B—on record
- 2026-09-02reviewsNew reviews+1 (22 total)+122 total
Follow this actor, compare it against its rivals, and get
every overnight change in one morning report.
Publish it yourself? Claim your publisher page and its full history is
yours free, forever.
Open in the app
Publish this actor? Claim the page
Numbers on this page are measured only by an independent census of the Apify Store — not self-reported.
memo23
Skool