> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nrev.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Search People

> Trigger your play by pulling in people who match flexible filters—perfect for lead routing, alerts, or targeted enrichment.

## What It Does

* **Trigger or Filter:** Use this to kick off plays or narrow people mid-play.
* **Flexible Matching:** Search by role, domain, location, or seniority—using static inputs or dynamic ones passed from earlier in the play.
* **Enriched Output:** Returns the exact person fields you care about—ready for scoring, routing, or alerts.
* **Built for GTM:** Perfect for finding decision-makers, targeting ICPs, or launching smart outreach.

***

## 🏁 Getting Started

<Frame>
  <img src="https://mintcdn.com/nurturev/XbOQSoFzT8ExEzUj/images/Search%20People%20node%20configuration%20screenshot.png?fit=max&auto=format&n=XbOQSoFzT8ExEzUj&q=85&s=5a84224e05e0d5265abcb5a72790385f" alt="Search People node configuration screenshot" style={{ borderRadius: '0.5rem', width: '100%', margin: '1.5rem 0' }} width="1178" height="1664" data-path="images/Search People node configuration screenshot.png" />
</Frame>

<Steps>
  <Step title="Start a New Play">
    Click **Start New Play**, then choose **Search People** as your trigger.
  </Step>

  <Step title="Define Your Filters">
    Fill in at least one filter inside **Person Details**—e.g., keywords, domain, seniority, or location.
  </Step>

  <Step title="Build the Play">
    Add enrichment, scoring, or messaging nodes after the trigger.
  </Step>

  <Step title="Run the Play">
    Only people matching your filters will be pulled into the play.
  </Step>
</Steps>

***

## Inputs

### 🛠️ Required Fields

* **Person Details (✅)**\
  A group of filters that define which people to search for—includes **Keywords**, **Company Domain**, **Seniority**, **Location**, **Person Titles**, **Person Location**, and **Include Similar Titles**.\
  *Why it matters:* This node won’t run unless you provide **at least one** of these fields.

* **Limit (✅)**\
  Sets the maximum number of people to return. Default: `100`. Max: `10,000`.\
  *Why it matters:* Controls result volume and credit usage.

* **Enrichment Fields (✅)**\
  Required dropdown. Choose one or more fields to include in your output.\
  *Why it matters:* Defines exactly which person attributes you want enriched.

<Note>
  When used **mid-play**, **Keywords**, **Company Domain**, and **Location** can accept dynamic values from upstream columns.\
  Use `@` or the **Insert Input** button to select a column from a previous node.
</Note>

### 🎯 Optional Sub-Fields

* **Keywords (⚪️)**\
  Comma-separated terms like `marketing`, `buyer`, or `revops`.\
  *Why you’d use it:* Find people by title, role, or skill focus.

* **Company Domain (⚪️)**\
  Comma-separated list of domains (e.g., `nrev.ai`, `globex.io`).\
  *Why you’d use it:* Limit results to people from specific companies.

* **Seniority (⚪️)**\
  Dropdown selector (e.g., `Manager`, `VP`, `C-Level`).\
  *Why you’d use it:* Target senior roles only.

* **Location (⚪️)**\
  Freeform location input (e.g., `San Francisco`, `Europe`).\
  *Why you’d use it:* Useful for geo-based routing or regional filters.

* **Person Titles (⚪️)**\
  One or more specific titles to target (e.g., `Head of Sales`, `VP Engineering`)\
  *Why you’d use it:* Directly match job titles instead of just role keywords.

* **Include Similar Titles (⚪️)**\
  Boolean toggle to expand fuzzy title matches (e.g., `Head of Growth` also returns `Growth Lead`)\
  *Why you’d use it:* Widen your net slightly when searching by specific titles.

* **Person Location (⚪️)**\
  Where the person physically lives (distinct from work location)\
  *Why you’d use it:* Useful for WFH or territory-based outreach.

***

## Output

* Only matching rows from your filter criteria will move forward.
* All selected row data is passed to downstream nodes.

### 🧾 Available Enrichment Fields

**🧍 Basic Info**

* `first_name`
* `last_name`
* `name`
* `photo_url`

**💼 Professional Details**

* `title`
* `headline`
* `seniority`
* `departments`
* `subdepartments`
* `functions`

**🔗 Social Profiles**

* `linkedin_url`
* `twitter_url`
* `github_url`
* `facebook_url`

**📍 Location**

* `state`
* `city`
* `country`

**📘 Employment History**

* `employment_history`

**🏢 Company Info**

* `organization_id`
* `org.name`
* `org.primary_domain`
* `org.linkedin_url`
* `org.logo_url`
* `org.website_url`
* `org.founded_year`

<Note>
  Only the fields you select will be returned in the output.
</Note>

***

## How It Works

1. Add **Search People** as a trigger or mid-play filter node
2. Provide one or more filters — either manually or by selecting dynamic column inputs (e.g., company domain from a CRM export)
3. Set a **Limit** and choose your **Enrichment Fields**
4. The platform queries our source based on those filters
5. Matching people are returned and passed to the next node

***

## 🚀 Example Use Cases & Prompts

| Use Case              | Filter Example                                  |
| --------------------- | ----------------------------------------------- |
| Outbound trigger      | `keywords = buyer, marketing` AND `region = US` |
| Region-based alerts   | `location = EMEA`                               |
| Persona-based scoring | `seniority = VP` AND `company_domain = nrev.ai` |

***

## ✨ Pro Tips

<Tip>
  Use this as a starting point, then follow up with **Enrich Person**, **AI Scorer**, or **Slack Alert** nodes to automate your GTM motion.
</Tip>

<Tip>
  Dynamic values from previous nodes can help you create more targeted searches. For example, use `@company_domain` to pull in the domain from an earlier step.
</Tip>

<Tip>
  Select only the fields you need in the **Enrichment Fields** dropdown to keep your play clean and fast.
</Tip>

***

## ⚠️ Important Considerations

<Warning>
  The default **Limit** is `100`. If you want to fetch more people per item (e.g., per company or keyword), update the limit accordingly—up to a max of `10,000`.
</Warning>

***

## 🛠 Troubleshooting & Gotchas

| Symptom                   | Likely Cause                 | Quick Fix                                  |
| ------------------------- | ---------------------------- | ------------------------------------------ |
| Result not as expected    | Filters are too narrow       | Broaden your filters or check input values |
| Unexpected credit usage   | High Limit value             | Lower the limit to reduce page count       |
| Missing enrichment fields | Field not selected in config | Update the node and include that field     |

***

## 📝 FAQ

<AccordionGroup>
  <Accordion title="Can I use this mid-play to search people?">
    Yes — you can use **Search People** mid-play. You can even pass in values like `company_domain` or `location` using inputs from earlier nodes.
  </Accordion>

  <Accordion title="Is just one Person Details field enough?">
    Yes — one is technically enough. But we recommend using 2–3 fields to sharpen your targeting and cut down on noisy results.
  </Accordion>

  <Accordion title="What if I want all enrichment fields?">
    Just select **All** from the dropdown when configuring the node. You’ll get every available person info.
  </Accordion>
</AccordionGroup>

***

## 💰 Pricing

> Every page fetched consumes **5 credits**.

<Note>
  *Example:* A limit of 500 results = 5 pages × 5 credits = **25 total credits**
</Note>

***

<p style={{ fontSize: '1rem', fontWeight: 'bold', marginTop: '1.5rem' }}>
  Drop Search People at the top of your play to auto-capture high-fit contacts—and put your GTM on autopilot. 🚦
</p>