Every 15 minutes
Post Hunter campaign replies to Slack
When a recipient replies to one of your Hunter campaigns, your team sees it in Slack.
- Runs
- Every 15 minutes
- Apps
- Hunter.io
- AI
- Not needed
- Access
- API key
Send this to your assistant
Create a ClickRuntime automation: every 15 minutes, check my Hunter campaigns for recipients who have replied and post their name, email and campaign to #outreach in Slack.
First time? Adding ClickRuntime to your assistant takes about two minutes.
Why use it
Why teams use this automation
You send a Hunter campaign to 400 prospects, and replies arrive in the mailbox you connected, mixed with out-of-office messages and newsletters. A genuinely interested prospect writes back on Tuesday morning and is not noticed until Thursday, because the inbox is busy and nothing marks Hunter replies as special. Cold outreach rewards speed, and a warm reply left for two days has often cooled.
Every 15 minutes, ClickRuntime lists the recipients of your Hunter campaigns, spots anyone whose status has changed to replied since the last check, and posts a message in Slack. The post names the prospect and the campaign so you can open the thread and answer while they are still looking at their inbox.
It suits founders and small sales teams who run outreach alongside other work and cannot watch a mailbox all day.
What you get out of it
Warm replies get answered fast
The first reply to a cold email is a short window of attention. A Slack message within a quarter hour lets you respond while the prospect still remembers your message, which is when meetings get booked.
Reply handling does not depend on inbox checks
Outreach replies mix with everything else in a mailbox. A separate alert for the ones that matter means they cannot be buried under invoices and notifications you were never going to read promptly.
See which campaigns get responses
Alerts show the campaign name, so you learn which sequences generate replies. That informs which subject lines and audiences deserve more sends, based on real conversations rather than open-rate guesses.
Shared outreach has a clear owner
In a team, the Slack post can be claimed with a reaction. Two people stop replying to the same prospect, which looks careless and costs credibility with a person you were trying to win.
Less time scanning Hunter itself
You no longer open the campaign dashboard several times a day to check on results. The tool tells you when something happened, which returns that time to writing messages and preparing calls.
How it works
What happens, step by step
Every 15 minutes, ClickRuntime goes through your Hunter campaigns and their recipients.
It looks for recipients whose status is now replied and skips anyone it has already posted.
Each new reply is posted to #outreach in Slack with the person's name, email and the campaign.
Before it runs live
- Connect Hunter.io
What you get
Build your own
Need it to work differently?
Your own rules
Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.
Any number of apps
One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.
AI where it helps
Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.
On a schedule or on each event
Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.
Changes you can ask for
- Act only on the items that match your own rules, and skip the rest
- Add an AI step, for example to summarize, sort or draft a reply
- Add another app, for example also send it to Slack
- Combine it with other Hunter.io steps into one automation
Under the hood
The code that runs this automation
from clickruntime import on_trigger, credentials, notify, http, state, report_fetched
API = "https://api.hunter.io/v2"
@on_trigger
def run(event):
key = credentials.secret("HUNTER_API_KEY")
seen = set(state.get("replied") or [])
new = []
for c in http.get(f"{API}/campaigns", params={"api_key": key}).json()["data"]["campaigns"]:
recipients = http.get(f"{API}/campaigns/{c['id']}/recipients",
params={"api_key": key}).json()["data"]["recipients"]
for r in recipients:
uid = f"{c['id']}:{r['email']}"
if r.get("status") == "replied" and uid not in seen:
new.append((uid, r, c["name"]))
report_fetched(len(new))
if not new:
return {"posted": 0}
for uid, r, campaign in new:
name = f"{r.get('first_name') or ''} {r.get('last_name') or ''}".strip()
notify.slack(f"Reply: {name} <{r['email']}> in {campaign}", channel="#outreach")
seen.add(uid)
state.set("replied", sorted(seen))
return {"posted": len(new)}FAQ
Common questions
Does it alert on out-of-office auto-replies too?
Will I be alerted once per prospect or on every reply?
Do I need a paid Hunter plan for this to work?
What permissions does it need?
Does it need AI?
How many runs does it use?
Can I change how it works?
Related
You might also like
Verify new leads in a Hunter list every day
Each day you get the new leads whose emails are invalid or risky, before you write to them.
See how it worksGet warned when Hunter credits run low
Each morning, Hunter's account usage is checked and an email goes out when searches or verifications left for the month drop below 10%, with the reset date.
See how it worksAdd new contacts at target companies to a Hunter list
Every Monday, Hunter's Domain Search runs for a set of company domains and any new contacts in chosen departments are saved as leads in a Hunter list, with an email summary.
See how it worksKeep exploring
Set up “Post Hunter campaign replies to Slack” from your assistant
Copy the prompt above, or connect your assistant first. Free plan, no credit card.