Skip to main content

Automated drafts

Automations create newsletter drafts on a schedule. Use them for recurring issues like a Monday roundup or Friday digest.

Written by Cagri Sarigoz

Automations create newsletter drafts on a schedule. Use them for recurring issues like a Monday roundup or Friday digest.

Automated drafts are saved to Issues. HeyNews does not send or publish them for you.

What automations do

Each automation can:

  • Pick eligible stories with Smart Select

  • Write the draft with the AI Writer you choose

  • Create a subject line and preview text

  • Save the finished draft to Issues

  • Notify you when the draft is ready or when something needs attention

Smart Select picks complete stories first. It only reaches for stories marked Summary only when there aren't enough complete ones to meet your Minimum stories, and it stops once the minimum is met. So a week when most of your sources sit behind a paywall still gets a draft, and that draft can be made entirely of Summary only stories. Your AI Writer mentions each one and links it, without writing more than the short description says. Read those drafts closely before you publish.

For an AI Writer created from an approved Newsletter Format, first select a ready Sending Connection. For beehiiv, connect draft publishing, choose its destination Publication, and select Use for new provider drafts. A ready Kit connection also meets this requirement. Where Kit drafts have been turned on, you can create an unsent Kit draft from the saved HeyNews Draft; otherwise copy Drafts into Kit yourself. The same check applies when editing an automation or choosing Create next draft now. Importing past issues alone does not complete this step.

Creating an automation

  1. Go to Automations in the sidebar.

  2. Click New Automation.

  3. Choose a ready AI Writer.

  4. Select one or more Issue Days. Use Weekdays for Monday through Friday, or choose any combination such as Tuesday and Thursday.

  5. Choose whether HeyNews should create each draft on the Issue Day or up to six days before it.

  6. Set the time, timezone, and a cadence from every week to every four weeks.

  7. Check the next five draft and Issue Day pairs in the preview.

  8. Set the minimum and maximum number of stories.

  9. Choose a date window. New automations start on Since last draft.

  10. Save the automation.

For schedules longer than one week, Starts anchors the cadence. For example, a two-week schedule that starts on Monday repeats from that week's selected Issue Days. The schedule continues until you pause or delete it.

HeyNews keeps the draft run and issue day separate. If you ask for a Friday issue one day early, the draft runs on Thursday but your AI Writer is told that the issue is for Friday. The calculation follows the timezone saved on the automation, including clock changes.

Story rules

Automations work best when your sources are bringing in fresh stories. You can control:

  • Minimum stories: the fewest stories needed before HeyNews writes the draft

  • Maximum stories: the most stories HeyNews should include

  • Date window: which stories are recent enough to use. You get the same choices as the date filter in Compose: Since last draft, Last 24 hours, Last 7 days, Last 14 days, Last 30 days, a custom number of minutes, hours, or days, or All available. Calendar dates are only available in Compose.

  • Allow previously used stories: when checked, HeyNews can pick stories that are already in a saved draft for this publication, including drafts your teammates saved. When unchecked, it skips them. Either way, HeyNews still follows the date window and its other story rules.

How Since last draft works

Since last draft picks from stories published after this AI Writer's most recent draft. Every draft counts, whether you wrote it in Compose or an automation created it. Until the AI Writer has a first draft, HeyNews looks at the last 7 days instead.

A draft you write yourself moves that starting point too. If you create one shortly before a scheduled run, the run only has the stories published since then. When that's fewer than your minimum, even after adding Summary only stories, the run fails and HeyNews tells you why. If runs keep failing, HeyNews pauses the automation. Choose a rolling window such as Last 7 days if you often write drafts by hand between runs.

Automations you set up earlier

Automations you created before these options existed pick stories the way they always did. An automation that looked back a set number of days keeps that window. If you'd checked Allow previously used stories, the automation now shows All available with the box unchecked. That matches what it did before: it ignored the date window but still skipped used stories. Check the box if you want it to reuse stories.

HeyNews picks from the eligible stories available when the automation runs. New automations do not lock drafts to one fixed source list. If there are not enough matching stories, the run fails and HeyNews tells you what needs attention instead of creating a weak draft.

Reviewing automated drafts

When an automation finishes, the draft appears in Issues with an Automated badge. New drafts also show a New badge.

Open the draft, review it, and edit anything you want. Copy it into any email platform when it is ready. If you connected beehiiv for draft publishing, save your changes and use Create draft in beehiiv when beehiiv is the selected, ready Sending Connection.

Create an unsent draft in beehiiv

