Skip to main content
MindStudio
Pricing
Blog About
My Workspace
CRM & Enrichment

[Hunter.io] Enrich Person

This block fits into workflows that need to qualify or enrich contact records before taking further action — for example, routing leads based on seniority, personalizing outreach based on job title, or appending company context to a CRM entry.

Look up professional info by email address

This block fits into workflows that need to qualify or enrich contact records before taking further action — for example, routing leads based on seniority, personalizing outreach based on job title, or appending company context to a CRM entry. Because it returns a JSON object even when a person is not found rather than throwing an error, it can be used in conditional branches that handle both matched and unmatched lookups gracefully.

What you can build

Real-world workflows powered by the [Hunter.io] Enrich Person block.

Lead Qualification Routing

Enrich an inbound lead's email to retrieve their seniority and department, then route them through different workflow branches based on role.

CRM Record Enrichment

Automatically append job title, LinkedIn URL, and company details to a contact record when a new email is added to a CRM system.

Personalized Email Outreach

Look up a prospect's position and company name before generating a personalized outreach message tailored to their role.

Sales Intelligence Gathering

Retrieve company industry and domain alongside contact details to give sales teams context before a call or meeting.

Social Profile Discovery

Pull LinkedIn and Twitter profile URLs associated with an email address to build a more complete contact profile.

Contact Deduplication Check

Use enriched name and company data returned from a lookup to identify and merge duplicate contact entries in a workflow.

Ready to add [Hunter.io] Enrich Person to your workflow?

Get Started Free

Common questions about [Hunter.io] Enrich Person

What is the required input for this block?

The only required parameter is an email address string. There is also an optional destination variable field where you can specify the variable name that will store the returned JSON result.

What data does this block return?

The block returns a JSON object containing first_name, last_name, email, position, seniority, department, linkedin_url, twitter, phone_number, and a nested company object with name, domain, and industry. Fields without available data are returned as null.

What happens if the email address is not found in Hunter.io?

If the person is not found, the block returns an object with an error message rather than throwing an error. This allows workflows to handle unmatched lookups using conditional logic without interrupting execution.

What kinds of workflows is this block commonly used in?

This block is commonly used in lead enrichment, CRM automation, and outreach personalization workflows — any scenario where a contact's email is known but additional professional context such as job title, seniority, or company information is needed before taking a next step.

Where is the enriched data stored after the block runs?

The result is stored as a JSON object in the variable specified by the optional destinationVar field. That variable can then be referenced by subsequent blocks in the workflow.

Add [Hunter.io] Enrich Person to your workflow

Build powerful AI workflows with drag-and-drop blocks. No coding required.