💬 Skool Posts & Comments Scraper — Full Threads & Engagement

Scrape any Skool community's feed — posts AND their complete, nested comment trees — in one run. For every post you get the title, body, author, timestamp, likes and comment count; for every reply you get the author, text, time, likes and how deep it sits in the thread. Filter by date for incremental pulls, and turn on the monitor to get alerted the moment a new post drops. Public communities need no login; bring your own Skool cookie for member-only data.

Only checks your User-Agent — no captcha, no headless browser, no flaky login flow. Posts come straight from Skool's server-rendered page data; comments come from Skool's own public JSON API, so the full reply tree comes back intact.

---

Why this one

Most Skool scrapers stop at the post and hand you a flat list with no replies, or scrape only what's on the first screen. This one is built around the thread:

• ✅ Full nested comment tree — every reply and reply-to-a-reply, with a depth field so you can rebuild the conversation
• ✅ Posts and comments in one run — no second actor, no stitching two datasets together
• ✅ Real engagement numbers — likes and comment_count on posts, likes on every comment
• ✅ Date filter — postedAfter for clean incremental/delta pulls instead of re-scraping everything
• ✅ New-post monitor with Slack / email / webhook alerts — pair with a Schedule
• ✅ Public communities work with zero login; private/paid communities work with your own Skool cookie

---

What you get

Per post: title · body · author_handle · author_name · author_id · likes · comment_count · pinned · category (label) · created_at · updated_at · post_url · id

Per comment / reply: text · author_handle · author_id · likes · depth (0 = top-level) · is_reply · parent_id · root_post_id · parent_post_title · created_at · comment_url · id

Export to CSV / JSON / Excel, or pull via the Apify API into your warehouse, a sentiment model, n8n, Make, or a Clay table.

---

How to use it

1. Click Try for free.
2. Paste a community URL (e.g. https://www.skool.com/ai-automation-society) — or just the slug.
3. Keep Include comments & replies on for full threads (turn it off for a faster, posts-only run).
4. Click Start, then open the Dataset tab (switch the view between Posts and Comments & replies).
5. For a live feed: turn on Monitor mode + a Schedule to get alerted when a new post lands.

Quick start (public community, no login)

{ "communityUrl": "https://www.skool.com/ai-automation-society", "maxItems": 50, "includeComments": true }

Incremental / delta pull

{ "communityUrl": "ai-automation-society", "postedAfter": "2026-06-01", "includeComments": true }

Private / paid community (your own membership)

{ "communityUrl": "https://www.skool.com/your-paid-group", "skoolCookie": "auth_token=eyJ…", "maxItems": 0 }

Daily new-post monitor

{ "communityUrl": "ai-automation-society", "monitorMode": true, "slackWebhookUrl": "https://hooks.slack.com/services/…" }

---

Who it's for

• 🧠 Community operators & ghostwriters — pull the whole feed to study what gets engagement
• 📈 Market & sentiment research — mine posts + comments for pain points, objections, requests
• 🤖 AI / RAG builders — turn a community's threads into a clean dataset for a model
• 🔔 Members who can't keep up — monitor mode pings you when a new post drops
• 🗂️ Course / cohort owners — archive your own community's posts and discussions

---

Pricing (pay-per-event)

You pay per record returned — no monthly subscription, no per-run minimum.

Event	What it covers	Suggested price
lot-scraped	each post or comment returned	~$1 / 1,000 ($0.001)
lot-detail-enriched	each post we open to pull its comment tree	~$1 / 1,000 ($0.001)
monitor-run-completed	each scheduled watch run	~$0.05 / run
new-lot-detected	each newly-seen post in monitor mode	~$0.01
alert-delivered	each Slack / email / webhook alert	~$0.005

A 50-post run with comments on a busy community is typically a few cents. Posts-only runs are cheaper — turn off Include comments & replies.

---

How it compares

	This actor	Typical Skool scraper	Leading Skool suite	Budget clone
Posts (title, body, author, time)	✅	✅	✅	✅
Full nested comment tree	✅ every reply + depth	❌ none / first level only	⚠️ flat, no nesting	❌
Likes + comment count	✅ both	⚠️ posts only	✅	⚠️
Date / delta filter	✅ postedAfter	❌	⚠️	❌
New-post monitor + alerts	✅ Slack / email / webhook	❌	⚠️ extra actor	❌
Private community (your login)	✅ your own cookie	⚠️ sometimes	✅	❌
Pricing	per-result, $0.001	monthly	monthly	per-result

Generic comparison — not a claim about any specific provider.

---

Related Skool & community actors (ours)

Actor	What it pulls
Skool Posts & Comments Scraper (this)	Posts + full nested comment threads + engagement
Eventective Scraper	Event vendor & venue leads + emails
BounceGuide Scraper	Party-rental company leads by state/city

---

Notes & limits

• Public community data. Post and comment content, authors, and engagement are visible to anyone who opens the public community page; this actor reads the same data. You are responsible for compliant use of what you collect (GDPR / local law) and for respecting Skool's Terms.
• Private/paid communities use your own login. The skoolCookie is your personal auth_token — it is sent only to Skool, never stored or logged. Only use it on communities you are a paying/approved member of.
• No double-counting in monitor mode — seen post IDs are remembered in a named store, so each post is alerted once.
• depth rebuilds the thread: 0 = top-level comment, 1 = reply, 2 = reply-to-a-reply, and so on.

---

FAQ

Does it get the comments, not just the posts? Yes — that's the point. With Include comments & replies on, every post's full nested reply tree is pulled and flattened with a depth field so you can reconstruct the conversation.

Do I need to log in? No, for public/free communities. Only private/paid communities need your own Skool cookie.

Where do I get the cookie? Log into Skool in your browser, open DevTools → Application → Cookies → skool.com, copy the auth_token value, and paste it (raw, or as auth_token=…). It's marked secret and is never logged.

Can it scrape a community I'm not a member of? Only if it's public. Private communities require you to be a member (your cookie).

How do I do an incremental update? Set postedAfter to your last run's date. It stops paging once it reaches older posts and skips older comments.

How do I only get new posts? Turn on Monitor mode and add a Schedule. It diffs against the previous run per community and outputs/alerts only new posts.

How many posts can it pull? Set maxItems: 0 for the entire community (can be thousands). The default 50 keeps test runs fast and cheap.

What's the category field? Skool communities organize posts into labels/channels (e.g. "General Discussion", "Support"). We map each post's label to its display name.

Does it handle @mentions in the text? Yes — Skool's [@Name](obj://user/…) mention markup is normalized to a readable @Name.

Is it blocked by anti-bot? No captcha or JS challenge — Skool only checks the User-Agent, which the actor sends, with proxy rotation and retries for reliability.

Can I get posts only (no comments)? Yes — turn off Include comments & replies for a faster, cheaper run.

Why per-result pricing instead of monthly? You only pay for what you pull. A small run costs a few cents; you're never locked into a subscription.