Sell a Course With Stripe and Automate the Student Emails

Short answer: course email automation starts a sequence the moment a student pays. Send access details straight away, drip one email per module to pace them, nudge students who stop clicking, and offer the next course when they finish. With Stripe connected to your email platform, the payment itself is the trigger, so nobody has to add students by hand.

Selling a course through Stripe is simple. A Payment Link or Checkout page takes the money, and your course platform hosts the lessons. The part that decides whether students finish, and buy again, is the email in between.

Many course creators send a receipt and a login link, then nothing until the next launch. This guide covers the full online course email sequence, how to run one per course, and how to handle payment plans and refunds with Audienceful and Stripe.

The course email automation sequence

Welcome and access, straight after purchase

Trigger the welcome on Payment succeeded. In Audienceful, payment events cover invoices, Stripe Checkout and Payment Links. Students who check out as guests, with no Stripe customer record, still become contacts and get the email.

Keep the first email short. Give the login link, the first lesson to watch, and how to ask for help. Stripe can send the receipt, so you don't need to repeat the amount.

Example welcome:

Subject: You're in, {{first_name}}. Start with lesson 1

Welcome to the course. Here's your login: [Open the course].

Start with Module 1. It's 20 minutes and sets up everything after it. I'll email you as each new module is worth starting, so you never have to wonder what's next.

Pace students through the modules

A drip is the backbone of any course sequence. Instead of leaving students with 40 lessons and no plan, send one email per module, spaced at the pace you'd recommend.

Each drip email does three things: says what this module covers, why it matters, and links straight to it. Two or three days apart suits most video courses. Slower, practical courses can be weekly.

Build it in the same flow as the welcome: email, wait, email, wait. In Audienceful you can also limit which days the flow sends from the automation's settings, if you'd rather not email at weekends.

Nudge students who go quiet

Be honest about what your email tool can see. Audienceful knows whether a student opened or clicked each email. It doesn't know whether they watched a lesson, unless your course platform tells it.

That gives you two levels of nudge:

• Email engagement. Add a conditional after a module email: if they didn't click it, send a short "pick up where you left off" before the next one. Clicks are stronger evidence than opens, because some mail apps open emails automatically. You can also save an audience of students who didn't click a specific email.
• Course progress, via custom events. If your course platform connects to Zapier or can call an API, send a custom event such as lesson_completed or module_finished. Events can start their own flows and update contact fields, so you can nudge on real progress.

Example nudge:

Subject: Module 2 is waiting for you

Hi {{first_name}}, life gets busy. Module 2 is 15 minutes, and it's the one students tell me made the rest click. [Pick up where you left off].

Completion and the next course

When a student finishes, three emails earn their place. Congratulate them, ask what they'd change, and then, a few days later, offer the next step: an advanced course, a cohort or coaching.

If your platform sends a course_completed event, trigger on it. If not, send the completion email at the end of the drip, timed to when most students finish.

Don't pitch a course a student already owns. Tag buyers in each course's flow (for example bought-course-2), then add a conditional that skips the upsell for anyone with that tag.

One sequence per course

Selling more than one course? Each needs its own welcome and drip. Any Stripe trigger in Audienceful can be limited to specific Stripe products, so the course A flow only runs for course A buyers.

Product filters work on subscriptions and invoice payments, because those events list what was bought. A one-off payment made outside an invoice carries no product, so a product-scoped flow won't run for it. It fails closed rather than send the wrong course.

If you sell several courses through one-off Payment Links, pick one of these:

• Use payment plans or invoices. Both carry the product, so product filters work for them.
• Send an enrolled custom event from your course platform, with the course name as an event property. It's the most reliable way to tell courses apart for Stripe course sales emails.
• Selling one course? Skip the filter. One Payment succeeded flow covers it.

Payment plans

A payment plan is usually a Stripe subscription set to end after the last instalment. Every instalment is a payment, so start the course flow on Subscription activated rather than Payment succeeded, and keep it to once per person. That leaves two more flows to get right.

Failed instalments. Trigger the failed payment template on Payment failed: a calm fix-it email, a reminder two days later, a final notice three days after that. Add a goal of Stripe Subscription Status is active so it stops once the card works. More in dunning emails for Stripe.

The plan finishing. When the last instalment is paid and the subscription ends, it arrives as Subscription canceled. If you run a win-back flow for a membership, limit it to membership products. Otherwise students who just paid in full get a "sorry to see you go" email.

Refunds

Trigger a short email on Charge refunded. The Refund follow-up template ("Your refund is on its way") closes the loop gracefully and asks what didn't work. Leave this flow without a product filter, since refund events don't list a product.

The same flow should stop the course emails. Add a refunded tag, and put a conditional before each later module email that skips anyone with that tag. Revoking course access stays with your course platform.

Refunds also come out of your revenue numbers. Audienceful credits each Stripe payment to the email that drove it and nets refunds back out. Here's how revenue attribution works.

How to do it in Audienceful

1. Connect Stripe from Integrations with Stripe Connect. No API key or webhook. Step-by-step.
2. Import past students with the one-time historical import, so past buyers and their total spend are in place.
3. Create the course flow. New automation with the Stripe event Payment succeeded for one-off sales, or Subscription activated for a payment plan. Add a product filter if you sell more than one course on plans or invoices.
4. Add the welcome and the drip. One email per module, with waits between them and {{first_name}} merge tags.
5. Add conditionals for students who didn't click, and a tag for buyers.
6. Add the refund and failed payment flows from the Stripe templates.
7. Switch them on. New automations are always created paused.

Prefer to describe it? The AI agent or MCP server can build the drip from a prompt in Claude or ChatGPT. It arrives paused for you to review.

How this compares with Kit

Kit is popular with course creators. It sells digital products through its own Stripe checkout and connects to course platforms such as Teachable. Its Stripe connection powers Kit's own sales rather than syncing your Stripe subscription and payment events. If your courses already sell through your own Stripe account, a native integration reads those events directly. Our Kit comparison has the detail.

For more, see email marketing for course creators and email marketing for subscription businesses. Running a membership alongside your courses? See membership email automation on Stripe. Coaching too? See Payment Link follow-up for coaches. The Stripe integration page covers every event.

Audienceful is free up to 1,000 contacts, then paid plans start at $29/month billed yearly ($37.50 monthly) for 3,000 contacts. Start free and connect Stripe in a few clicks.

FAQs

How do I send course access emails after a Stripe payment?

Connect Stripe to an email platform that triggers on payments, then start a flow on the payment succeeded event. The first email holds the login link and where to start. Guest buyers from Payment Links are included in Audienceful.

How long should an online course email sequence be?

Roughly one email per module, plus a welcome, a completion email and a next-step offer. Space the module emails at the pace you'd recommend, usually two to seven days apart.

Can I run a separate sequence for each course?

Yes, by limiting the Stripe trigger to a product. That works for payment plans and invoiced sales. One-off Payment Link payments carry no product, so send an enrolled event from your course platform to tell those courses apart.

Can my email tool see whether students watched a lesson?

Not on its own. It sees opens and clicks on your emails. For lesson progress, your course platform needs to send events, through an API or Zapier.

Sources

• Stripe: Guest customers