AI CEO LabAutomated Newsletter: The Tag That Sends It Without Me
One tag starts it. Wait steps pace it. Every keyword funnel feeds it. The Health & Wealth note I send is one thing from medicine and one thing from business, only things I actually did, written like a person and inked so it lands out of the Promotions tab. Here is the shape.
Every doctor I know who tried a newsletter quit inside two months. Not because they had nothing to say. Because the newsletter was a chore bolted onto a busy week, with no system feeding it readers and no shape telling them what to write.
Mine is called Health & Wealth. One thing from medicine, one thing from business, every week, and the rule that keeps it honest: only things I actually did. No summaries of other people's ideas. If I did not run the test, it does not go in the note.
The part nobody talks about is that a newsletter is not an email. It is a workflow. A tag starts it. Wait steps pace it. Every keyword funnel I build ends by adding that tag, so the list grows while I post reels. I never import a list, never export a CSV, never remember to send.
This guide is the workflow, the shape of one issue, the voice rules I hold myself to, and the primary inbox method with the evidence I actually have for it, including what that evidence does not prove. The keyword funnels that feed it are in Comment To DM To Email In One Afternoon. How an issue gets written from a five minute voice note is in Turn A Voice Note Into A Newsletter Issue. This one is the machine the issue drops into.
The three levels
A broadcast to an imported list when you remember, from a template with a header image, landing in Promotions.
One tag triggers the sequence. Issues sit behind wait steps. Every lead magnet ends by adding the tag. Each issue is short, one idea, a reply ask, inked for the inbox.
An agent drafts next week's issue from your notes and the last thing you shipped, in your voice, and holds it for a yes. Opens, replies and unsubscribes per issue land in one weekly line. You write for one hour a week and the rest is the workflow.
The mental model
A newsletter is a broadcast you write on Sunday night to a list you exported from somewhere.
A newsletter is a workflow one tag starts. Lead magnets feed the tag. Wait steps set the cadence. You only write the words.
| Role | Talks to you | Job |
|---|---|---|
| The tag | Trigger | One tag, added by every lead magnet's last step. Nothing else starts the sequence. |
| The wait step | Cadence | The gap between issues lives in the workflow, not in your memory. |
| The issue | Weekly | One thing from medicine, one from business, only things you did, one reply ask. |
| The ink | Before send | A hidden honest passage that moves the email out of Promotions. Not a fix for a bad sender. |
Build it once
1. One tag starts everything
Create the tag before the workflow. Mine is health-wealth. Then a second one the workflow adds on entry, newsletter-subscriber, so you can always count who is actually in. The trigger is tag added, and nothing else. Not a form. Not a purchase. Any funnel that wants to feed the newsletter adds the tag as its last step, a day after it delivered its own resource.
2. The onramp workflow
Trigger: tag added. Step one: add newsletter-subscriber. Step two: send Issue 01. Then a wait step, then Issue 02, and so on. New subscribers walk through the issues in order at the pace the wait steps set. This is the difference between a newsletter and a broadcast: a reader who arrives in March gets the same first issue as one who arrived in January, because the first issue is the one that earns the second.
3. The shape of one issue
Preheader that says what this issue is, in one line. First name. One line that says what the note is and how often it comes. Then the one idea, with a name so they can repeat it. A simple example with a number only if it is a real number. A short list they can run this week. One question at the end that I actually want a reply to. A line at the bottom saying why they got this and how to stop. Under 400 words. The idea comes from the hook, value, ask, PS format I learned from Alex Hormozi's weekly emails; the version I send has the PS folded into the reply question.
4. The voice rules
Paragraphs of one to three sentences with a blank line between them, and the spacing set explicitly in the email so it does not render as one block. No header image. No stock photo. One button at most, usually none. Plain words. The painful truth named once. No em dashes. Read it aloud on a phone before it goes into the workflow. If it sounds like an agency, rewrite it until it sounds like a message to one person.
5. The primary inbox pass
Gmail sorts on more than the visible words. Ghost Ink appends one hidden passage of honest, first person prose on the same subject as the email, below the footer, and records it so a resend is byte identical. In my seed test, the same email with no passage landed in Promotions twenty out of twenty times and with the passage zero out of forty. That is enough to choose a configuration. It is not a Primary guarantee, not an effect size, and it does nothing for a burned domain or a bought list. The passage may not contain a pitch, a link, a product name, a claim or a number. Anything you would mind the reader seeing is abuse, and the gate rejects it.
6. Platform settings that decide whether the ink helps or hurts
On GoHighLevel the passage runs long, around twelve hundred to thirty five hundred words, and it needs a seed of your own long form writing or it pads. GoHighLevel sends no plain text part, so the passage stays hidden. On a platform that builds a plain text version by flattening the HTML, every hidden word becomes visible text, so the passage must be short, under about three hundred and forty words, and the preheader is left alone. Wrong platform setting is worse than no ink. Verify one real send by viewing the raw source before any bulk run.
Starter prompts
Paste these as written. They are short on purpose, because the long ones drift.
Act as my newsletter editor. The note is called [NAME]. Its promise: [one thing from X, one thing from Y, every week, only things I actually did]. Here are my notes from this week: [paste]. Write one issue under 400 words in this shape: a preheader under 90 characters that says what the issue is; first name greeting; one line reminding them what this note is; one idea with a name they can repeat; a simple example using only numbers from my notes, or [X] if none; a short list of what to run this week; one question at the end that I want a reply to; one closing line saying why they received this and how to stop. Paragraphs of one to three sentences with a blank line between them. Plain words, no hype, no em dashes, no header image, at most one button. Flag any sentence that claims something my notes do not say I did.
Read this issue as a burned out doctor on her phone between patients. Mark every sentence that sounds like an agency, a summary of someone else's idea, or a claim without a real number. Rewrite only those sentences. Do not add anything.
Here are the last [N] issues with opens, replies and unsubscribes for each: [paste]. Tell me which reply question got answered, which subject line got opened, and one change for next week. One paragraph. No new ideas for issues.
Draft in a chat, send from the workflow
Layer 1 is writing the issue in a chat window from your notes, with the prompt below. Layer 2 is the workflow and the sending settings that make it run without you. These are the ones that must be set.
Trigger is tag added, and only that
A form trigger or a purchase trigger doubles people up. Every entry point adds the tag instead.
Wait steps in days, between every issue
Set the gap in the workflow. If you change cadence, you change one number, not a calendar.
Explicit paragraph spacing in the email HTML
The first version of Issue 01 relied on default paragraph margins and read as a block. Set the margins.
A preheader on every issue
Under ninety characters, says what this issue is. On GoHighLevel the ink pass blanks it deliberately; on other platforms it stays.
Ink after the copy is final, with a stable key
One key per issue, reused on every edit and resend. A key built from the subject breaks the moment you edit the subject.
Sender identity is yours
Your name, your domain, your reply address, and you actually read the replies.
Give it to your agent, three ways
Same skill, three worlds. Pick the one you actually use. The skill file at the bottom of this page is the instructions in every case.
An agent with connectors (Claude Desktop, Claude Code, Grok Bot)
Drafting is the agent's job; sending is the workflow's. Give Claude the skill and your notes and it returns the issue in the shape. The ink pass runs as a local command on stock Node with your API key in the environment, and it never touches your sending platform.
- Save the skill file as a project instruction in Claude or a skill in Claude Code. Paste the first prompt with your notes from the week.
- Take the subject, preheader and body it returns into the email step of the onramp workflow. Set explicit paragraph spacing.
- Export the email HTML from the platform, run the ink command below for your platform, upload the inked HTML back.
- Send one real copy to a seed inbox. View the raw source. Then let the workflow send.
export ANTHROPIC_API_KEY=... # the passage is written by a model # GoHighLevel: long passage, seeded with your own long form writing node ghost-ink.mjs ink --html issue-02.html --subject "The AI ROI Test" --platform ghl \ --key "ghl:workflow:ONRAMP:issue-02" --bio-file bio.txt --seed-file past-newsletter.txt --out issue-02.inked.html # Check a delivered copy still carries what was recorded node ghost-ink.mjs verify --html sent.html --key "ghl:workflow:ONRAMP:issue-02"
ChatGPT (a project or a custom GPT)
ChatGPT has no connector to a CRM and cannot run the ink pass. Use a Project for the drafting and do the workflow and the ink by hand.
- Create a Project with the skill file as its instructions. Paste your notes and the first prompt each week.
- Ask it for the subject, preheader, and body in plain text with blank lines between paragraphs. Paste into the email step and set the spacing yourself.
- For the inbox pass, run the ink command from the connectors block in your own terminal, or skip it and rely on sender reputation and a short, plain email.
- Paste last week's opens, replies and unsubscribes back and ask what to change in the reply question.
Anything with an API (a token and a curl call)
If an agent builds the workflow for you, the CRM's workflow endpoints can create the onramp, chain the tag step, the email steps and the wait steps, attach the tag trigger and publish. Tags must be created first. Keys in environment variables, mutation behind a flag.
- Create the two tags through the tags endpoint before anything references them.
- Create the workflow, save the step graph in order: add tag, email, wait, email, wait.
- Attach a contact tag trigger for the newsletter tag, then publish.
- Keep every issue's HTML in a file per issue, keyed the same way the ink record is keyed, so a resend reproduces the same email.
export GHL_API_KEY=... export GHL_LOCATION_ID=... # tags first, then workflow, then trigger, then publish; refuses to mutate without the flag ALLOW_MUTATE=1 node build-onramp.mjs --tag health-wealth --issues issues/*.html --wait-days 7
Failure modes
Every one of these has happened to me or to someone I set this up for.
| Failure | Fix |
|---|---|
| Nobody new receives the first issue | The lead magnet's last step never adds the newsletter tag, or the trigger is not tag added |
| The issue renders as one block on a phone | Explicit paragraph margins in the email HTML, not default spacing |
| Every issue lands in Promotions | Ink it, on the right platform setting, and fix the sender before blaming the copy |
| Three thousand hidden words showed up as visible text | Wrong platform. Short band and no preheader change anywhere that builds a plain text part |
| A resend rolled a new passage | Same key on every edit and resend of the same issue |
| You skipped a week, then two | Wait steps, a writing hour on the calendar, and an agent draft you only edit |
| The issue is a summary of a podcast you liked | Only things you did. Run the test first, then write it |
The tools I use for this
| Tool | What it is for here | |
|---|---|---|
| GoHighLevel | The workflow: tag trigger, email steps, wait steps. Where the newsletter actually lives. | Get it |
| Ghost Ink | My hidden passage tool for the primary inbox pass. Local, no dependencies, never touches the sending platform. | no link, just use it |
| Claude | Drafts the issue in the shape from my notes and writes the ink passage. | Open |
| Wispr Flow | How the notes get written. I talk the week out, it types. | Get it |
The free skill
It holds the workflow shape, the issue template, the voice rules and the checks before send. Give it your notes from the week and it drafts the issue in the shape, flags anything that is not something you actually did, and returns the subject, preheader and body ready for the email step. It never sends.
--- name: newsletter-runs-itself description: Drafts one issue of a weekly newsletter in a fixed shape from the owner's notes, and holds the workflow rules that make the newsletter run without them: one tag as the trigger, wait steps as the cadence, every lead magnet feeding the tag, and an honest hidden passage pass for inbox placement. Never sends. Trigger on "draft this week's issue", "write my newsletter", "build the newsletter onramp", "why is my newsletter in promotions". --- # The Newsletter That Runs Itself A newsletter is a workflow, not a broadcast. One tag starts it. Wait steps pace it. Every lead magnet ends by adding the tag. The owner only writes the words, and you draft them first. You draft. You never send. You never invent a number, a result or a story the owner's notes do not contain. ## The workflow (build once) 1. Tags first: the newsletter tag (the trigger) and a subscriber tag (added on entry). Tags must exist before a workflow references them. 2. Trigger: tag added, the newsletter tag. Nothing else starts the sequence. 3. Steps: add subscriber tag, send Issue 01, wait N days, send Issue 02, wait, and so on. New readers walk through the issues in order. The first issue earns the second. 4. Every lead magnet's workflow ends by adding the newsletter tag, one day after it delivered its own resource, so two emails never land in the same minute. ## The shape of one issue Under 400 words. In this order: - Preheader under 90 characters that says what this issue is. - First name greeting. - One line reminding them what the note is and how often it comes. - One idea, with a name they can repeat. - A simple example. Numbers only from the owner's notes; otherwise `[X]`. - A short list of what to run this week. - One question at the end the owner actually wants a reply to. - One line saying why they received this and how to stop. The idea of hook, value, ask and a tease comes from Alex Hormozi's weekly email format. Here the tease is folded into the reply question. ## Voice rules - Paragraphs of one to three sentences with a blank line between them. Explicit paragraph spacing in the HTML; default margins render as a block. - Plain words. Name the painful truth once. No hype, no stat dumps, no em dashes. - No header image, no stock photo, at most one button. - Only things the owner actually did. Flag any sentence that claims otherwise. - Written to one person reading on a phone. ## The inbox pass (Ghost Ink) One hidden passage of honest, first person prose on the same subject, below the footer, recorded under a stable key so a resend is byte identical. - Evidence the owner holds: same email, no passage, Promotions 20 of 20; with passage, Promotions 0 of 40. Enough to choose a configuration. Not a Primary guarantee, not an effect size, not a fix for a burned domain or a bought list. - The passage may not contain a pitch, a link, a product name, a call to action, a claim or a number. Anything the reader should not see is abuse and the gate rejects it. - GoHighLevel: long passage (about 1,200 to 3,500 words), seeded with the owner's own long form writing, preheader blanked by the tool. GoHighLevel sends no plain text part. - Any platform that flattens HTML into a plain text part: short passage (about 270 to 340 words), preheader untouched. Unknown platform gets the short band. - One key per issue, reused on every edit and resend. Never derive the key from the subject line. - Verify one real send by viewing the raw source before any bulk send. ## Before it goes into the workflow - Read aloud on a phone. If it sounds like an agency, rewrite. - Subject, preheader and body ready to paste into the email step. - Sender is the owner: their name, their domain, a reply address they read. ## Weekly line Subscribers, opens, replies, unsubscribes, per issue. Change the reply question if nobody answers it. Never miss a week.
What done looks like at thirty days
- The onramp runs from one tag and at least one lead magnet feeds it
- Four issues sent, none missed, each under 400 words with one reply question
- Every issue was inked on the right platform setting and one real send was verified by raw source
- Subscriber count, opens, replies and unsubscribes are written down weekly
- You answered every reply yourself
- You have not exported or imported a list in a month
Want your newsletter built and fed by your own keyword funnels?
Inside the AI CEO Lab we build the onramp on your CRM, wire your first lead magnet into it, and write the first three issues with you.