Daily
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.
- Runs
- Daily
- Apps
- Hunter.io
- AI
- Not needed
- Access
- API key
Send this to your assistant
Create a ClickRuntime automation: every day at 7am, verify the emails of leads added to my Hunter list 'Q3 SaaS founders' since yesterday, and email me the ones that are undeliverable or risky.
First time? Adding ClickRuntime to your assistant takes about two minutes.
Why use it
Why teams use this automation
A marketer imports 300 new leads into a Hunter list and starts an outreach sequence the same afternoon. Forty of the addresses are dead, mistyped or catch-all mailboxes. The bounces hit within a day, the sending domain's reputation drops, and the next campaign, to the good addresses, lands in spam. One careless import ends up hurting every email the company sends for weeks.
Each day, ClickRuntime finds leads added to your Hunter list since its last run and passes each address through Hunter's Email Verifier. It then emails you a short list of the ones that came back invalid or risky, along with the verification result, so you can remove them before they are ever emailed.
This is most valuable for teams that import leads in bulk from events, scrapers or partner lists.
What you get out of it
Protect the domain you send from
High bounce rates teach mailbox providers to distrust your domain. Catching invalid addresses before the first send keeps your bounce rate low and your normal emails, such as invoices and replies, arriving in inboxes.
Stop paying to email dead addresses
Sending tools and sequences cost money per contact or per send. Removing addresses that cannot receive mail means your outreach budget and your daily sending limits go toward people who can actually read it.
Fix bad data at the source
The list of failures shows patterns, such as typos in one importer's data or an old event list. You can correct the process that created the bad addresses, instead of repeatedly cleaning up after it.
Verification happens without a manual step
Running a list through a verifier by hand is exactly the task skipped when a campaign is in a hurry. Because new leads are checked each day, nobody has to remember to upload and wait.
Sales time goes to reachable people
Reps who call or LinkedIn-message contacts based on a lead list waste effort on records with nothing behind them. Flagging bad emails early helps them judge which leads are worth personal effort.
How it works
What happens, step by step
Once a day, ClickRuntime checks your chosen Hunter leads list for leads added since its last run.
Each new email address is checked with Hunter's email verifier. Leads already checked are skipped.
If any addresses come back undeliverable or risky, you get an email listing each one with its result, so you can remove them before writing.
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
- Run it at a different time, more or less often, or only on weekdays
- 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
LIST_ID = 123456 # Hunter leads list "Q3 SaaS founders"
@on_trigger
def run(event):
key = credentials.secret("HUNTER_API_KEY")
since = state.get("last_created_at") or ""
leads = http.get("https://api.hunter.io/v2/leads",
params={"leads_list_id": LIST_ID, "limit": 1000, "api_key": key}).json()["data"]["leads"]
new = [l for l in leads if l["created_at"] > since]
flagged = []
for lead in new:
v = http.get("https://api.hunter.io/v2/email-verifier",
params={"email": lead["email"], "api_key": key}).json()["data"]
if v["result"] in ("undeliverable", "risky"):
flagged.append(f"{lead['email']}: {v['result']} ({v['status']})")
if new:
state.set("last_created_at", max(l["created_at"] for l in new))
if flagged:
notify.email_me(f"{len(flagged)} risky or undeliverable leads", "\n".join(flagged))
return {"checked": len(new), "flagged": len(flagged)}FAQ
Common questions
What does a risky result mean in Hunter's verifier?
Does each verification use my Hunter credits?
Does it remove bad leads from my list automatically?
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
Get 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 worksFind missing emails for leads in a Hunter list
Every day, leads in a Hunter list that have a name and company domain but no email are run through Hunter's Email Finder, and found addresses are saved back to the lead.
See how it worksKeep exploring
Set up “Verify new leads in a Hunter list every day” from your assistant
Copy the prompt above, or connect your assistant first. Free plan, no credit card.
