> For the complete documentation index, see [llms.txt](https://docs.hockeystack.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hockeystack.com/account-intelligence/workflows/nodes/transformations/contact-enrichment.md).

# Contact Enrichment

The **Contact Enrichment Node** enhances your contact records with missing data — typically used to retrieve verified **email addresses** and other key contact attributes. If you've already discovered a person but are missing ways to reach them, this node fills in the gaps.

***

### When to Use It

Use the Contact Enrichment node when you want to:

* Find email addresses for contacts discovered or passed through earlier steps
* Complete missing fields before pushing to downstream systems like Outreach, Salesforce, or HubSpot

***

### Configuration Overview

Here’s how it works:

**Enrichment Mode**

Currently, the available enrichment mode is:

* **Email** – Finds the best available email address for each contact, prioritizing verified work emails where possible.

***

<figure><img src="https://318687664-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FedLASfWbQxGa0eYkwALS%2Fuploads%2Ft4G4bKJtBzaiHu4Krz5k%2FScreenshot%202025-04-18%20at%204.28.56%E2%80%AFPM.png?alt=media&amp;token=84671976-9598-4f1e-9f4b-7e0eb99a1d45" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.hockeystack.com/account-intelligence/workflows/nodes/transformations/contact-enrichment.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.