Email automation sequences

Trigger-based email flows, no external tool needed. Pro plan.

Pro plan
On this page

Set a trigger (a tag being added, a course being completed, etc.), then chain steps — wait, then send an email, or apply another tag. This runs natively without needing Mailchimp or a similar external tool, and is separate from the transactional emails (receipts, password resets) that always send regardless of plan.

Email step content is written with the same rich text editor used elsewhere, automatically converted to email-safe HTML on send (video embeds become plain links, since most inboxes don't run embedded video) and wrapped in your school's branded header/footer.

Deactivating and reactivating

Deactivating a sequence also pauses everyone already in it — they won't get the remaining emails — and no new students join. Reactivate it once you've fixed the content, and paused students carry on from the step where they stopped. Delete the sequence only if nobody should get it anymore. If your plan stops including email automation (for example after a downgrade), or your subscription is past due or your dashboard is locked, sequences pause the same way and carry on once that's resolved.

This is a Pro-plan feature.

Free courses count as a purchase

When a student joins a free course (including rejoining after their access lapsed), it triggers "course purchased" automations just like a paid purchase, and syncs them to your email marketing list (tag free). If a student is refunded, the automations they started by buying that course stop.

Editing a sequence

You can change a sequence at any time: click its name under Email → Automations, or choose "Edit" in the "⋯" menu. The name, the trigger, and each step's wait and content can all be changed, and you can add or remove steps.

  • People already in the sequence aren't thrown off: send times that were already scheduled don't change. If the step someone is waiting on still exists, they keep waiting for it; if you delete it, they move on to the next step that still exists, and if none is left they count as finished.
  • People who already finished the whole sequence are not added again, so a step you add at the end won't be sent to them.
  • Changing the trigger only affects people who qualify afterwards.

Variables, preview and test emails

Email steps can use "Insert variable" just like broadcasts: the student's name ({name}) and the school name ({schoolName}). When the trigger is "Course purchased" or "Course completed" you can also use the course title ({courseTitle}). Every email step has "Preview" and "Send me a test".

If an email uses {courseTitle} but that course has since been deleted, that step is skipped (a raw {courseTitle} is never sent) and the sequence moves on.

Two emails when a student buys a course

When a student pays, the system already sends the "Purchase receipt" by itself (edit it under Email → System emails). A "Course purchased" automation is a separate email: use it for onboarding or a welcome series, not to repeat the receipt.