HubSpot + Hunter.io: cleaner lists, fewer bounces

Your HubSpot list looks fine… until the campaign goes out. Then come the bounces, the spam complaints, and the awkward question: “Why are we emailing bad addresses?” A simple HubSpot email validation loop fixes that before it hurts your sender reputation.

Marketing Ops feels this when list hygiene gets skipped. A CRM manager sees it when fields are missing or inconsistent. And a small team owner just wants deliverability without adding another weekly chore.

This workflow pulls unvalidated HubSpot contacts, checks each email with Hunter.io, writes the status back to the contact record, and sends you a clean summary email when it’s done.

How This Automation Works

Here’s the complete workflow you’ll be setting up:

n8n Workflow Template: HubSpot + Hunter.io: cleaner lists, fewer bounces

Click to explore

flowchart LR

    subgraph sg0["When clicking ‘Test workflow’ Flow"]
        direction LR
        n0["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/hubspot.svg' width='40' height='40' /></div><br/>HubSpot"]
        n1@{ icon: "mdi:play-circle", form: "rounded", label: "When clicking ‘Test workflow’", pos: "b", h: 48 }
        n2@{ icon: "mdi:swap-vertical", form: "rounded", label: "Loop Over Items", pos: "b", h: 48 }
        n3@{ icon: "mdi:cog", form: "rounded", label: "Replace Me", pos: "b", h: 48 }
        n4["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/hunter.png' width='40' height='40' /></div><br/>Hunter"]
        n5["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/httprequest.dark.svg' width='40' height='40' /></div><br/>Add Hunter Details (Contact)"]
        n6@{ icon: "mdi:cog", form: "rounded", label: "Wait", pos: "b", h: 48 }
        n7@{ icon: "mdi:message-outline", form: "rounded", label: "Send Email", pos: "b", h: 48 }
        n6 --> n3
        n4 --> n5
        n0 --> n2
        n3 --> n2
        n2 --> n7
        n2 --> n4
        n5 --> n6
        n1 --> n0
    end

    %% Styling
    classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
    classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
    classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
    classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
    classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
    classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
    classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
    classDef disabled stroke-dasharray: 5 5,opacity: 0.5
    class n1 trigger
    class n5 api
    classDef customIcon fill:none,stroke:none
    class n0,n4,n5 customIcon

Why This Matters: Email List Hygiene That Actually Sticks

Email validation is one of those “we’ll do it later” tasks that quietly turns into a real growth problem. People import lists, sales reps add contacts manually, forms accept typos, and suddenly your “high intent” segment contains addresses that will never deliver. Then you spend about 2 hours exporting CSVs, running checks in a separate tool, re-importing, and still not trusting the results because nothing is written back to the CRM in a consistent way. It’s not just time. It’s confidence.

The friction compounds, especially when multiple people touch the database.

You end up validating “one-off” lists, but the master CRM stays dirty and keeps generating future bounce problems.
Team members build segments off guesswork because there’s no dependable validation status field in HubSpot.
Manual checks get skipped during busy weeks, which means the next campaign inherits the mess.
Deliverability takes a hit, and the cost shows up later in lower inbox placement and more list churn.

What You’ll Build: HubSpot → Hunter.io Validation Loop + CRM Update

This automation starts by searching HubSpot for contacts that already have an email address, but do not yet have a Hunter validation status stored on their record. From there, it processes contacts one at a time (so you don’t overwhelm any API limits), and sends each email to Hunter.io’s Email Verifier. When Hunter returns a status, the workflow immediately updates the matching HubSpot contact via an API call, writing two properties: the validation status and the verification date. A short wait is added between records to keep things stable. Once every eligible contact has been checked, you receive a summary email letting you know the run finished.

The workflow begins with a manual run in n8n, which is useful for your first cleanup pass. After validation happens per contact, HubSpot becomes the single source of truth for “is this email safe to send to?” And the summary email gives you closure so you’re not babysitting the process.

What You’re Building

What Gets Automated

What You’ll Achieve

Find HubSpot contacts that have an email but no Hunter validation fields yet.
Verify each email through Hunter.io’s Email Verifier automatically.
Write the validation status and today’s date back onto the HubSpot contact record.
Send a completion email once the batch finishes running.

