A new edition
The Sunday Letter, edition 41: three things worth your time this week, and the one we got wrong last week. [link]
Free guide
The BlastsFlow Publisher's Guide
How to turn each publication you run into a list readers choose, bring your readers in by email first, give each publication its editor and schedule, and publish every edition to the people who asked for it.
Written for editors-in-chief, editors and whoever runs the publishing schedule at a publisher setting up BlastsFlow.
1. What BlastsFlow is
BlastsFlow is the Blasts Hub for publishers. Your readers subscribe to publications by name, and each edition is the thing they asked for. In the Hub, each publication is an audience readers choose, and each edition is a message to that audience.
Editions reach readers by email from the first day, with nothing installed, and directly on their phone or computer once they connect on Blasts with the same email address.
2. Decide what your publications are
Name each publication the way readers know it. A publication is something readers choose and expect again, not a cadence: "The Sunday Letter" is a publication, "Weekly" is not.
- One audience per publication, left open so readers choose it.
- A one-line description on each: what it covers and how often it arrives.
- Announcements, already created for you, for news between editions.
- Groups you fill yourself, like contributors or beta readers, set to organization assigns so readers never see them.
There is no paid tier or early-access audience in the Hub. Anything left open can be chosen by any reader.
3. Bring your readers, email first
Prepare an export
From wherever your readers are today: email, name and an audiences column naming the publications each reader chose. Every other column, like a plan, paid status or open history, is discarded before anything is saved.
Import and confirm
Import on Subscribers and confirm your readers agreed to hear from you. Each becomes an email subscriber in the publications named for them.
Point your sign-up form at the Hub
The inbound webhook on Integrations turns each new sign-up into an email subscriber with the publications they picked.
4. The Blasts connection and the same-address rule
Anyone who uses Blasts can enter your enrollment code in the app, which sends you a connection request. When a reader connects with the same email address they subscribed with, their editions move to Blasts on their own.
A reader who connects with a different address is a separate person in your Hub: the publications the first address chose do not follow it, and the first address keeps receiving by email.
5. Editors and approval
Invite each editor on Team as a Leader and grant them the publications they edit. An editor publishes to those publications and reads their readers' replies, and nothing else.
Approval is on by default: an editor's edition waits under Sent & Scheduled until an owner or administrator approves it. Settings can turn it off.
6. Publish an edition
Compose an edition, pick the one publication it belongs to, send a test to yourself, then send now or schedule it. Templates cover a new edition, a special edition, a schedule change, a correction, a reader question and a new publication.
Files you attach reach readers on Blasts only. The email edition carries the edition itself, so link to anything an email reader needs.
7. Run a publication's schedule as a Content Series
Write the next month of a publication's editions at once as a Content Series on its audience, set its day and time, and the Hub releases each one on schedule. A reader who subscribes midway receives the next edition, not the backlog. A paused series skips the dates it missed.
Series editions are text. An edition with images or files goes out through Compose, now or scheduled. Content Series is included from the start.
8. Replies
A reader's reply to an edition becomes a private conversation with the editors of that publication. Readers never see each other's replies. Replies can be turned off for any single edition.
9. STOP and START
A reader who replies STOP receives nothing more and is removed from every publication. If they reply START later, messages turn back on, but no publication is restored: they choose their publications again on their preferences page.
10. New Reader Welcome (Hub Pro)
A short Journey on one publication's audience, started for readers who join from now on only, so an imported list is never welcomed as if it had just arrived. The starter says what the publication is, what to expect and where to change choices. Hub Pro unlocks at $500 in cumulative Blast Credit purchases.
11. Editions from your own systems
If a system you run produces editions, BlastsHub staff can register it as a producer for your organization. Each item it files waits in your review queue, shown exactly as readers would receive it. A person presses Publish, which sends it now to its audience. The queue never schedules and never sends on its own.
12. Cost
Standard Blast Credits, with no BlastsFlow subscription: one edition on Blasts to one reader is one Blasts credit, and one email is one email credit. Credits never expire. Every new Hub includes 50 email credits.
Your first four weeks
A calm way to move one publisher onto BlastsFlow.
Week 1 Publications and editors
Create one audience per publication with its description, invite your editors and grant each one their publications.
Week 2 Readers
Import your opted-in readers with their publications, and point your sign-up form at the inbound webhook.
Week 3 Start publishing
Publish the next edition of each publication to its readers, and load the regular ones as Content Series.
Week 4 Blasts, for readers who want it
Put your enrollment code in the footer of your editions and on your sign-up pages, so readers who use Blasts can connect with the same address.
What BlastsFlow does and does not do
- Delivers each edition to the readers who chose that publication, by email and on Blasts.
- Lets readers choose and drop publications on their preferences page.
- Releases a publication's prewritten editions on its schedule as a Content Series.
- Routes readers' replies privately to the editors of that publication.
- Holds editions from a registered producer until a person publishes them.
- Host a website, archive or paywall for your publications.
- Bill readers, or know anything about what a reader pays.
- Know who read an edition or what they did next.
- Write, generate or publish editions by itself.
- Schedule an item from the review queue: publishing sends it now.
Every edition is written by your team or a system you run, and sent by a person, on a schedule a person set, or from the review queue by a person.
Ready when you are
Sign in, create an audience for each publication, bring your opted-in readers, and publish the next edition to the people who chose it. The Help covers each step in more detail.
See it at the example publisher Roundmark Publishing (a fictional example organization created to show the product, not a customer)
Product facts on this page reflect published Blasts.app information as of September 24, 2026.