Cold email,run from ChatGPT.
ChatGPT writes the copy and picks the leads. HotHawk sends it. Connect over the REST API or a custom GPT, and let HotHawk rotate the mailboxes, keep warmup running, and label every reply at 40,000 a day and more.
No credit card required.
The outbound teams running AI on HotHawk
The basics
How do you run cold email with ChatGPT?
You have ChatGPT do the writing and lead research, then send it through HotHawk. HotHawk is the layer that actually sends: inbox rotation, warmup on real Google and Microsoft inboxes, 40,000 a day and more, and a Master Inbox that labels every reply out of the box.
With ChatGPT you connect over the REST API with a Bearer token, or wrap HotHawk as a custom GPT action. Webhooks push replies back to your agent as they arrive. ChatGPT handles the words, HotHawk handles the sending, and you keep control of what goes out.
What it does
ChatGPT writes. HotHawk sends.
Your agent handles the copy and the leads. HotHawk does the sending over the API, keeps your mailboxes healthy, and sorts what comes back.
One endpoint builds and sends a campaign.
Have ChatGPT write the copy and pick the leads, then POST it to HotHawk. The API creates the campaign, imports the list and sends across your warmed mailboxes. Bearer token auth, JSON in, JSON back. If ChatGPT can call a function, it can send.
Sending that holds up at volume.
ChatGPT does the writing. HotHawk does the hard half: inbox rotation across every mailbox, warmup running on real Google and Microsoft inboxes, and the headroom for 40,000 a day and more. The API never lets an agent quietly hammer one account into the spam folder.
Webhooks push replies back to your agent.
Point a webhook at your stack and HotHawk tells ChatGPT the moment a lead replies, an out of office fires, or a positive answer arrives. Your agent reacts on the event instead of polling for it. That is how you build a loop that actually keeps up.
Every reply, labelled and yours to answer.
The Master Inbox catches every response, forwarded and out of office included, and HotHawk's own AI labels each one out of the box: Interested, Not interested, Out of office. Have ChatGPT draft answers over the API for a human to approve, so a warm lead never sits in a thread nobody read.
Try it
See it in action
Build an AI SDR workflow
Wire an agent that researches, sends and follows up.
Read the guideBulk import and clean a lead list
Push a raw list to HotHawk and dedupe it over the API.
Read the guidePull your cold email analytics
Query reply and positive counts straight into your agent.
Read the guideWhat you get
What you get
REST or a custom GPT.
Call HotHawk over the API from your ChatGPT agent, or wrap it as a custom GPT action. Bearer auth, webhooks, clean JSON.
Real send volume.
Your agent sends 40,000 a day and more across warmed, rotated mailboxes, not a handful from one API-connected inbox.
You keep the guardrails.
Rotation, warmup and tracking-off are enforced by HotHawk, not your prompt. The agent runs the campaign, it cannot undo the protections.
ChatGPT cold email FAQs
How do you run cold email with ChatGPT?
You have ChatGPT write the copy and pick the leads, then send it through HotHawk. HotHawk is the layer that actually sends, at volume, across warmed and rotated mailboxes. You connect ChatGPT over the REST API with a Bearer token, or wrap HotHawk as a custom GPT action. ChatGPT handles the words, HotHawk handles the sending.
How does HotHawk connect to ChatGPT?
Over the REST API, which covers every action: campaigns, mailboxes, leads, replies and reporting. You call it from your ChatGPT agent with a Bearer token, or wrap HotHawk as a custom GPT action. HotHawk also has an MCP server, and as ChatGPT widens its MCP support the same server works there too. Either way you are calling the same endpoints, so nothing about the sending changes.
Is this an AI SDR?
No. An AI SDR is sold as a hands-off agent that runs outbound for you. HotHawk is the execution layer it runs on. You build the agent with ChatGPT and stay in control, while HotHawk handles the sending, deliverability and reply management underneath. You keep the keys.
Does letting an agent send over the API hurt deliverability?
No. The protections live in HotHawk, not the prompt. Sending rotates across your mailboxes, warmup runs on real Google and Microsoft inboxes, and open and link tracking stay off for everyone. Your ChatGPT agent runs the campaign, but it cannot switch off the practices that keep your sending healthy.
Do I need to write code?
For ChatGPT, some. The REST API is how you connect it, so you or a developer wires up the calls, or you build a custom GPT action pointed at the endpoints. The endpoints are clean JSON, so it is a small job for a developer, not a big build.
Build with the API
Every campaign, mailbox and reply action over REST, with Bearer auth and webhooks. This is the ChatGPT path.
Read the API docsThe AI cold email hub
See the whole picture of AI cold email on HotHawk, and every way to connect your model.
Explore AI cold emailSend cold emails that get delivered. Never miss a positive reply.
Serious deliverability paired with the best reply management in the market.
No credit card required.