Newsletter Issue AI workflow template: One theme, one issue, sent right.

The ConvOps Newsletter Issue template makes your AI build one issue: decide the theme, audience and lead story, curate three to six items that serve it, write the issue with subject line and preview text, then run a pre-send check. Sending to a list is irreversible, so it waits for your approval.

5 steps · 1 approval · 1 loop back

Newsletter Issue · example runyour AI client
  1. 01Theme
  2. 02Curate
  3. 03Draft
  4. 04Send Reviewwaits for approval
  5. 05Completeclosing note
task created · workflow attached

example · the steps are this template's real steps

in short

What does the Newsletter Issue template do?

For marketers and founders who send a weekly or monthly newsletter and want each issue to read as one story, not a link dump.

Newsletter Issue is stored in ConvOps as five steps, and your AI client receives them one at a time. A Newsletter Issue run holds at Send Review until an explicit approval is given.

  • Build a weekly issue around a single theme with curated links
  • Turn a launch into a newsletter that leads with the announcement
  • Assemble a roundup from a list of saved articles into a clean draft
step by step

How does the Newsletter Issue workflow run?

The 5 Newsletter Issue steps in order, each with the instruction your AI receives there as Newsletter Issue stores it.

Theme
Curate
Draft
Send Reviewapproval
Completeclosing note

One newsletter issue built around a theme and a lead story, with three to six curated items, a subject line, preview text and a passed pre-send check.

  1. 01

    Theme

    the agent works

    Decide what this issue is about before gathering anything.

    Capture, in plain prose:

    • Theme: the single through-line tying the issue together
    • Audience: who receives it and what they expect from you
    • Lead story: the one item that anchors the issue
    • Goal: the open, the click, or the reply you want
    • Working subject line: a first attempt, to be refined later

    If there is no clear theme, ask the operator: a themeless issue reads as noise.

    Save the theme, audience, lead story, goal, and working subject line as a task note with task_notes_add. The next step (Curate) reads it.

  2. 02

    Curate

    the agent works

    Read the task notes with task_notes_list: the note from the Theme step contains theme, audience, lead story, and goal. Work from it.

    Curate the items. What good looks like:

    • 3 to 6 items, each clearly serving the theme: cut anything that only loosely fits
    • The lead story placed first
    • For each item: a title, the link, and one line on why it matters to this audience
    • A logical order so the issue reads as a sequence, not a dump

    Save the ordered, annotated item list as a task note with task_notes_add. The Draft step reads this note.

  3. 03

    Draft

    the agent works

    Read the task notes with task_notes_list: the note from the Curate step contains the ordered item list, and the Theme note holds the audience and goal. Work from them.

    Write the full issue:

    • A short intro that states the theme and earns the scroll
    • Each curated item written up in the issue's voice with its link
    • A clear closing and CTA matching the goal
    • A refined subject line and preview text that fit the theme

    Save the full issue draft, subject line, and preview text as a task note with task_notes_add. If the draft exceeds 10,000 characters, split it across notes or store it where the operator keeps documents and record the location. The Send Review step reads this note.

  4. 04

    Send Review

    waits for your approval

    Read the task notes with task_notes_list: the note from the Draft step contains the full issue, subject line, and preview. Work from it.

    Do the pre-send check:

    • Every link works and points where it should
    • Subject line and preview text are final and compelling
    • The issue delivers on the theme and the goal
    • No placeholder text, broken formatting, or unfinished item

    Ask the operator to approve the issue for sending. This is a checkpoint: sending to the list is irreversible, so the AI cannot advance until you approve. If you reject, the workflow returns to Draft.

    rejected → back to Draft

  5. 05

    Complete

    closes with a note

    The issue is approved and ready to send. Confirm the final issue, subject line, and preview text are saved as a task note, then close out the task.

reach for it when

  • You send to a list on a regular rhythm.
  • Each issue should read as one story, not a list of links.
  • A broken link or a leftover placeholder in a sent email is unacceptable.

