Can an AI agent write and send your newsletter?

An AI agent can do most of a newsletter's weekly work: gather the links and notes, write the issue in your voice into a saved template, build the campaign for your subscribers, validate it and send you a test. Keep the final send with a person, or give the agent a key without campaigns:send. Keep the schedule, sender name and design fixed, so readers and mailbox providers see the same newsletter every week.
Unitpost ·
A newsletter is a loop: find what's worth sharing, write it up, send it on the same day, see what people read. A model is good at the first two and tireless at the rest. What it shouldn't decide alone is who gets the mail and when it goes.
What can an agent do for a newsletter?
- Collect: read your notes, the week's links, a changelog or an RSS feed you point it at.
- Write: draft the issue and three subject lines in your voice, from a style guide you give it.
- Lay out: fill a saved template, so the design and footer never change.
- Build: create a draft campaign for the subscriber segment, under a Newsletter topic.
- Check: validate the campaign and send you a test to read on your phone.
- Report: after a couple of days, summarize what people opened and clicked, and who bounced or unsubscribed.
What should stay with a person?
- The send. Read the test, then press send or approve the schedule. A key with
campaigns:writeand nocampaigns:sendmakes that a rule (approval before send). - Who's on the list. Only people who signed up. An agent must never add addresses it found or guessed (consent for AI marketing email).
- The facts. Check every claim, price and quote. A wrong number sent to ten thousand inboxes can't be taken back.
- The sender. Keep the From name and address fixed. Readers recognize them, and changing them looks like a different sender.
How do you set it up once?
- One marketing template with your layout and Brand Kit. The agent fills in the content and leaves the design alone.
- A Newsletter topic, so readers can leave the newsletter and keep the rest of your mail.
- A segment of subscribers, filled by your sign-up form or the API.
- A brief the agent reads every week: sources, tone, length, sections, words to avoid, and the day and time it goes out.
- A scoped key or connection that can write campaigns and send tests, but not send campaigns.
The product update walkthrough shows each step with the exact MCP tools.
What does one week look like?
- The agent gathers the week's material and drafts the issue into the template.
- It creates the draft campaign with the segment and topic, then runs
email_campaigns_validateto see who it will reach and whether anything blocks it. - It sends a test to you with
email_templates_test_send. - You read it, fix what's wrong (or ask the agent to), and send or schedule it.
- Two days later the agent reads
email_campaigns_statsand tells you what people clicked.
Does an AI-written newsletter hurt deliverability?
Mailbox providers don't judge who wrote an email; they judge how readers react. What hurts is what hurts any newsletter: an irregular schedule, sudden jumps in volume, a list nobody cleaned, and issues people stop opening. An agent helps with the schedule, since it never misses a week. The copy is where it can hurt: a generic issue is easy to ignore. Keep the frequency steady and the copy specific.
What does it cost to run?
Drafting, building and validating a campaign cost nothing; the sends are what's billed. Paid plans charge by emails sent rather than by subscribers kept, so an issue costs what it sends, and contacts you store but don't mail cost nothing. Newsletters on Unitpost compares the price of a weekly issue with the newsletter platforms.
