Enrich Person

Enrich a person using their first name, last name, and company domain, or simply their LinkedIn profile URL. You can also reverse lookup a person from their email address to find matching profile and contact data.

It runs as a waterfall — several providers are tried in sequence and the first one to return a result wins. You are charged once for the run, not once per provider tried.

Inputs

Every field is optional. Pass at least one identifier — the more you pass, the tighter the match.

Three ways to run it:

• Name + domain — first_name, last_name, and domain (or company_name) is the most common combination.
• LinkedIn URL alone — linkedin_url on its own is enough, and it is the most accurate anchor.
• Reverse lookup from email — pass email on its own to find the profile and contact data behind an address.

Outputs

Use cases

• Enrich a list of LinkedIn profiles. You scraped or exported a set of profile URLs and need the record behind each one — title, company, location, and contact details. Pass linkedin_url on its own; it is the strongest anchor and needs nothing else alongside it.
• Reverse lookup from an email address. An address from a form fill, a webinar list, or a shared inbox is enough on its own. Pass email and get back the matching profile and contact data — who they are, what they do, and where they work.
• Fill in a name-and-company list. A CSV of first names, last names, and company domains is the most common outbound starting point. Pass first_name, last_name, and domain together to resolve each row into a full person record.
• Backfill a CRM. Run the action over contacts that are missing a title, company, or LinkedIn URL. Enrich Person fills several fields in one run instead of chaining a separate action per field.
• Qualify inbound leads. Turn a raw signup email into seniority, department, and employer before the lead hits routing rules, so the right rep picks it up.
• Refresh stale records. Titles and employers go out of date fast. Re-running a contact returns the current role, which keeps personalisation from referencing a job they left a year ago.

Best practices

• Anchor on the strongest identifier you have. linkedin_url beats email, and email beats a name. When you have more than one, pass all of them — the extras cost nothing and are what stop a wrong match.
• Always send a company signal with a name. A first and last name on their own will match the wrong person more often than you would like. domain is the most precise company signal; company_name works when you do not have the domain.
• Prefer domain over company_name. Company names are ambiguous and inconsistently formatted across data sources; a domain is unique. Pass both when you have both.
• Use a LinkedIn URL alone when you have one. Do not pad the call with a guessed company or a partial name — a wrong extra identifier can push the match away from the right person rather than toward it.
• Deduplicate and suppress before you run. Filtering rows you already own costs nothing; enriching them costs 3 credits each.
• Spot-check the first few rows. Run a handful, confirm the matches look right, then let the rest of the list run. A wrong match still bills.
• Chain it, do not repeat it. If you only need a single field — just the work email, just the current title — a targeted action such as Find Work Email or Current Role is cheaper. Reach for Enrich Person when you need the broad record.
• Go deeper with LinkedIn. Enrich Person returns contact basics and current role. For full work history, education, and skills, run Enrich/Scrape LinkedIn Profile instead.

Related enrichments

Next steps

• Person Enrichment — where this action fits, and what to run before it
• Actions — adding, configuring, and auto-running an action column
• Credits — how usage is billed
• enrich_person — run the same enrichment from an AI client over MCP