Zapier and Webhooks

Skool has no public API; use Zapier or webhooks. Zapier provides the documented bridge for supported Skool events and actions, while Webhooks by Zapier can pass data to or from other systems.

What you need

As of July 2026, the Skool Zapier integration was available on Pro, not Hobby. It was enabled from Plugins in group settings and used a separate API key for each group.

Keep the key in a secret manager. Record which group and Zap use it, but never put the key itself in a shared note. Refreshing a key breaks existing Zaps until they are rebuilt.

Supported Skool events

• Answered Membership Questions sends submitted application answers into a Zap.
• New Paid Member starts after payment and group entry.
• Invite Member adds a member and requires an email address.
• Unlock Course for Member grants a specific course and requires an email address.

Use Membership Questions To CRM for the application-answer flow and Classroom Course Structure before automating a course unlock.

Webhooks by Zapier

Webhooks by Zapier can receive requests with Catch Hook or Catch Raw Hook, poll a URL, or send Custom Request, GET, POST, and PUT actions. These are Zapier features. Skool does have one native webhook of its own, a Webhook plugin on the Pro plan, documented as a developer-only feature for automating member invitations from an off-platform action, such as sending a unique email invite link when someone checks out through an external processor.

Catch Raw Hook accepted an unparsed body up to 2 MB. Check the current Zapier limits before choosing payload size or timing.

Setup flow

1. Confirm the group is on a plan that includes Zapier.
2. Enable the plugin and copy the group-specific key into your secret manager.
3. Choose the exact Skool trigger or action.
4. Record the correct group URL slug when the workflow needs it.
5. Map only the fields the destination really needs.
6. Test with non-sensitive sample data.
7. Check invites, course access, CRM records, and error handling.
8. Write a rebuild plan before refreshing the key.

Pitfalls

• A wrong key or group URL can stop the connection.
• Membership-question updates may not be immediate.
• A destination app can reject missing or badly formatted fields.
• Invite and unlock automations can create unintended access.
• Use API And Integration Limits before estimating anything beyond the documented surface.