How to launch a cold email campaign from Claude
How-to guide Updated 12 July 2026
How do you launch a cold email campaign from Claude?
Connect the HotHawk MCP server to Claude, then ask it to build the campaign, add your leads and start sending. Claude calls the same tools you use in the app: it drafts the steps, enrols the list, and activates the campaign across your warmed, rotated mailboxes once you approve the copy.
No credit card required.
Before you start
You need a HotHawk account and the HotHawk MCP server connected to Claude. It takes a couple of minutes and no code. Full setup is on the MCP server page.
Step by step
-
1
You ask Claude
Build a four step cold email campaign called SaaS Q3, sending on US business hours.
Claude callsmcp__hothawk__campaigns_createname "SaaS Q3" type COLD timezone America/New_York sendingStartTime 09:00 sendingEndTime 17:00 steps 4 stepsClaude creates the draft with your four steps and the 9 to 5 window, then reads the copy back so you can check every line before a single email goes out.
-
2
You ask Claude
Add the 480 leads from my "SaaS signups" list.
Claude callsmcp__hothawk__campaigns_leads_createcampaignId SaaS Q3 leadIds 480 leads allowLeadsInMultiple falseThe leads are enrolled. Anyone already sitting in another live campaign is skipped by default, so nobody gets two of your emails at once.
-
3
You ask Claude
Copy looks good. Launch it.
Claude callsmcp__hothawk__campaigns_activate_createcampaignId SaaS Q3SaaS Q3 goes live and starts sending across your warmed, rotated mailboxes, only inside the window you set.
-
4
You ask Claude
How is it doing so far?
Claude callsmcp__hothawk__workspaces_analytics_listworkspaceId current workspaceClaude pulls the numbers back into the chat: how many have sent, the replies in so far, and which step is doing the work.
Why launch a campaign from a chat at all
Building a campaign in any cold email tool is mostly clicking: name it, set the steps, pick the window, choose the mailboxes, load the list, check it, launch. None of that is hard. It is just slow, and it is the kind of slow that stops you spinning up the third or fourth campaign you meant to run this week.
Running it from Claude collapses that into a sentence. You describe the campaign you want and it assembles the pieces, then hands it back for a look. The work you actually care about, the offer and the copy, is where your time goes. The setup runs itself.
What Claude is really doing here
It is not a black box. Each instruction maps to one real HotHawk tool, the same endpoint the app calls when you click. Ask for a campaign and it runs campaigns_create. Add a list and it runs campaigns_leads_create. Say launch and it runs campaigns_activate_create. You can watch the tool calls happen, and you can ask to see the draft at any point before it goes live.
That is the line we care about. An AI SDR product decides for you and hopes you trust it. Here the model does the assembly and you keep the launch. It is your infrastructure, run from a chat.
The part an AI cannot skip
A campaign launched from Claude reaches the inbox the same way one launched by hand does, because the sending machinery sits under HotHawk, not under the model. Mailbox rotation, warmup on real Google and Microsoft inboxes, and best-practice sending are on by default. Open and link tracking are off for everyone. Claude can build and launch, but it cannot turn deliverability against you.
Once it is live, keep the chat open. Ask how the campaign is doing, which step is pulling replies, or to pause a weak variant, and it reads the numbers straight back to you. From here you can send a follow up on reply or personalise the next batch, both a sentence away.
The HotHawk tools behind this
Every action here is a real endpoint. Claude reaches it over the MCP server, and you can hit the same endpoints directly from the REST API if you would rather build it into your own stack.
-
mcp__hothawk__campaigns_createCreate the draft campaign, steps and schedule -
mcp__hothawk__campaigns_leads_createEnrol leads into the campaign -
mcp__hothawk__campaigns_activate_createSet it live and start sending -
mcp__hothawk__workspaces_analytics_listRead back sends, replies and performance
Frequently asked
Will Claude send emails without me approving them?
No. Claude builds the campaign as a draft and reads the copy back to you first. Nothing sends until you tell it to launch, and even then it only sends inside the schedule you set. You stay the one who says go.
Does this work with ChatGPT or my own agent, not just Claude?
Yes. The steps here use Claude and the MCP server because that is the quickest way in. Every tool is a REST endpoint underneath, so you can run the same flow from ChatGPT, a custom agent, or your own code.
What happens to deliverability when an AI launches the campaign?
The same protections apply whether a person or Claude hits launch. Sending rotates across your mailboxes, warmup runs on real Google and Microsoft inboxes, and open and link tracking stay off for everyone. The AI cannot switch those off.
Can I still edit the campaign in the app afterwards?
Of course. A campaign launched from Claude is a normal HotHawk campaign. Open it in the app to change copy, pause a step or adjust the schedule, exactly as you would any other.
Do I need to write any code to do this?
No. You add HotHawk as a connector in Claude once, then everything on this page is plain language. The REST API is there only if you want to build the flow into your own stack.