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
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
example · the steps are this template's real steps
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.
The 5 Newsletter Issue steps in order, each with the instruction your AI receives there as Newsletter Issue stores it.
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.
Decide what this issue is about before gathering anything.
Capture, in plain prose:
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.
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:
Save the ordered, annotated item list as a task note with task_notes_add. The Draft step reads this note.
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:
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.
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:
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
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.
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
Newsletter Issue holds at Send Review until an explicit approval is given, recorded with the account that gave it.
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
reject → back to Draft
gates the engine checks without you
Newsletter Issue runs in a ConvOps workspace and attaches to the task type, so new work of that type starts on it. Newsletter Issue saves each step's output as a task note in ConvOps, and the next Newsletter Issue step reads it back. Newsletter Issue needs no repository, so a chat client such as ChatGPT or Claude can run it. Connect a client , then install Newsletter Issue from the catalog .
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.
new chat
workflow_step_update · Newsletter Issuemore example prompts
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.
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.
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.
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.
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.