Skool API: No Public API, Zapier on Pro, and What Actually Works

Skool has no public API and no developer documentation. The only official integration is the Zapier plugin, and it is locked to the $99 per month Pro plan. The Hobby plan gets no API key, no Zapier, and no webhooks. Everything else you will find online, including the internal api.skool.com endpoints and the n8n templates built on them, is unofficial and can break without notice.

That is the whole answer for most people. The rest of this page covers what the Zapier connection can actually do, where the API key lives, what Zapier MCP adds for AI agents, and the honest state of webhooks and third-party bridges, so you can decide whether Pro is worth $90 more a month for the integration alone.

What the Skool Zapier Plugin Can Do

Zapier lists four Skool events, and Skool's own help center documents the same four. Two are triggers, which start a Zap when something happens in your group, and two are actions, which Zapier performs inside your group after another app fires.

Both triggers are polling triggers. Zapier checks Skool for new data on a schedule rather than receiving an instant push, and on Zapier's free plan that check runs every 15 minutes. A new member can therefore sit in your group for up to a quarter of an hour before the CRM hears about it. Paid Zapier plans poll faster.

Notice what is missing. There is no trigger for a new post, comment, level-up, cancellation, or failed payment, and no action to remove a member or post on their behalf. If a workflow depends on any of those, Zapier will not deliver it and neither will anything official.

Where the Skool API Key Lives (Pro Only)

The key is generated inside the group, not the account. Open your community's settings, go to the Plugins menu, and click edit next to the Zapier plugin. That panel holds the on/off toggle, the API key, a refresh button, and short setup notes. Zapier then asks for two things when you connect: the API key and the back half of your group URL, so for skool.com/your-group you paste your-group.

• Refreshing the key breaks every existing Zap until you reconnect each one with the new key. Skool warns you first, and Zapier emails when a Zap fails.
• On Hobby the Zapier plugin does not appear at all. Upgrading to Pro turns it on immediately, and the Skool pricing breakdown shows what else the $99 tier adds.
• The key is scoped to one group. A second community needs its own Pro plan and its own key.

Three Skool Automations Worth Building

Skool's help center walks through four setups, and three of them cover most of what owners actually ask for.

• Paid member to CRM. Trigger on New Paid Member, send first name, last name, and email to HubSpot, ActiveCampaign, or a Google Sheet. This is the one automation almost every paid group should run, because Skool ships no email broadcasts of its own.
• Applications to a lead list. Trigger on Answered Membership Questions and write the answers to a sheet or CRM. Owners of free groups use this to sell to applicants who never convert inside the community.
• External purchase to course access. Trigger on a Stripe, ThriveCart, or Shopify sale, then run Invite Member followed by Unlock Course for Member. That lets you sell a course on your own checkout and deliver it inside Skool without touching the group's built-in pricing.

The Skool payouts breakdown matters for that third setup: money collected on an external checkout never touches Skool's 2.9% or 10% fee, but it also never appears in Skool's member billing, so refunds and access removal become your job.

Webhooks, MCP, and n8n: What Exists and What Does Not

Skool has no native webhooks. The closest official option is chaining a Skool trigger into Webhooks by Zapier, a premium Zapier app, which then posts the payload to any URL you control. That works, with the same polling delay, and it means a paid Zapier plan on top of Skool Pro.

Zapier MCP is the newer piece. Zapier's Skool listing exposes the two Skool actions, Invite Member and Unlock Course for Member, through its MCP server so an AI agent in Claude, ChatGPT, or Cursor can call them in plain language. It is Zapier's product, not Skool's, and it inherits the same Pro-plan requirement, but it is currently the only supported way to let an agent act inside a Skool group.

Everything else is reverse-engineered. The Skool web and mobile apps talk to internal endpoints on api.skool.com, and developers have mapped enough of them to build n8n workflows, Apify scrapers, and community bridges. None of it is documented, rate limits are unknown, and Skool can change or block it whenever the app ships an update. Use it for personal scripts, never for anything a client is paying you to keep running.

Does the Hobby Plan Get Any Integration?

No. Hobby includes the membership-questions plugin, the chat and posting gates, and native payments, but the Zapier plugin, AutoDM, onboarding videos, and multiple admins are all Pro features. If you need Skool to talk to a CRM or an external checkout, the $99 plan is the price of admission, and the Hobby vs Pro fee math shows the point where the lower transaction fee pays for the upgrade anyway.

For a wider view of what Skool does and does not automate compared with Circle, Kajabi, or Mighty Networks, the full Skool review covers the platform, and the nine-platform alternatives lineup names the tools that ship real APIs.