> 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-discovery.md).
# Contact Discovery
The **Contact Discovery Node** automatically finds relevant people at each account in your workflow — based on the criteria you define. Instead of manually researching contacts or relying on static lists, this node pulls fresh, up-to-date profiles that match your target persona.
***
### When to Use It
Use this node when you want to:
* Discover net-new contacts at high-fit accounts
* Automate top-of-funnel lead generation
* Find the right person to enrich, qualify, or route into an outbound sequence
***
### Configuration Overview
{% hint style="info" %}
#### Important
It is required to have **Personas** before using the Contact Discovery node. You can configure this in **Settings > Account Intelligence > Personas.**
{% endhint %}
The Contact Discovery node discovers new contacts based on user configured **Personas** and job change signals.
> **Note:** Contact Discovery runs on a max of 2,000 accounts. For scheduled workflows, data is refreshed every 90 days.
***
---
# 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-discovery.md?ask=&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.
