Send Cold Email Replies to Your CRM

How do you send cold email replies to your CRM?

Register a webhook in HotHawk and point it at your CRM. When a reply or a positive reply comes in, HotHawk posts the event and the lead to your endpoint, and your stack does the rest. From Claude that is one sentence per webhook, and it keeps your CRM in sync without anyone copying replies across by hand.

Start your 7 day free trial Connect the MCP server

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
Fire a webhook to my CRM whenever a reply comes in.

Claude calls mcp__hothawk__webhooks_create

url https://hooks.mycrm.com/hothawk event reply.received

Claude registers the webhook. From now on, every reply posts to your endpoint the moment it arrives, with the lead and the thread attached.
2

You ask Claude
Add a second one that only fires on positive replies.

Claude calls mcp__hothawk__webhooks_create

url https://hooks.mycrm.com/hot-leads event reply.positive

A second webhook is live. Now your hottest replies hit a separate endpoint, so your CRM can route the ready-to-talk ones straight to a rep.
3

You ask Claude
Show me every webhook I have set up.

Claude calls mcp__hothawk__webhooks_list

workspaceId current workspace

Claude lists both, with the event each one listens for and where it posts, so you can see exactly what your stack is being told.

The reply is where the handover breaks

A cold email programme earns its keep at one moment: someone replies and says yes. Everything before that is setup. The problem is that the reply arrives in HotHawk and the deal lives in your CRM, and the gap between the two is usually a person copying details across, or forgetting to. Hot leads go cold in that gap more than anywhere else.

A webhook closes it. Instead of anyone watching the inbox and updating records by hand, HotHawk tells your CRM the instant a reply arrives, and your stack acts on it right away. The reply and the record stay in step on their own, which is exactly what you want when a rep is waiting on a warm lead.

Push the event, let your stack run

Setting one up is a sentence. Ask Claude to fire a webhook on replies and it runs webhooks_create, registering an endpoint that posts every reply, with the lead and thread attached, to a URL you own. Want to be pickier? Point a second webhook at positive replies only, so your keenest prospects hit a different endpoint and can be routed straight to a rep.

HotHawk's job ends at the push. It sends the event out; your CRM or automation tool decides what happens next. Create the contact, move the deal stage, raise a task, drop a message into Slack, the logic sits in your stack where it belongs. Because a webhook is just an HTTP post, it works with any CRM or tool that can take one, so you are not tied to a single integration.

It changes nothing about how you send

A webhook only reads what has already happened and passes it on. It does not touch the sending side, so all the infrastructure that gets you the reply in the first place carries on untouched. Sending still rotates across your mailboxes, warmup still runs on real Google and Microsoft inboxes, and open and link tracking stay off by design. This is a notification going out, not a lever being pulled on the send.

Pair it with the rest and the loop gets tidy. A reply can fire a webhook to your CRM and trigger a follow up in the same breath, all wired up from the same chat. HotHawk handles the sending and the signal; your stack handles the record. Nobody sits copying replies across a browser tab.

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__webhooks_create Register a webhook that fires on a chosen event
mcp__hothawk__webhooks_list See every webhook and the event it listens for
mcp__hothawk__webhooks_delete Remove a webhook you no longer need

MCP server setup Read the API docs

Frequently asked

Which events can I fire a webhook on?

The ones that matter for a cold email programme, like a reply arriving or a reply being marked positive. You point each webhook at the event you care about, so your CRM only hears about the things it needs to act on.

What does my CRM do with the webhook?

Whatever you build it to. HotHawk posts the event and the lead and thread that go with it, and your stack takes it from there: create the contact, move a deal stage, ping a rep in Slack, start a task. We push, you decide what happens next.

Does this only work with one CRM?

No. A webhook is just an HTTP post to a URL you own, so it works with any CRM or tool that can receive one, and with automation platforms in between. If your stack has an inbound endpoint, HotHawk can feed it.

Are the deliverability protections still on when replies fire a webhook?

Yes, and the webhook does not touch sending at all. It reads events and posts them out. Sending still rotates across your mailboxes, warmup still runs on real Google and Microsoft inboxes, and open and link tracking stay off. This is a notification, not a change to the machinery.

Do I need to write code?

Registering the webhook needs none. You add HotHawk as a connector in Claude and set it up in plain language. The endpoint that receives it lives in your CRM or automation tool, so whether you write code there is up to your stack.

Keep going

Auto follow up after a reply Trigger a follow up the moment a lead replies Launch a campaign from Claude Build, fill and send a campaign from a chat AI cold email software The whole picture: what AI runs on inside HotHawk AI cold email Run your cold email infrastructure from a chat

How to send cold email replies to your CRM