Skip to content

Email campaign drafts with pre-send checks and a count matched yes

Builds an email campaign as a draft in your email platform and runs automatic checks on links, tracking tags, fallbacks and the unsubscribe footer. It can only send or schedule when you type a phrase that includes the live recipient count.

MarketingWorks with Claude Code · Claude Desktop with MCP+1Community example

What it does

  • Writes the campaign and creates it as a draft
  • Checks subject, preview, links, tracking tags and merge tag fallbacks
  • Checks the unsubscribe link, mailing address, from address and image alt text
  • Blocks the campaign on any failed check
  • Shows the recipient count and the exact phrase needed to send

Your approval boundaries

Approval required

These actions always wait for your yes:

  • Sending or scheduling the campaign
  • Choosing the audience

You decide what happens next.

More about this workflow

This setup is for marketers and solo creators who need steady output without losing their voice. It takes a repeat chore off your plate and hands back something you can check quickly.

First, it writes the campaign and creates it as a draft. Next, it checks subject, preview, links, tracking tags and merge tag fallbacks. Then it checks the unsubscribe link, mailing address, from address and image alt text. After that, it blocks the campaign on any failed check. Finally, it shows the recipient count and the exact phrase needed to send. It works with your email platform and docs, each on its own login with limited access.

You get the prep work done and waiting for you. The agent stops and asks for your yes before sending or scheduling the campaign and choosing the audience, and says plainly if a step cannot be undone.

“never sends without an explicit, specific yes.”
brittanyslay brittanyslay on GitHub · Nov 5, 2026
Before you startEmail platform · Docs accessScoped permissionsClaude Code or Claude Desktop with MCP
Explore required tools and model recommendations

Tools and access

  • Email platform

    Handles the email platform part of this job. Grant draft access, no send or list export.

    API required: Optional. Your newsletter tool. An API helps, but the agent can also hand you a draft to paste.

    No sign-up needed
  • Google Docs

    Handles the docs part of this job. Grant one folder, create and edit only.

    API required: Yes. Needs a Google Cloud OAuth app with the Docs API turned on.

Official links only. Not sponsored, no affiliate links.

Model recommendations

Best pick

GPT-6.1 Sol

Strong general writer at a mid price.

$2 per million input tokens, $10 per million output tokens, for prompts up to 272K tokens. Longer prompts cost $4 in and $15 out.

OpenAI docs as of October 11, 2026

Cheaper backup

GPT-6 Luna

Very low cost for first drafts and digests.

$0.10 per million input tokens, $0.50 per million output tokens, for prompts up to 272K tokens.

OpenAI docs as of October 11, 2026

Our own picks. Not sponsored, no affiliate links.

Build your prompt

Add your details, then copy the prompt into your tool.

1Your details

Fill these in and the prompt updates as you type.

e.g. utm source and medium

2Your prompt

4 of 4 still empty
Fill these in before you run it: [EMAIL PLATFORM] [AUDIENCE OR SEGMENT] [CAMPAIGN BRIEF] [TRACKING TAG RULES: e.g. utm source and medium] You are the Email campaign drafts with pre-send checks and a count matched yes agent. Builds an email campaign as a draft in your email platform and runs automatic checks on links, tracking tags, fallbacks and the unsubscribe footer. It can only send or schedule when you type a phrase that includes the live recipient count. Use only the details filled in above. If any [BRACKETED] item is still blank or unclear, stop and ask for it first. Do not guess. What you do on your own: - Writes the campaign and creates it as a draft - Checks subject, preview, links, tracking tags and merge tag fallbacks - Checks the unsubscribe link, mailing address, from address and image alt text - Blocks the campaign on any failed check - Shows the recipient count and the exact phrase needed to send What you must never do without a yes from a person: - Sending or scheduling the campaign - Choosing the audience Rules: - Before any step on the list above, stop and ask. Say in plain words what you want to do, who it affects, and whether it can be undone. - If something cannot be undone, say so first, in one short line. - Write drafts, not final actions. A person sends, pays, posts, or deletes. - Keep a short log of every action you took and every source you read. - If you are unsure, ask instead of guessing.
View run instructionsPaste into: Claude Code, Claude Desktop with MCP, Cursor

Your answers stay in this browser only.

Run your workflow

Connect your tools with only the access this setup needs, then follow these steps.

Steps

Do these in order. Test on old data before it touches live work.

  1. 1Set up Email platform. Keep it to draft access, no send or list export.
  2. 2Connect Google Docs with its own login, not yours. Grant one folder, create and edit only.
  3. 3Paste the prompt where your harness takes instructions. See the note under the Copy button.
  4. 4Do a dry run on old or test data first. Check every draft and every stop point by hand before you let it near live work.
  5. 5Read its log after the first real run. Only widen access once a week of runs looks clean.

Safeguards and trust score

The score describes this example setup’s access, approval boundaries, ability to undo changes, and scope.

Access18 / 30

Can draft things that send or spend, so it sits close to risky actions.

Human approval30 / 30

Waits for a yes on: sending or scheduling the campaign, choosing the audience.

Undo and logs14 / 20

Proposes changes to live records, so the setup needs a change log and a way back.

Scope18 / 20

Runs on its own login across 2 tools. Fewer connections means a smaller blast radius.

How to raise it

  • Access: Take away its ability to send, post or spend. Let it only write drafts, and have a person press send or pay from their own account +6
  • Undo and logs: Stop it from editing live records. Have it write the change as a proposal you apply, and keep a log of every change with a way to roll it back +3
  • Scope: Run it on one tool only, with its own login that can see just what this job needs +2

Do all of these to reach 91, up from 80.

Want help getting there? Get an AI Trust Audit from Pixeldesigns

Reviewed by Trustcase (example setup). How scoring works

Embed badge

Show this trust score on your site or README. It links back here.

Trustcase trust score badge
Markdown
[![Trustcase trust score for Email campaign drafts with pre-send checks and a count matched yes](https://trustcase.dev/badge/email-campaign-drafts-with-pre-send-checks-and-a-count-matched-yes.svg)](https://trustcase.dev/use-cases/email-campaign-drafts-with-pre-send-checks-and-a-count-matched-yes)
HTML
<a href="https://trustcase.dev/use-cases/email-campaign-drafts-with-pre-send-checks-and-a-count-matched-yes"><img src="https://trustcase.dev/badge/email-campaign-drafts-with-pre-send-checks-and-a-count-matched-yes.svg" alt="Trustcase trust score for Email campaign drafts with pre-send checks and a count matched yes" height="20"></a>

Other workflows that use the same tools