cold-email-campaign-deploy

Deploy cold email campaigns to Email Bison or Instantly via API in paused state.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/LGJ-Jonathan/Jonathan_Global_Claude_Skills --skill cold-email-campaign-deploy-lgj-jonathan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cold-email-campaign-deploy
Source: https://github.com/LGJ-Jonathan/Jonathan_Global_Claude_Skills/tree/main/cold-email-campaign-deploy
Command: npx skills add https://github.com/LGJ-Jonathan/Jonathan_Global_Claude_Skills --skill cold-email-campaign-deploy-lgj-jonathan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Deploying a cold email campaign involves compiling strategy, copy, and A/B variants into a brief, verifying deliverability safeguards, and making multiple error-prone API calls to a sequencer. This Skill automates that entire deployment workflow while enforcing safety gates that protect sender domain reputation. ## Core Features & Use Cases - Campaign Brief Generation: Compiles upstream strategy, copy, and A/B testing artifacts into a complete campaign brief using a structured template. - 8-Gate Pre-Launch Checklist: Validates email verification, warmup scores, DNS authentication, tracking settings, spintax format, A/B variant minimums, and sender signatures before any API call. - Dual-Sequencer API Deployment: Creates campaigns in Email Bison or Instantly in PAUSED/DRAFT state, with correct variant linking, sender attachment, and deliverability-safe settings. - Error Recovery Guidance: Provides specific recovery steps for partial deployments, API errors, and rollback without breaking variant structures. - Use Case: After running strategy, copywriting, and A/B testing skills, deploy a 4-email sequence with 9 variants across 90 sender accounts to Email Bison, generating the brief, passing all safety gates, and creating the campaign paused for review. ## Quick Start Deploy my campaign to Email Bison using the strategy, copy, and A/B variant files in the workspace, and show me the campaign brief and API calls.

Frequently Asked Questions about cold-email-campaign-deploy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy a cold email campaign to Email Bison via API?

Create the campaign with POST /campaigns, add sequence steps with A/B variants via POST /campaigns/v1.1/{id}/sequence-steps using variant_from_step positional indexes, attach sender emails, then PATCH settings with open_tracking false and plain_text true. The campaign is created in paused state for review.

How do I create an Instantly campaign with A/B variants through the API?

Use POST /campaigns with the full sequences structure embedded, nesting variants inside each step's variants array. The campaign_schedule with a schedules array is required, and follow-up emails use an empty subject for threading. Campaigns are created as status 0 (draft).

Email Bison vs Instantly spintax format differences?

Email Bison uses {option1|option2|option3} format while Instantly uses {{RANDOM | option1 | option2 | option3}}. Deploying with the wrong format renders spintax as literal text in sent emails, so the format must match the target sequencer before deployment.

Why are my Instantly emails blank after API deployment?

Instantly strips all text content from emails containing <br> tags, which is the most common cause of blank emails. Use only <p> tags for paragraph breaks in email bodies, including signature lines.

What pre-launch checks should pass before deploying a cold email campaign?

Verify lead lists with bounce rate under 3%, confirm warmup scores of 95 or higher on all senders, ensure SPF/DKIM/DMARC are configured, disable open and link tracking, use plain text, apply spintax, and meet A/B variant minimums of 3 variants on email 1 and 2 on each follow-up.

What happens if campaign deployment fails partway through the API calls?

Since campaigns are created in paused state, recovery is safe. If sender attachment fails, retry with backoff or attach via the sequencer UI. If steps are partially created, delete all created steps and recreate the full sequence, since editing individual steps breaks variant linking.