Skip to main content

HubSpot contact email validation with Hunter.io

Workflow preview

Workflow preview
100%
HubSpot contact email validation with Hunter.io preview
Open on n8n.io

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

Workflow: HubSpot Contact Email Validation with Hunter.io Overall Goal This workflow retrieves contacts from HubSpot that have an email address but haven't yet had their email validated by Hunter. ...

Best for

  • Lead Generation automation workflows
  • intermediate n8n builders looking for reusable templates

Tools used

n8n-nodes-base.hubspot, n8n-nodes-base.manualtrigger, n8n-nodes-base.splitinbatches, n8n-nodes-base.noop, n8n-nodes-base.hunter, n8n-nodes-base.httprequest, n8n-nodes-base.wait, n8n-nodes-base.stickynote

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Akhil Varma Gadiraju.

Original n8n.io source

1.1 Workflow description

Title
HubSpot contact email validation with Hunter.io
Workflow name
HubSpot contact email validation with Hunter.io

Workflow: HubSpot Contact Email Validation with Hunter.io

Overall Goal

This workflow retrieves contacts from HubSpot that have an email address but haven't yet had their email validated by Hunter. It then iterates through each of these contacts, uses Hunter.io to verify their email, updates the contact record in HubSpot with the validation status and date, and finally sends a summary email notification upon completion.

How it Works (Step-by-Step Breakdown)

Node: "When clicking ‘Test workflow’" (Manual Trigger)

  • Type: n8n-nodes-base.manualTrigger
  • Purpose: Start the workflow manually via the n8n interface.
  • Output: Triggers workflow execution.

Node: "HubSpot" (HubSpot)

  • Type: n8n-nodes-base.hubspot
  • Purpose: Fetch contacts from HubSpot.
  • Configuration:
    • Authentication: App Token
    • Operation: Search for contacts
    • Return All: True
    • Filter Groups:
      • Contact HAS_PROPERTY email
      • Contact NOT_HAS_PROPERTY hunter_email_validation_status
  • Output: List of contact objects.

Node: "Loop Over Items" (SplitInBatches)

  • Type: n8n-nodes-base.splitInBatches
  • Purpose: Process each contact one-by-one.
  • Configuration:
    • Options > Reset: false
  • Output:
    • Output 1 to "Hunter"
    • Output 2 to "Send Email"

Node: "Hunter" (Inside the loop)

  • Type: n8n-nodes-base.hunter
  • Purpose: Verify email with Hunter.io
  • Configuration:
    • Operation: Email Verifier
    • Email: {{ $json.properties.email }}

Node: "Add Hunter Details (Contact)" (HTTP Request - Inside the loop)

  • Type: n8n-nodes-base.httpRequest
  • Purpose: Update HubSpot contact.
  • Configuration:
    • Method: PATCH
    • URL: https://api.hubapi.com/crm/v3/objects/contacts/{{ $('Loop Over Items').item.json.id }}
    • Headers: Content-Type: application/json
    • Body (JSON):
      {
        "properties": {
          "hunter_email_validation_status": "{{ $json.status }}",
          "hunter_verification_date": "{{ $now.format('yyyy-MM-dd') }}"
        }
      }
      

Node: "Wait" (Inside the loop)

  • Type: n8n-nodes-base.wait
  • Purpose: Avoid API rate limits.
  • Configuration: Wait for 1 second.

Node: "Replace Me" (NoOp - Inside the loop)

  • Type: n8n-nodes-base.noOp
  • Purpose: Junction node to complete the loop.

Node: "Send Email" (After the loop completes)

  • Type: n8n-nodes-base.emailSend
  • Purpose: Send summary notification.
  • Configuration:

Sticky Notes

  • "HubSpot": Create custom properties (hunter_email_validation_status, hunter_verification_date).
  • "Add Hunter Details": Ensure field names match HubSpot properties.
  • "Wait": Prevent API rate limits.

How to Customize It

Trigger

  • Replace Manual Trigger with Schedule Trigger (Cron) for automation.
  • Optionally use HubSpot Trigger for new contact events.

HubSpot Node

  • Create matching custom properties.
  • Adjust filters and returned properties as needed.

Hunter Node

  • Minimal customization needed.

HTTP Request Node

  • Update JSON property names if renaming in HubSpot.
  • Customize date format as needed.

Wait Node

  • Adjust wait time to balance speed and API safety.

Email Node

  • Customize email addresses, subject, and body.
  • Add dynamic contact count with a Set or Function node.

Error Handling

  • Add Error Trigger nodes.
  • Use If nodes inside loop to act on certain statuses.

Use Cases

  • Clean your email list.
  • Enrich CRM data.
  • Prep verified lists for campaigns.
  • Automate contact hygiene on a schedule.

Required Credentials

HubSpot App Token

  • Used by: HubSpot node and HTTP Request node
  • Create a Private App in HubSpot with required scopes.

Hunter API

  • Used by: Hunter node

SMTP

  • Used by: Email Send node
  • Configure host, port, username, and password.

Made with ❤️ using n8n by Akhil.

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - HubSpot

Type / Role
n8n-nodes-base.hubspot - hubspot
Config choices
Version 2.1

Block 2 - When clicking ‘Test workflow’

Type / Role
n8n-nodes-base.manualTrigger - manualTrigger
Config choices
Version 1

Block 3 - Loop Over Items

Type / Role
n8n-nodes-base.splitInBatches - splitInBatches
Config choices
Version 3

Block 4 - Replace Me

Type / Role
n8n-nodes-base.noOp - noOp
Config choices
Version 1

Block 5 - Hunter

Type / Role
n8n-nodes-base.hunter - hunter
Config choices
Version 1

Block 6 - Add Hunter Details (Contact)

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 7 - Wait

Type / Role
n8n-nodes-base.wait - wait
Config choices
Version 1.1

Block 8 - Sticky Note

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 9 - Sticky Note1

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 10 - Sticky Note2

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 11 - Send Email

Type / Role
n8n-nodes-base.emailSend - emailSend
Config choices
Version 2.1

3. Summary Table

Workflow HubSpot contact email validation with Hunter.io
Complexity intermediate
Nodes 11
Categories Lead Generation
Author Akhil Varma Gadiraju
Published 27 May 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/4416/4416.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Frequently asked questions

What does HubSpot contact email validation with Hunter.io do?

Workflow: HubSpot Contact Email Validation with Hunter.io Overall Goal This workflow retrieves contacts from HubSpot that have an email address but haven't yet had their email validated by Hunter. ...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Lead Generation use case.