An automation can also copy each new draft into beehiiv. Open the automation, check Also create an unsent draft in beehiiv, and save. The option uses your Publication's Sending Connection, so Editors can turn it on once an Owner or Admin has chosen a ready one.

  • Automations you already have stay off until someone turns this on.

  • If no Sending Connection is ready, the option is greyed out. Owners and Admins see a link to Connections. Editors see who can fix it.

  • HeyNews never sends or schedules the copy. It starts with that platform's default design and audience, and you decide who gets it and when. The Issue Day is your plan in HeyNews, not a send date.

  • HeyNews saves the draft first. If the copy has a problem, the draft is still in Issues, the automation keeps running, and the problem doesn't count toward pausing it.

  • Each run uses the Sending Connection that was selected when it started. If the connection is down later, the option stays on and copying picks up again once it's ready.

  • A copy doesn't use another draft from your plan.

  • Each copy shows the draft as it was when the run finished. Later edits in HeyNews don't change it. Use the update action on the draft to copy your latest edits.

  • Kit copies follow the same rollout as Create draft in Kit. Where Kit drafts have not been turned on yet, the option stays greyed out even though your Kit connection is ready; copy your finished Issue into Kit instead.

Scheduled runs and Create next draft now both follow this setting. Open Recent runs to see each copy's status, a link to the draft in beehiiv, or a link to the HeyNews draft when the copy needs a look. The draft itself shows the same status and the same explanation.

Some older automations set up by HeyNews keep a fixed source list and save drafts in HeyNews only. Editing, pausing, or resuming them keeps that source list. They cannot create provider drafts.

When a copy needs attention

HeyNews always saves your draft first, so a problem with the copy never costs you the draft.

  • If beehiiv is down for a moment, HeyNews keeps trying for up to 30 minutes from when the run started. After that it stops, and the draft shows Try again.

  • If beehiiv stopped answering partway through, HeyNews can't tell whether the copy exists, so it won't try again on its own. Check your drafts in beehiiv, then open the HeyNews draft and choose It's in beehiiv or It's not in beehiiv. The second one lets you try once more.

  • If the copy couldn't be verified, open it in the provider and review it. Then open the saved HeyNews Draft and choose I reviewed it, create a new beehiiv draft (or Kit draft). Editors, Admins, and Owners can do this. HeyNews creates a new unsent draft beside the reviewed one and shows links to both. The reviewed draft stays unchanged; delete it in the provider if you no longer need it. Recent runs links to the HeyNews Draft for this action and shows the same explanation.

  • If the connection was removed, expired, or lost access, a Publication Owner or Admin can reconnect it in Connections. The automation stays on and starts copying again once the connection is ready.

  • Retries always go to the connection the run started with. If you've since selected a different Sending Connection and the copy failed without creating anything, the draft also offers Create draft in beehiiv for it.

Notifications

HeyNews can notify you by email and in the in-app notification inbox when:

  • An automated draft is ready

  • An automation needs more stories or a settings change

When an automation also creates a draft in beehiiv, HeyNews waits until that copy is done and sends one message. The in-app notification says whether the beehiiv draft is ready. Draft-ready emails can also include the copy's status and a link to open it in beehiiv when that link is available. When the copy needs attention, check the email or in-app notification for the next step. Your HeyNews draft is still safe in Issues.

A copy that needs attention also goes to the Publication's Owners and Admins, since they can fix a connection. If one connection problem affects several runs, they get one message about it. They're told again only if the problem comes back after a copy has worked. Anyone on the Publication can see a draft's copy status on the draft. Recent runs belongs to the automation, and only the person who created that automation can see it.

You can turn automated draft emails on or off from Account settings > Notifications. In-app notifications still appear so you can see what happened later.

Pausing or editing an automation

From the Automations page, you can pause, resume, edit, create the next draft now, or delete an automation. Create next draft now creates a draft for the next configured Issue Day without moving future dates.

Pause an automation when you want to keep the setup but stop scheduled runs for a while. Delete it when you no longer need that schedule.

HeyNews does not create missed Issue Days later. If a temporary service problem interrupts a draft that started on time, HeyNews retries every five minutes for up to 30 minutes. Only one draft can be active for an automation at a time. Pausing or deleting the automation cancels an unfinished retry.

If the automation also creates drafts in beehiiv, pausing it, deleting it, or turning that option off stops a copy that hasn't started yet. Recent runs shows the copy as cancelled, and you can still create one from the draft. A copy that has already started finishes normally. Drafts already in beehiiv stay there, because HeyNews never deletes them.

Did this answer your question?