Mato just raised pre-seed Read more

DocsContent

Newsletters

Draft an email newsletter from an episode, design it, and push it as an unsent draft to Klaviyo.

4 min read

A newsletter is an email draft Mato writes from one of your episodes. Mato never schedules or sends it: it creates the draft, and choosing the audience and pressing send stay with you, in your email tool. For the longer, SEO-focused version of this flow, see Write a researched article.

Where to find it

Click Content in the sidebar, under Create, to open the Content hub. It lists every newsletter and article across your shows, with filters for kind, status (All, Drafts, Pushed, Failed), and show. A newsletter's status badge reads Draft, Generating, Pushed, Edited since push, Pushing…, or Push failed.

Draft one from an episode

Click New content on the hub, pick a show, and leave the toggle on Newsletter. Each episode in the list shows one of:

  • Draft newsletter, for an episode with a transcript, script, or show notes to write from.
  • Open existing, if a newsletter already exists for this episode.
  • Needs transcript, if the episode has none of the sources above.

Mato writes the newsletter as one of the show's assigned hosts. If the show has no host assigned yet, drafting is blocked until you assign one in show settings.

You can also turn on automatic drafting for a show: in Content settings (see below), turn on Newsletters for this show and Mato drafts one every time an episode publishes. It still only creates a draft; nothing is sent automatically.

The newsletter editor

The editor has a Subject and Preview text field at the top, followed by the email body as a series of blocks: an episode card, key takeaways, pull quotes, and call-to-action buttons. Add block inserts any of these that are not already in the newsletter.

The top bar has Regenerate, Save, and Push draft, with a version number and a saved/unsaved indicator. Design opens template and styling controls: choose a template (Editorial, Episode Spotlight, Personal Note, or Plain), an accent color, and heading and body fonts, or reset any of them back to the show's brand defaults. Design changes apply the next time you save.

A live Preview panel shows the newsletter as it will render, with desktop and mobile width toggles. If you are mid-edit on a block, the preview shows the last valid version until you finish that block.

If someone else (or a regeneration) saves the newsletter while you are editing it, Mato shows a conflict dialog: Keep editing keeps everything you typed, or Load the newer version switches to the other save. Nothing is lost or silently overwritten either way.

Push the draft to your email tool

Click Push draft to send the newsletter to your connected email destination as an unsent draft. You choose an audience (a list or segment) before pushing; Mato records which one you picked but never reads who is in it and never sends the email itself.

If a draft was already pushed for this newsletter, the dialog switches to Update draft, which updates that same provider draft with your latest content and keeps its existing audience.

Every push is recorded in the newsletter's publication history, in order, with a link to open the draft at its destination. Nothing here indicates the email was ever sent; that step happens in your email tool.

Set up Klaviyo

Newsletters push to Klaviyo. Click Settings at the top of the Content hub to open Content settings, and connect it:

  1. Paste a private Klaviyo API key with campaign and template access, a connection name, and a from name and from address you have already verified in Klaviyo. Mato checks the key with Klaviyo before saving anything.
  2. Set a default audience: the list or segment a new draft is addressed to by default. You can still pick a different one on any individual draft before pushing.
  3. Optionally set a default author and default destination per show, and turn on Newsletters for this show to enable automatic drafting when an episode publishes.

To change your Klaviyo key, use Replace key rather than reconnecting; a key that fails validation leaves the old one in place. Disconnect removes the connection; drafts already pushed to Klaviyo stay there, but new drafts have nowhere to go until you connect again.

Support

Still need help?

If this doc didn't solve it, start a chat and ask us directly. Include the page you were reading and what you expected to happen.

Back to docs