Cut a typical “export → validate → import” cleanup from about 2 hours down to a single run.
Fewer bounces in campaigns because you stop mailing obviously risky addresses.
Cleaner segmentation because every contact can carry the same validation properties.
More predictable handoffs between sales and marketing, since the CRM shows what’s verified.
A repeatable contact hygiene process you can run weekly or daily.

Expected Results

Let’s say you have 2,000 contacts in HubSpot that never got validated. Doing this manually usually means exporting a list (about 10 minutes), running a bulk check elsewhere (often 30 minutes or more), then re-importing and mapping fields (another 30 minutes), plus fixing odd formatting. Call it about 2 hours and a lot of context switching. With this workflow: start the run in a minute, let it process in the background (it waits 1 second per contact), then read the summary email when it’s done.

Before You Start

n8n instance (try n8n Cloud free)
Self-hosting option if you prefer (Hostinger works well)
HubSpot to store contacts and validation fields.
Hunter.io to verify email deliverability status.
HubSpot App Token (create a HubSpot Private App and copy the token).
Hunter API key (get it from your Hunter.io dashboard).
SMTP credentials (from your email provider for sending the summary).

Skill level: Beginner. You’ll connect accounts, add two custom properties in HubSpot, and paste a token into n8n.

Want someone to build this for you? Talk to an automation expert (free 15-minute consultation).

Step by Step

A manual run kicks things off. In n8n, you click “Test workflow” to start. That’s ideal for your first cleanup so you can verify the fields are being written correctly.

HubSpot is searched for “unvalidated” contacts. The workflow pulls contacts that have an email address and do not yet have the hunter_email_validation_status property. This keeps the run focused and avoids re-checking the same people every time.

Contacts are processed one-by-one. n8n uses a batching loop to take a single contact, send the email to Hunter.io for verification, then move to the next. A 1-second wait is added between contacts to reduce rate-limit headaches.

The contact record is updated and you get a summary. After Hunter returns a status, the workflow writes that status plus today’s date back to HubSpot via an HTTP PATCH call. When the loop ends, the Send Email node sends a “completed” message so you know the job finished cleanly.

You can easily modify the trigger to run on a schedule instead of manually based on your needs. See the full implementation guide below for customization options.

Step-by-Step Implementation Guide

Step 1: Configure the Manual Trigger

Start the workflow with a manual trigger so you can test the flow end-to-end before automating.

Add the Manual Execution Start node as the trigger.
Leave all parameters at their defaults (no configuration required).
Connect Manual Execution Start to Retrieve HubSpot Contacts.

Step 2: Connect HubSpot and Retrieve Contacts

Pull contacts from HubSpot that have an email address but are missing verification status.

Open Retrieve HubSpot Contacts and set Operation to search.
Enable Return All to true.
Set Authentication to appToken.
In the filters, include HAS_PROPERTY for email|string and NOT_HAS_PROPERTY for hunter_email_validation_status|enumeration.
Credential Required: Connect your hubspotAppToken credentials.

Tip: Keeping the filters as shown ensures you only verify contacts that still need validation.

Step 3: Batch Processing and Verification Loop

Split records into batches, verify emails with Hunter, and update HubSpot with verification results.

Configure Iterate Through Records to use batch processing (leave Options as default; reset is false).
Note the execution flow: Iterate Through Records outputs to both Dispatch Email Notice and Verify Email via Hunter in parallel.
In Verify Email via Hunter, set Operation to emailVerifier and Email to {{ $json.properties.email }}.
Credential Required: Connect your hunterApi credentials.
In Update Contact Verification, set URL to https://api.hubapi.com/crm/v3/objects/contacts/{{ $('Iterate Through Records').item.json.id }} and Method to PATCH.
Set JSON Body to { "properties": { "hunter_email_validation_status": "{{ $json.status }}", "hunter_verification_date": "{{ $now.format('yyyy-MM-dd') }}" } }.
Credential Required: Connect your hubspotAppToken credentials.

⚠️ Common Pitfall: The Update Contact Verification URL uses an expression tied to Iterate Through Records. If you rename the batch node, update the expression to match.

