📅 Skool Events Scraper — Community Calendar & Reminders

Pull every event from a Skool community's calendar in seconds — title, description, start/end time (with timezone), recurring flag, host, location and the join link. Public communities scrape with no login; for members-only calendars, bring your own Skool login. Turn on Monitor mode + a Schedule to get a reminder feed: a Slack / email / webhook ping the moment a community posts a new event. From ~$0.004 per event.

No browser, no anti-bot fighting — Skool server-renders its calendar, so this reads it straight from the page.

---

Why this one

Most Skool scrapers grab posts, members or community metadata and skip the calendar entirely. This actor is built for the events lane and does it cleanly:

• ✅ Full event detail — title, description, start/end datetime (ISO with offset), per-event timezone, cover image, host
• ✅ Recurring-aware — detects recurring series and (optionally) emits every occurrence as its own dated row
• ✅ Location-typed — physical address, online/video link, or a linked Skool page, plus the raw join link
• ✅ Multi-community — pass a list of communities and pull them all in one run
• ✅ Public lane needs no login — and a member-only lane when you supply your own Skool cookie
• ✅ A new-event monitor — schedule it and get reminders for newly-posted events (no other event actor offers this)

---

What you get (per event occurrence)

title · description · startTime · endTime · timezone · recurring · host · locationType · locationLabel · link (join URL) · address · coverImage · reminderDisabled · hasAccess · eventId · occurrenceId · createdAt · updatedAt · groupId · communitySlug · communityName · eventUrl · is_new · scraped_at

Export to CSV/JSON/Excel or pull via the Apify API into Google Calendar, Notion, n8n, Make, or your CRM.

---

How to use it

1. Click Try for free.
2. Paste one or more communities — a URL (https://www.skool.com/ai-automation-society) or just the slug (ai-automation-society).
3. Click Start, then open the Dataset tab.
4. Members-only calendar? Paste your own Skool auth_token cookie in Your Skool login (see FAQ).
5. For a reminder feed: turn on Monitor mode + an Apify Schedule to be alerted when new events are posted.

Quick start (public community)

{ "communities": ["ai-automation-society"], "maxItems": 50 }

Daily new-event reminders

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

Members-only calendar (your own login)

{ "communities": ["my-private-community"], "skoolCookie": "<your auth_token value>" }

---

Who it's for

• 🗓️ Members who want every community's events in one calendar / one feed
• 🔔 Community managers tracking what other communities run and when
• 🤖 Automators piping Skool events into Google Calendar, Notion, n8n or Make
• 📊 Researchers / analysts studying event cadence across communities

---

Pricing (pay-per-event)

Event	What it covers	Suggested price
lot-scraped	each event occurrence returned	~$0.004 / event (~$4 / 1,000)
monitor-run-completed	each scheduled watch run	~$0.05 / run
new-lot-detected	each newly-posted event occurrence	~$0.02
alert-delivered	each Slack / email / webhook reminder	~$0.005

You're charged per result, not per run, and never for the actor start. The new-event monitor remembers what it has seen, so you never pay for or get reminded about the same event twice.

---

Related Skool actors (our suite)

Actor	What it pulls
Skool Events Scraper (this one)	Community calendar events + new-event reminders
Skool Posts Scraper	Feed posts, comments, engagement
Skool Members Scraper	Community member rosters
Skool Profile Scraper	Individual member profiles
Skool Community Scraper	Community metadata & stats
Skool Discovery Scraper	Discover/browse public communities

---

Notes & legal

• Public community data. A community's calendar is fetched the same way your browser renders it. For members-only calendars you must supply your own Skool login (auth_token) — you are accessing only data you already have access to. We never log or store your cookie.
• You are responsible for using the data in line with Skool's Terms and applicable law.
• No double-counting — monitor mode keys on each event occurrence and emits/reminds once.

---

FAQ

Does it need a login? No — for public communities. The daily demo and most communities work with no cookie. Only members-only calendars require your own Skool auth_token.

How do I get my auth_token? Log into Skool in your browser → DevTools (F12) → Application → Cookies → www.skool.com → copy the auth_token value → paste it into Your Skool login. It's optional and only needed for private calendars.

How are recurring events handled? Each occurrence is detected and flagged recurring: true. By default every occurrence is its own dated row (occurrenceId); flip Include every recurring occurrence off to collapse a series to its next occurrence only.

Can I watch several communities at once? Yes — pass a list in communities. The monitor tracks all of them in one scope.

What time zone are events in? Each event carries its own timezone (events can differ within one calendar); the calendar's default timezone is used as a fallback. startTime/endTime are ISO-8601 with the UTC offset baked in.

Why don't I get any events for a community? Its calendar may be members-only (you'll see a warning to add your skoolCookie) or it simply has no upcoming events.

Is there a host/organizer field? host is derived from the community owner. Skool's public calendar payload doesn't attach a per-event organizer, so per-event host isn't always available on the public lane.

Will it break when Skool redeploys? No — it reads Skool's dynamic build id at runtime and falls back to the rendered calendar page, so it keeps working across deploys.