When should you use it?
- You publish on a site your agent already manages
- Your newsletter lags because writing it is a chore
- Your email platform has an API for broadcasts
Not for: Sending without reviewing the draft; Platforms whose API cannot create campaigns
What do you need, and what do you get?
You need
- Email platform API key
- The new post's content
- Your newsletter format
You get
- A draft broadcast in the email platform
- A summary written from the post
How does it work, step by step?
- Map the API firstList which actions the platform allows, so you know what can be automated.
- Store the key safelyPut it in an environment file the repo ignores.
- Write the skillOn publish, summarize the post in your format and create a draft broadcast.
- Review in the platformRead and edit the draft before scheduling it yourself.
- Do the rest by handForms and sequences the API cannot create still need the dashboard.
The prompt
Our own prompt, inspired by Sid Bharath and written to work in Claude Code. Values in lime are placeholders.
After each new article goes live, read it and write a newsletter version: subject line, a two-paragraph summary in my voice, three key takeaways and a link to the post. Use the email platform API key from .env. Create the issue as a draft broadcast only; never schedule or send. Reply with the draft ID and the subject line. If the API returns an error, stop and show it to me.
Inspired by Sid Bharath: How To Automate Your Email Newsletter With Claude Code. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Not everything is scriptable; in Kit, forms and automations were dashboard-only.
- An auto-summary can overstate a post; check claims before sending.
Our take
Sid Bharath's first step is the most transferable lesson: before planning an automation on any platform, find out what its API can actually do. He wanted forms, sequences and broadcasts created automatically, discovered only some of that was possible, and designed around the gap instead of building a plan that would stall. Ask your agent to read the API documentation and produce that inventory up front. Saving each newsletter as a draft rather than sending it keeps you in control of what subscribers receive, which matters because an email cannot be unsent and a summary can miss the point of a post. Read the draft in Kit's own preview, where formatting and links appear as readers will see them. Store the API key in an environment variable or secrets manager, not inside the skill file, especially if the blog repository is public. If you publish less often than weekly, consider batching posts into one digest draft so subscribers are not emailed for every small update. Handle the unsupported pieces, like forms, by hand.
Where the time goes back: The newsletter step happens as part of publishing instead of being a separate weekly task.
FAQ
Why check the API first?
Will it send automatically?
Source and credit
Inspired by Sid Bharath. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- How To Automate Your Email Newsletter With Claude Code
- Creator
- Sid Bharath
- Published on
- sidbharath.com
- Original date
- Mar 4, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Claude Code
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 23, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.