Step 4: Add Delay and Completion Email

Insert a delay between record updates and send a final notification email when processing is done.

Configure Delay Execution with Amount set to 1 (this uses the default unit in the Wait node).
Ensure Update Contact Verification connects to Delay Execution, then to Placeholder Step, and back into Iterate Through Records to continue batching.
Open Dispatch Email Notice and set Subject to Email Verification Completed for Your HubSpot Contacts.
Set To Email to [YOUR_EMAIL] and From Email to [YOUR_EMAIL].
Keep the HTML field as provided, including {{ new Date().getFullYear() }} in the footer.
Credential Required: Connect your smtp credentials.

Tip: Replace [YOUR_EMAIL] with a monitored address so you can confirm completion notices during testing.

Step 5: Test and Activate Your Workflow

Run a manual test, verify HubSpot updates, then activate the workflow for production use.

Click Execute Workflow on Manual Execution Start to run a test.
Confirm that Verify Email via Hunter returns a status and Update Contact Verification updates the contact properties in HubSpot.
Check that Dispatch Email Notice sends a completion email to your address.
When satisfied, toggle the workflow to Active for production use.

🔒

Unlock Full Step-by-Step Guide

Get the complete implementation guide + downloadable template

Troubleshooting Tips

HubSpot credentials can expire or lack the right scopes. If updates fail, check your HubSpot Private App permissions and the token used in the HubSpot node first.
If you’re using Wait nodes or external processing, timing varies. This workflow waits 1 second per contact; increase it if the Hunter or HubSpot API starts returning rate-limit errors.
The HTTP Request update depends on exact HubSpot property names. If your custom fields are named differently, the workflow will “succeed” but nothing will appear on the record, which is honestly the most frustrating failure mode.

Quick Answers

What’s the setup time for this HubSpot email validation automation?

About 30 minutes if you already have the API keys.

Is coding required for this email validation automation?

No. You’ll mostly connect accounts and confirm the HubSpot property names match what the workflow writes.

Is n8n free to use for this HubSpot email validation workflow?

Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in Hunter.io API usage costs, which depend on how many emails you verify.

Where can I host n8n to run this automation?

Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.

Can I modify this HubSpot email validation workflow for different use cases?

Yes, and it’s common. You can replace the Manual Trigger with a Schedule Trigger, or switch the HubSpot search to only pull contacts created in the last day. You can also change the “Update Contact Verification” HTTP Request node to write extra properties (like a “safe_for_marketing” checkbox) based on the Hunter status. Another popular tweak is adding an If node inside the loop so “risky” results get added to a suppression list or sent to a review queue.

Why is my HubSpot connection failing in this workflow?

Usually it’s the Private App token missing scopes for contacts, or the token was rotated and n8n is still using the old one. Also check the HTTP Request node, because it calls the HubSpot API directly and needs the same authorization to PATCH contact records. If the workflow runs but fields stay blank, the property internal names in HubSpot probably don’t match what you created.

What volume can this HubSpot email validation workflow process?

A lot, but it’s intentionally paced. This workflow waits 1 second per contact, so 1,000 contacts takes about 20 minutes plus API response time. On n8n Cloud, your limit depends on the plan’s monthly executions; if you self-host, there’s no execution cap and you mainly size your server for steady runs.

Is this HubSpot email validation automation better than using Zapier or Make?

Often, yes. n8n makes it easier to loop through a big batch, add waits to protect API limits, and update HubSpot through both native nodes and raw HTTP calls when you need more control. You also get a self-hosting option, which matters when you want to run contact hygiene frequently without watching task counts. Zapier or Make can be fine for small lists, but they get clunky when you need per-contact processing and CRM write-backs. Talk to an automation expert if you want help picking the simplest path.

Once validation lives inside HubSpot, you stop second-guessing every segment you build. Run it, get your summary email, and move on to work that actually grows revenue.

HubSpot + Hunter.io: cleaner lists, fewer bounces

How This Automation Works

n8n Workflow Template: HubSpot + Hunter.io: cleaner lists, fewer bounces

Why This Matters: Email List Hygiene That Actually Sticks