smartlead-cold-email-operator

Drop in your list. Get a Smartlead campaign, an opener for every lead, and a warm-inbox check — ready to launch. Preinstalled on Claude Code. Fork it, export your key, go. Nothing auto-sends.

NewNew10.9 KB snapshotStarter VM

What's inside

Harness

Claude Code

Plan

Starter

vCPU

1

Memory

2 GiB

Snapshot

10.9 KB

How it works · ~3 minutes

  1. 01 · Fork

    New isolated microVM on your subdomain — creator state included.

  2. 02 · Your keys

    Log into Claude Code with your own model credentials (BYOK).

  3. 03 · Ask it to work

    Open the terminal and give it a real job. You keep what ships.

30-day money-back on your first purchase · no free trial · keys never leave the VM

About this template

Build the whole campaign. Then don't send it.

You already know the Smartlead motion — and the one part you never want automated is the send.

Import the list. Write a sequence. Personalize the opener. Check the inboxes are warm. Launch. Then work the replies.

What you do not want: rebuilding that by hand in the Smartlead UI every launch, or re-explaining the whole motion to a blank chat. Worst of all: handing an AI your domain and hoping it doesn't blast 400 people with "Hi {{first_name}}."

This template is that motion, already on Claude Code. It preps the whole campaign end to end and stops at the send.

Fork it. Log into your Claude. export SMARTLEAD_API_KEY from your Smartlead account. Then paste:

Here's my leads.csv from Clay. Build a 3-step Smartlead campaign for it, write a personalized opener for each lead, and check my sending accounts are warm.

You get a draft campaign in Smartlead, a real sequence, an opener for all 400 leads from one paste (Smartlead's per-request max), and a deliverability go/no-go — under ~/outputs/. Ask it to "send it" and it says: open Smartlead and hit Start. It does not send on your behalf. That refusal is the feature.

What it does

  • sequence-builder — creates the campaign in draft and saves a multi-step sequence with merge fields. Real subject and body copy, not placeholder text.
  • opener-personalizer — one opener per lead from real enrichment (title, company, a funding or hiring signal). Can't personalize a lead? It flags that lead instead of faking a line that torches your domain.
  • deliverability-watch — warmup health, mailbox rotation, bounce risk. A plain go/no-go before you launch.
  • reply-triage — pulls the reply queue and sorts it: positive, out-of-office, not interested, wrong contact. Drafts your reply to the positives. You send it.

First five minutes

  1. Fork this template → open the terminal.
  2. Log into Claude Code (claude or your Anthropic key).
  3. export SMARTLEAD_API_KEY=... (Smartlead → Settings → API).
  4. Paste the demo prompt above.

Your Smartlead sending and credits are yours — same as the Smartlead UI. No markup. No mystery keys in the snapshot.

Who this is for

  • Founders and GTM engineers who already run Smartlead
  • People who want Claude Code to drive Smartlead, not re-learn the API every session
  • Anyone who wants AI to do the tedious 90% and stop at the send

Who this is not for

  • Teams who want the full Smartlead UI as the control plane (use Smartlead's product)
  • Anyone who wants one-click autonomous send on day one (the human gate is the point)
  • Tire-kickers with no Smartlead plan (sending is real, on your account)

Pairs with

  • Clay Outbound Engine — builds the list this template sends. Clay finds the 20 CEOs and the work emails; this turns them into a ready-to-launch Smartlead campaign.

BYOK

You bringNotes
Claude Code login / ANTHROPIC_API_KEYRun-time only
SMARTLEAD_API_KEYSmartlead → Settings → API. Environment only, stays on your VM. Never written to a file.

Upstream

The rule that keeps you safe

Never auto-send. This agent builds the campaign, the sequence, and the first line for every lead. It creates everything in draft and never flips a campaign to Start. You hit send in Smartlead.

Fork it. It's yours.

Nothing's trapped here

Cancel anytime and it all stays yours — your Smartlead account, your sending, your sequences, your list. None of it ever lived in our platform; the key was only ever an env var on your VM. On top of that: jurniti 30-day money-back on your first paid purchase.

Fork it. export SMARTLEAD_API_KEY. Paste your list.

Inside this fork

Forking copies this template into a brand-new, fully isolated microVM on your own subdomain. Here's exactly what lands in it.

  • Claude Code agent

    The upstream harness, pre-installed — same version the creator ran.

  • Starter VM

    1 vCPU · 2 GiB RAM · 10 GiB disk.

  • Creator's /persist data

    The captured persist volume is copied byte-for-byte into your fork.

  • BYOK — your keys, your VM

    Add your model API keys after forking; they live only inside your microVM.

What this agent can do

1 skill

  • smartlead-outbound

    Human-in-the-loop cold email on Smartlead. Build the campaign, write the multi-step sequence, personalize an opener for every lead from…

What you'll configure after forking

Secrets are scrubbed from shared templates — these are the names you supply in your agent's terminal once it boots.

Environment variables

  • ANTHROPIC_API_KEY

Your turn

Your own smartlead-cold-email-operator, live in about 3 minutes.

Forking copies this Claude Codeagent into a brand-new, fully isolated microVM on your own subdomain — the creator's /persist state and all. Add your own keys after it boots; they never leave the box. Don't love it? Your first jurniti purchase comes with 30 days to get every cent back.

New paid VM · BYOK · 30-day money-back on your first purchase · ~3 min to provision

Starter · fork

$25/ mo

Needs 1 of your own API key