EmailBison Campaign Launch
This skill builds a campaign the way it should be built: one campaign per lead list, every offer and copy template as A/B variants inside a single step, all senders attached, the deliverability-protecting settings applied, and the schedule set to the recipients' timezone. It stops one step short of sending on purpose. There is no activation code anywhere in it, because the QA gate downstream only works if nothing can route around it.
Pipeline Playbooks · Open Source, MIT Licensed
Assembles a complete EmailBison campaign end to end, copy, leads, senders, schedule, then deliberately stops at draft so nothing can go live without the QA gate.
When to use this
- Copy is approved, list is clean, senders are warm
- Ready to build the campaign or upload the leads
- Getting a campaign live in EmailBison for the first time
- Rebuilding a campaign after a rework
What it covers
- The core rule: one campaign per lead list, offers and templates go in as variants, not separate campaigns
- Creating the campaign and loading all copy variants of a step in one POST
- The deliverability settings set: plain_text, open_tracking off, daily limits at 1000+
- Why campaign caps aren't volume control, senders govern volume
- Uploading leads: bulk upsert then attach, verifying total_leads against the source count
- Attaching every available sender, not some, and verifying the full match
- Setting the schedule to weekdays, business hours, recipient timezone
- Stopping at draft: pre-launch-qa runs next, then you press start yourself
Install just this skill
Every skill folder is self-contained. Run this from your project root to pull just this one into .claude/skills/emailbison-campaign-launch/:
npx degit joelwylie7/cold-email-playbooks/.claude/skills/emailbison-campaign-launch .claude/skills/emailbison-campaign-launch
Want the whole system, not just one skill?
Related skills
Pre-Launch QA
A numbered gate that checks copy, settings, leads, senders, schedule and sequence structure before any campaign launches or resumes, PASS or FAIL, one line of evidence each.
EmailBison API
The EmailBison API reference built from getting it wrong first: auth failures that look like success, pagination that silently truncates at 15, and one PATCH that can flip live campaign settings.
Sequence Architecture
Joel's 4-step cold sequence: a first touch, a same-thread nudge at +3 days, a fresh thread with a new offer angle at +30 days, then a final nudge.