The 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.
It is a stored workflow, not a prompt. Your AI client receives one step at a time from ConvOps over MCP, does the work, and advances. The engine holds the run at the approval until a person says yes.
5 steps, in this order. Below each one is the instruction your AI receives at that step, exactly as the template stores it.
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.
One step waits for a person. You answer in the chat; the engine records the verdict and the audit row records who 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
Read from the template's own steps: the tools they call, the files they write, and whether they touch code.
Connect your AI client first, then install Newsletter Issue from the catalog in the ConvOps app. See how to connect a client
An installed template is a workflow in your workspace. Ask your AI to change it in plain words; the edit lands on the one step that needs it.
new chat
more example prompts
Three to six, each clearly serving the theme, with the lead story first and one line on why each matters to this audience.
Every link works, subject line and preview text are final, the issue delivers on the theme and goal, and there is no placeholder text or broken formatting.
No. It 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.
Any MCP client connected to ConvOps. Verified clients: Claude Code, Claude (desktop, web, Cowork), OpenAI Codex, ChatGPT, Cursor, OpenCode. It needs no repository, so a plain chat client works.