Beehiiv New Subscriber Agent with Codex
Look the subscriber up, read the UTM values and the referring site, apply tags, write two or three custom fields, and usually say nothing. That is API-shaped work with a short and obvious ending, which is the kind of job Codex finishes quickly and without ceremony.
Watch it work before it's live
Run a staged conversation — no account needed. The agent handles it for real while a simulated world answers its tool calls; nothing touches real accounts, and nothing is actually sent.
New subscriber
Free tier. utm_source=partner-swap, utm_campaign=aug-crosspost, referring site theampereletter.com. Signed up 07:41 CEST on mobile and confirmed the double opt in four minutes later. Her email domain matches a company already listed on the sponsor prospect sheet.
Set up in minutes
Using this template drops you into a guided setup. It asks exactly this, nothing else:
Connect beehiiv
One sign-in. The agent acts through your account, scoped to what this template uses.
Connect Slack
One sign-in. The agent acts through your account, scoped to what this template uses.
Tagging rules
Which tags go on a signup and where each one comes from, the custom fields worth filling from the subscription record, and what makes a subscriber notable enough to interrupt someone for, usually a company domain you sell to or anyone on a paid plan.
Runs on Codex
Preselected for this page — connect your Codex account during setup, or switch to NoClick's built-in models with one click.
Watch it handle a test run
A staged conversation against a simulated world — then it’s live.
Why Codex for this agent
Record in, tags out
Everything the agent needs is on the subscription record and everything it does is a small write back to beehiiv. In the common case there is nothing to reason about.
Three facts, three tags
Source, referrer and tier stay separate rather than collapsing into one blended label. Keeping fields apart is precision work rather than interpretation.
Before you fork
Can it move somebody between tiers or remove them?
No. The workflow holds tagging and custom field writes and nothing else, so status changes, tier moves, deletions and sending are absent rather than merely forbidden. That matters more here than in most templates, because billing sits behind the tier field and an agent with no reach into it cannot start a refund conversation.
Run it with a different agent
Put Beehiiv New Subscriber Agent to work on Codex
Free to start. Guided setup, a test run against staged conversations, and it's live.