Newsletter
Pro includes a newsletter engine: it drafts issues, sends them through your own email provider, manages subscribers with double opt-in, and runs automated drip sequences. You bring the provider and the domain.
Email providers
Postwright sends through a provider you own — it is not an email service itself. Two providers are supported out of the box, and a brand can opt to send through the platform that already holds its list (Kit, Mailchimp, Ghost, or Beehiiv) instead:
| Provider | Support | What you set |
|---|---|---|
| Resend | Works out of the box | RESEND_API_KEY, a verified RESEND_DOMAIN, and optionally an audience to mirror subscribers into. The reference setup. |
| Mailgun | Works out of the box | MAILGUN_API_KEY and MAILGUN_DOMAIN. Pick per brand. |
| Ghost newsletter or Beehiiv email | Some setup | Optional, per brand, when the brand’s blog destination is Ghost or Beehiiv and its subscribers live there. Issues go out through that platform to its members or subscribers instead of Postwright’s list, at the same point in the order (after the blog post is live), at most once per issue, and never to Postwright’s list for that brand. Beehiiv needs its Pro or Enterprise plan. Ghost needs its own email setup. |
| Kit or Mailchimp | Some setup | Optional, per brand (Settings > Brand > Newsletter), when the brand’s subscribers live in Kit or Mailchimp. Issues go out through that platform to all subscribers, a segment, or a tag (Kit), or to an audience or a saved segment (Mailchimp), after the blog post is live, at most once per issue. A test goes to you through the platform first, and nothing is sent until you approve it. You use your own API key. Postwright imports and syncs no subscribers, and its subscribe form, double opt-in and drip sequences still use Postwright’s own list. |
| Substack | Not supported | Not supported. Substack has no API that lets an app post or send. Postwright never posts to Substack. |
Subscribers
Signups use double opt-in with signed confirmation tokens, so only confirmed addresses receive mail. Postwright tracks engagement and tiers subscribers as active, casual, or dormant, and it handles preferences and unsubscribes with the required CAN-SPAM footer and one-click links on every send.
Drip sequences
Sequences are automated multi-step campaigns you author as plain Markdown files — one file per step, each with its own delay and optional branching (for example: if a step wasn’t opened, wait and resend; if a link was clicked, jump ahead). Subscribers enroll on signup, manually, or via the API, and a re-engagement sequence can pick up subscribers who go dormant.
Send safety
A newsletter that links to a fresh blog post is held until that post is confirmed live, so no one receives a link to a page that hasn’t deployed yet. You can also preview and send a test to yourself before the full broadcast.