Set up a welcome sequence
A sequence is an ordered series of emails sent automatically—the classic use is a welcome series introducing new readers to you and your books. They live under your audience's Automations.
Building one
Create a sequence, pick its trigger, and write the emails with a delay before each one:
- A form—fires when someone signs up through that form (after confirmation, if it's double opt-in)
- A tag—fires the moment that tag is added to a reader, including by an integration
- Manual—you enroll readers yourself from their subscriber page
Then activate it. New readers matching the trigger start receiving the series; each reader gets each email once.
Good to know
- Enrollment is once per reader. Someone who signs up through the same form twice doesn't restart the series.
- Existing readers aren't swept in when you activate—triggers fire on new events, so your long-time subscribers won't suddenly get your welcome email. (Want specific people in it? Enroll them manually.)
- Pausing freezes everyone where they are—including emails already queued for delivery, which are held with the sequence. Reactivating resumes everyone and releases the held emails, using the latest content—so pausing to fix a typo works exactly the way you'd hope.
- A reader who unsubscribes mid-sequence exits immediately, wherever they were.
Migrating from another platform? Build and activate your welcome sequence here, then turn the old platform's welcome automation off. Both running at once means new readers get two welcome series in parallel.
Coming from MailerLite? The current MailerLite (dashboard.mailerlite.com) can hand its automations over—Automations → Import from MailerLite brings each one's trigger, waits, branches, and subject lines into a draft sequence. MailerLite Classic doesn't share automations over its API at all, so a Classic automation is rebuilt here by hand (your subscribers and groups still import fine). One workaround if you have many Classic automations: MailerLite's own free Classic-to-new migration moves most workflows across—run it first, spot-check the results, and then the importer here can read them from the new platform.