Skool Community Lead & Engagement Extractor

Turn public Skool communities into structured B2B intelligence for prospecting, creator research, audience analysis, and community-led growth.

Provide one or more public Skool community URLs and receive clean dataset records for community information, owners, members, posts, comments, engagement, leaderboards, and recurring topics.

Public content only: This Actor does not log in, join communities, bypass access controls, or collect private content. Results depend on what Skool makes publicly visible to an unauthenticated visitor.

Why use this Actor?

Capability	What you get
Community intelligence	Community name, description, owner, membership model, member counts, post counts, courses, modules, visible tabs, and canonical URL
Lead discovery	Public member names, handles, profile URLs, bios, avatars, and linked social profiles
Engagement analysis	Post text, authors, dates, likes, comments, bounded comment records, and aggregate totals
Creator research	Owner profile, public bio, website and social links, role, and community context
Topic discovery	Recurring keywords ranked by document frequency across extracted posts and comments
Resilient crawling	Browser rendering, retries, session rotation, proxy support, pagination guards, timeouts, and route-level error isolation

Quick start

1. Add community URLs

In the Actor input, add one or more public Skool URLs:

{
  "startUrls": [
    { "url": "https://www.skool.com/your-community" }
  ]
}

You can also paste URLs directly into the Skool community URLs field in Apify Console.

2. Choose your extraction scope

The defaults are designed for a useful first run. Increase limits for larger research jobs or disable expensive enrichment when you only need community-level data.

{
  "maxCommunities": 10,
  "maxMembers": 500,
  "maxPosts": 100,
  "maxCommentsPerPost": 500,
  "includeProfiles": true,
  "includeComments": true,
  "includeLeaderboard": true,
  "includeKeywords": true
}

3. Run and export

Start the Actor, open the Dataset tab when the run completes, and export the results as JSON, CSV, Excel, or any other format supported by Apify.

Input reference

Input	Type	Default	Description
startUrls	Array	https://www.skool.com/growth	Public Skool community URLs to process
maxCommunities	Integer	10	Maximum communities to process
maxMembers	Integer	500	Maximum member profiles discovered per community
maxPosts	Integer	100	Maximum public posts extracted per community
maxCommentsPerPost	Integer	500	Maximum comment texts retained per post
includeProfiles	Boolean	true	Visit public member profiles for bios and social links
includeComments	Boolean	true	Emit individual comment records in addition to post metrics
includeLeaderboard	Boolean	true	Extract public leaderboard entries when available
includeKeywords	Boolean	true	Calculate recurring keywords from posts and comments
proxyConfiguration	Object	Apify Proxy	Proxy settings; residential proxies are recommended for larger runs
requestTimeoutSecs	Integer	45	Maximum navigation/profile request time
renderWaitMs	Integer	1200	Wait time for client-rendered content after navigation

Dataset output

The Actor writes one normalized dataset containing several record types. Filter by recordType to build the view you need.

Record type	Contains
community	Community metadata, owner, counts, visible tabs, canonical URL, and public-access status
member	A discovered public member or owner record
member_profile	Enriched public profile with bio, avatar, handle, and social links
post	Post URL, text, author, date, likes, and comment count
comment	Bounded public comment text associated with a post
leaderboard	Rank, member, points, level, and activity text
keyword_summary	Recurring keywords and document frequency
community_metrics	Extracted post, like, comment, member, and leaderboard totals
error	Structured failure information when a community cannot be navigated after retries

Example community record

{
  "recordType": "community",
  "communityName": "Example Community",
  "communityUrl": "https://www.skool.com/example",
  "stats": {
    "totalMembers": 1250,
    "totalPosts": 480,
    "totalCourses": 12
  },
  "owner": {
    "name": "Community Creator",
    "bio": "Public creator bio",
    "profileUrl": "https://www.skool.com/@creator",
    "socialLinks": [
      "https://www.linkedin.com/in/creator"
    ]
  }
}

How reliability works

The Actor is designed for long-running research jobs:

• Rendered-page extraction handles Skool’s client-side interface.
• Payload-first parsing uses public page data when it is more complete than visible HTML.
• Automatic retries recover from transient navigation and network failures.
• Session rotation helps isolate problematic browser sessions.
• Proxy support is enabled through Apify Proxy by default.
• Pagination guards prevent infinite “load more” loops.
• Record isolation means a failed profile or unavailable route does not discard successful community records.
• Visibility reporting distinguishes unavailable private content from an empty community.

Proxy and scale recommendations

For small tests, the default configuration is sufficient. For larger runs:

1. Use Apify Proxy with a residential group.
2. Keep per-community limits realistic.
3. Start with a small sample and increase maxMembers and maxPosts gradually.
4. Use includeProfiles: false if you only need community and post-level intelligence.
5. Review warnings and community_metrics records after each large run.

Responsible use

Use this Actor only for public information and in accordance with:

• Skool’s Terms of Service and robots directives;
• applicable privacy and data-protection laws;
• your organization’s prospecting and outreach policies.

Do not use extracted data for harassment, deceptive impersonation, unauthorized account access, or sensitive profiling.

Frequently asked questions