something else fits when

  • It is a one-off announcement: Social Post or Blog Post.
  • The email is transactional and triggered by a product event.
  • There is no theme this cycle, so skipping the issue beats filling it.
example · professional associationenterprise

The monthly members' briefing

The issue leads with a new regulation and curates four items for practitioners. The pre-send check finds one broken link before the editor approves.

Send Review approval

where approval is required

Where do you approve in Newsletter Issue?

Newsletter Issue holds at Send Review until an explicit approval is given, recorded with the account that gave it.

step 4

Send Review

Sending to the list is irreversible. The AI checks links, subject line, preview text and placeholders, then you approve or send it back to Draft.

what you review

  • Every link works and points where it should
  • Subject line and preview text are final and compelling
  • The issue delivers on the theme and the goal
  • No placeholder text, broken formatting, or unfinished item

reject → back to Draft

gates the engine checks without you

  • Complete closes Newsletter Issue only when your AI leaves a closing note, saved on the task.
what you need

What do you need to run Newsletter Issue?

make it yours

How do you customize Newsletter Issue?

Once installed, Newsletter Issue is a workflow in your workspace. Ask your AI to change Newsletter Issue in plain words; the edit lands on the one step that needs it.

ChatGPTexample

new chat

In Curate, always include one item from our own blog.
workflow_step_update · Newsletter Issue
Done. Newsletter Issue in your workspace now has the change, and every new run follows it.

more example prompts

  • "In Curate, always include one item from our own blog."
  • "Add a step that writes two subject-line options for an A/B test."
  • "Schedule a new issue every first Monday of the month."
the difference

Newsletter Issue: without a workflow vs with it

  • The issue becomes a pile of unrelated links with no through-line and a subject nobody opens
  • The send button gets hit before anyone checks the links, the subject, or the preview text
  • You assemble half the issue, get pulled away, and lose track of which items were already in
  • A week later nobody remembers which items made the issue or why the others were cut
  • The Newsletter Issue process lives in a prompt, and each run follows it a little differently
  • The AI drives from a single Theme so every item earns its place and the subject line lands
  • The AI pauses at a send-review checkpoint so you confirm everything before it reaches the list
  • The AI saves the theme, the curated items, and the draft as notes, so a later session resumes mid-issue with nothing lost
  • Every step (Theme, Curate, Draft, Send Review) is logged, so the issue's full history is already there
  • Your AI receives the 5 stored steps one at a time, and the run holds at Send Review until an explicit approval is given
questions

Newsletter Issue template FAQ

What is the ConvOps Newsletter Issue template?

The ConvOps Newsletter Issue template makes your AI build one issue: decide the theme, audience and lead story, curate three to six items that serve it, write the issue with subject line and preview text, then run a pre-send check. Sending to a list is irreversible, so it waits for your approval.

How many items go in an issue?

The ConvOps Curate step picks three to six items, each clearly serving the theme, and cuts anything that only loosely fits. The lead story goes first, and each item gets a title, its link and one line on why it matters to this audience, in an order that reads as a sequence rather than a dump.

What does the pre-send check cover?

The ConvOps Send Review step checks every link works and points where it should, the subject line and preview text are final, the issue delivers on the theme and the goal, and nothing is left as placeholder text, broken formatting or an unfinished item. Sending to the list is irreversible, so the run holds there until an explicit approval is given.

Does it send the newsletter?

No. The ConvOps Newsletter Issue workflow ends with an approved issue, subject line and preview text saved as a task note. You or your AI client send it from your email tool. If you reject the issue at Send Review, the run returns to Draft, so only an approved version reaches the Complete step.

Where does the subject line come from?

In ConvOps, the Theme step records a working subject line next to the theme, the audience, the lead story and the goal. The Draft step refines it, writing the final subject line and preview text to fit the theme alongside the full issue, and Send Review confirms both are final before the issue can be approved for sending.