Auto-enroll Stripe customers in your Skool community and course

Build a deterministic code workflow that auto-enrolls Stripe buyers into my Skool community and unlocks the course they paid for. No LLM reasoning is needed anywhere in this pipeline. Payment in, invite plus unlock out.

Trigger: a Stripe webhook on a successful payment event. Default to checkout.session.completed, but make it easy to switch to charge.succeeded if I don't use Stripe Checkout. The workflow should ignore any other Stripe event types.

Configuration the user needs to supply once: a mapping table from Stripe product ID (or price ID) to one or more Skool course IDs. Treat the keys as a simple lookup; do not infer anything fuzzy. Example shape: { "prod_ABC123": ["course_skool_xyz"], "prod_BUNDLE": ["course_skool_xyz", "course_skool_pqr"] }.

Steps in order:

1. Receive the Stripe webhook. Pull the customer email (from customer_details.email on a checkout session, or by looking up the customer on a charge) and the purchased product or price ID. For checkout sessions, expand line_items so the product/price ID is available. For charges, use the price/product on the associated invoice line item or subscription.

2. Look up the product or price ID in the configured mapping table. If there is no match, write a log entry that says the event was skipped along with the product ID and the customer email, then exit successfully. Do not send any invite. Do not unlock any course.

3. If there is a match, call the Skool Invite Member action with the customer email so the buyer receives the join email for the community.

4. For every mapped Skool course ID, call the Skool Unlock Course action with the customer email and that course ID so access is granted the moment they accept the invite. If the mapping returns multiple courses, call Unlock Course once per course.

5. Log a success entry with the customer email, the Stripe product ID, and the list of Skool course IDs that were unlocked.

Error handling: if Skool Invite Member fails because the email is already a member, treat that as success and still run Unlock Course. If Unlock Course fails because the member hasn't accepted the invite yet, that's expected on a brand new invite. The Skool action handles the email-based lookup; do not try to wait or retry from inside the workflow. Surface any other errors so I can see them in the run log.

Integrations to use: Stripe (webhook trigger on a successful payment event) and Skool (Invite Member and Unlock Course actions). Do not pull in any other services unless I add them later.

Additional information

What does this prompt do?

The moment Stripe confirms a purchase, the buyer gets an invite email to your Skool community.
The right course unlocks automatically the moment they accept, so they can start learning immediately.
A simple mapping table tells the workflow which Stripe product unlocks which Skool course, including bundles that grant access to several courses at once.
Purchases that don't match a known product are skipped with a log entry instead of breaking the flow, so unmapped sales never trigger a wrong invite.

What do I need to use this?

A Skool group on the Pro plan with the Zapier plugin turned on (so you can grab the API key)
A Stripe account you can send webhook events from
A short list of which Stripe products or prices grant access to which Skool courses

How can I customize it?

Add as many Stripe product to Skool course mappings as you sell, including bundles where one purchase unlocks more than one course.
Choose which Stripe event drives it. Stripe Checkout sellers usually use the completed checkout event, while custom payment flows use the successful charge event.
Layer on extra welcome steps like tagging the buyer in your CRM, sending a personal welcome note, or posting a quiet sales ping in Slack.

Frequently asked questions

Will this work if I sell through Stripe Checkout, payment links, or a custom checkout?

Yes. As long as Stripe sends a successful payment event, the workflow picks it up. Stripe Checkout, payment links, subscriptions, and custom integrations all work the same way.

What happens if someone buys a product I haven't mapped to a Skool course yet?

Nothing breaks. The workflow records a skip entry so you can see the unmapped sale, and you can add the mapping later. No invite is sent and no course is unlocked until you decide what should happen.

Can a single purchase unlock more than one course?

Yes. Your mapping can return several Skool course IDs for one Stripe product, and the workflow unlocks each of them for the new member. Bundles and all-access passes work exactly the same as single-course sales.

How quickly does the buyer get their Skool invite after paying?

Within seconds. Stripe fires the payment event the moment the charge succeeds, the invite goes out right away, and the course unlock happens immediately after so access is ready when they accept.

Do I need a Skool Pro plan for this to work?

Yes. Skool's automation features are only available on the Pro plan. Hobby plan groups don't expose the API key needed to invite members or unlock courses from outside.