Skip to content

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.

Paste it into your assistant. It tells you what it will send or change before it runs live.

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

  1. Once a day, ClickRuntime checks your chosen Hunter leads list for leads added since its last run.

  2. Each new email address is checked with Hunter's email verifier. Leads already checked are skipped.

  3. 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

RunsDaily
Verify new leads in a Hunter list every daytoday, 9:00Succeeded
Email · Hunter verification3 risky or undeliverable leads ceo@northwind.io: undeliverable (invalid)

Build your own

Need it to work differently?

This template is a starting point. Copy the prompt and change it, or describe a different automation from scratch, with your own conditions, more apps or an AI step. Your assistant writes it, tests it and runs it on ClickRuntime.
  • 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

This is the Python script that runs each time the automation starts. Your AI assistant writes it for you when you send the prompt, and you allow each step in your assistant. To change how the automation works, describe the change to your assistant and it updates the script for you. For every function it can use, see the script reference.
verify_new_leads_in_a_hunter_list.pyexample
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?
Risky usually means the address could not be fully confirmed, for example a catch-all domain that accepts every address, or a mailbox that did not give a clear answer. It may still work, but it carries a higher chance of bouncing, so treat it with caution.
Does each verification use my Hunter credits?
Hunter's Email Verifier counts against the verification allowance on your Hunter plan, so each lead checked uses one. If you have a large list and a tight allowance, ask for the check to run on only certain lists or lead sources.
Does it remove bad leads from my list automatically?
No. It reports the invalid and risky addresses by email and leaves your Hunter list untouched, so you decide what to do. That avoids deleting a catch-all contact you know is real, and it keeps you in control of your data.
What permissions does it need?
API key. Nothing else in your accounts is used.
Does it need AI?
No. It runs without AI, so it doesn't use your plan's AI allowance.
How many runs does it use?
One run each time it runs (daily). Checks that find nothing to do and stop right away aren't counted.
Can I change how it works?
Yes. Describe the change to your AI assistant, for example a different schedule, channel or filter. It updates the automation, tests it and tells you what changed.

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.