HUNTER n8n INTEGRATION: AUTOMATE HUNTER WITH N8N

The Email Finder action is your go-to operation for discovering individual email addresses when you know someone's name and their company domain. This is particularly powerful for targeted outreach where you've identified specific decision-makers but need their direct contact information.

Key parameters:

• Domain: This text field is required and accepts the company domain you want to search (e.g., "company.com"). Hunter will use this as the base for finding the email pattern.
• First Name: An optional text field where you can specify the person's first name to narrow down the search results to a specific individual.
• Last Name: Also optional, this text field accepts the person's last name, which combined with the first name significantly improves accuracy.

Typical use cases:

• Automatically find emails for LinkedIn leads imported into your CRM
• Enrich a list of conference attendees with their work emails
• Build targeted ABM lists by finding specific roles at target accounts
• Complete partial contact records in your database

When to use it: Choose Email Finder when you have specific individuals in mind—you know their name and company, but not their email. It's ideal for quality over quantity approaches in account-based selling.

The Domain Search action takes a different approach: instead of finding one specific person, it retrieves all available email addresses associated with a given domain. This is your bulk prospecting powerhouse for mapping out entire organizations.

Key parameters:

• Domain: A required text field specifying the company domain to search (e.g., "targetcompany.com").
• Only Emails: This toggle switch, when enabled, filters results to return only the email addresses without additional metadata. Default is off.
• Return All: A toggle that determines whether to fetch all available results or respect the limit parameter. Default is off.
• Limit: A numeric field that caps the number of results returned, defaulting to 100. Useful for controlling API credit consumption.
• Filters: An expandable section allowing you to add custom filters to narrow results by department, seniority, or other criteria.

Typical use cases:

• Map all contacts at a target account before launching an ABM campaign
• Build industry-specific prospect lists by searching multiple domains
• Identify key stakeholders across departments at enterprise accounts
• Feed lead nurturing workflows with fresh contacts from target companies

When to use it: Domain Search shines when you're prospecting at the company level rather than the individual level. Perfect for discovering all reachable contacts before deciding who to prioritize in your outreach.

The Email Verifier action checks whether an email address is valid and deliverable. This is your quality control step—essential before any email campaign to protect your sender reputation and maximize deliverability.

Key parameters:

• Email: A required text field where you enter the email address to verify (format: name@domain.com). The action will return the verification status and confidence score.

Typical use cases:

• Validate leads before adding them to your email sequences
• Clean existing contact databases by verifying outdated addresses
• Verify emails collected from web forms before CRM entry
• Run batch verification on imported lists before campaigns

When to use it: Always verify before you send. Whether you're working with freshly found emails or aging contact lists, the Email Verifier ensures you're only reaching out to valid addresses—protecting your domain reputation and improving campaign performance. For comprehensive email deliverability strategies, consider exploring email deliverability best practices.