--- title: "Skool Integration" description: "Read Skool community data from AI agents: list members, look up a member's role, level, and points, and pull community metadata. Skool has no official public API, so an authenticated passthrough action reaches any Skool-compatible endpoint you have access to." url: https://flowrunner.ai/integrations/skool date_modified: 2026-08-04T10:04:16-07:00 --- # Skool [Social Media](https://flowrunner.ai/integrations/category/marketing-social) Read Skool community data from AI agents: list members, look up a member's role, level, and points, and pull community metadata. Skool has no official public API, so an authenticated passthrough action reaches any Skool-compatible endpoint you have access to. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 4 actions · API key · available [Skool website](https://skool.com/) · [Platform Documentation](https://www.skool.com) · Capability data verified 2026-07-27 1. The weekly community health schedule fires on Monday morning 2. Get Community reads the group's name, description, and current member count 3. List Members pages through the roster with each member's role, level, and points 4. The agent compares the roster against last week's export to find joins, departures, and members whose activity points went flat 5. Joins and departures append to the tracking sheet, and flat members are collected into a re-engagement list 6. The digest posts to the team channel: net growth, notable level-ups, and the at-risk list 7. The community manager reviews the at-risk list and decides who gets a personal check-in versus the standard re-engagement email ## What This Integration Enables A Skool community is a membership business, and its most valuable dataset, who the members are, what they have earned, and whether they are still showing up, has no official public API. Skool's first-party integrations are webhook-based, and there is no developer portal. This connector deals with that reality honestly: List Members, Get Member, and Get Community target the plausible endpoint shapes of whichever Skool-compatible API or proxy you configure, and Send Custom Request is an authenticated passthrough that reaches any endpoint those convenience actions do not cover. The convenience actions should be smoke-tested against your specific API before production use; the passthrough is the reliable workhorse. That caveat stated, the payoff is real: the roster stops being trapped behind an admin login and becomes data your agents can act on. - Export and sync membership rosters into spreadsheets, CRMs, and email tools on a schedule - Look up a member's role, level, and points mid-workflow to route decisions - Pull community metadata for growth reporting without logging in - Reach any Skool-compatible endpoint through one authenticated passthrough ### Without FlowRunner **The roster lives behind a login**: Member data exists only inside Skool's admin screens, exported by hand when someone remembers **Churn discovered after the fact**: A member's points went flat weeks before they left, and nobody was looking **Community data disconnected from the business**: The CRM, the email tool, and the community roster are three unreconciled lists ### With FlowRunner **Membership as queryable data**: Agents pull the roster, roles, levels, and points on a schedule into sheets and CRMs **Early-warning signals surfaced weekly**: Flat activity points become a reviewed list, not a post-mortem finding **One member record across tools**: Skool membership syncs into the same records the rest of the operation runs on ## Use Case Scenarios ### The roster that keeps itself current A course creator runs a paid community alongside an email list. A nightly agent calls List Members, diffs the roster against the synced copy in [Google Sheets](https://flowrunner.ai/integrations/google-sheets), and reconciles the differences: new members get tagged in the email platform and receive the onboarding sequence, departed members get suppressed from paid-member campaigns. The creator stops discovering that they emailed member-only content to people who churned two months ago. ### Points as an early-warning system Skool's gamification means every member carries a live engagement signal: their points and level. A weekly agent pulls the roster, compares each member's points to the prior snapshot, and builds a list of paying members whose activity went flat. The list posts to [Slack](https://flowrunner.ai/integrations/slack) with each member's tenure and level attached. The community manager picks who gets a personal message, because a founder's check-in retains members that an automated drip does not. ### The passthrough as coverage insurance An operator's Skool-compatible proxy exposes an endpoint the convenience actions do not model. Instead of waiting for a connector update, the agent calls Send Custom Request with the path, method, and query parameters, and the response flows into the same workflow. When the team's needs outgrow the modeled actions, the integration stretches instead of breaking, and Get Member still handles the common case of hydrating one member's profile before a routing decision. ## Human-in-Loop Highlight Send Custom Request is deliberately unconstrained: it sends whatever method, path, and body you give it, authenticated, to an API surface that Skool has never publicly documented. A GET that guesses wrong returns an error. A POST or DELETE that guesses wrong mutates production community data through an unofficial endpoint, with no documented contract for what it just changed and no support channel to appeal to. So FlowRunner workflows split the passthrough by method: reads run at machine speed, and any mutating request pauses with the full method, path, and body in front of a person before it is sent. The same discipline applies downstream of the reads: the at-risk list an agent builds from flat points is a hypothesis, and the member-facing message it triggers goes out only after the community manager decides who hears from a human and who hears from a sequence. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via preferred channel Human decides Agent resumes with decision ## Agent Capabilities 4 actions ### Passthrough 1 - **Send Custom Request** Sends an authenticated request to any Skool-compatible endpoint: your choice of HTTP method, query parameters, and JSON body, with the API key as a Bearer token. The most reliable action in the connector, and the one this page's human gate exists for when the method mutates. ### Members 2 - **List Members** Lists a community's members with pagination, targeting the standard members endpoint shape of your configured API. The roster pull behind syncs, diffs, and health reports. Smoke-test against your API before production use. - **Get Member** Retrieves a single member by ID, including profile, role, level, and points. Used to hydrate one member's context before a routing or outreach decision. ### Community 1 - **Get Community** Retrieves community metadata such as name, description, and member count. The lightweight read behind growth reports and notifications. ## Frequently Asked Questions ### What can FlowRunner do with Skool? FlowRunner agents can run Send Custom Request, List Members, and Get Member in Skool, plus 1 more action. ### Does connecting Skool to FlowRunner require OAuth? No. Skool connects to FlowRunner with an API key, no OAuth flow required. ### Can Skool trigger a FlowRunner workflow automatically? Skool doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Skool?** This integration exposes Skool to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/skool. Site index: https://flowrunner.ai/llms.txt