Skip to main content

​
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

Search People node configuration screenshot
1

Start a New Play

Click Start New Play, then choose Search People as your trigger.
2

Define Your Filters

Fill in at least one filter inside Person Details—e.g., keywords, domain, seniority, or location.
3

Build the Play

Add enrichment, scoring, or messaging nodes after the trigger.
4

Run the Play

Only people matching your filters will be pulled into the play.

​
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.
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.

​
🎯 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.
Search People output screenshot

​
🧾 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
Only the fields you select will be returned in the output.

​
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 CaseFilter Example
Outbound triggerkeywords = buyer, marketing AND region = US
Region-based alertslocation = EMEA
Persona-based scoringseniority = VP AND company_domain = nrev.ai

​
✨ Pro Tips

Use this as a starting point, then follow up with Enrich Person, AI Scorer, or Slack Alert nodes to automate your GTM motion.
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.
Select only the fields you need in the Enrichment Fields dropdown to keep your play clean and fast.

​
⚠️ Important Considerations

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.

​
🛠 Troubleshooting & Gotchas

SymptomLikely CauseQuick Fix
Result not as expectedFilters are too narrowBroaden your filters or check input values
Unexpected credit usageHigh Limit valueLower the limit to reduce page count
Missing enrichment fieldsField not selected in configUpdate the node and include that field

​
📝 FAQ

Yes — you can use Search People mid-play. You can even pass in values like company_domain or location using inputs from earlier nodes.
Yes — one is technically enough. But we recommend using 2–3 fields to sharpen your targeting and cut down on noisy results.
Just select All from the dropdown when configuring the node. You’ll get every available person info.

​
💰 Pricing

Every page fetched consumes 5 credits.
Example: A limit of 500 results = 5 pages × 5 credits = 25 total credits

Drop Search People at the top of your play to auto-capture high-fit contacts—and put your GTM on autopilot. 🚦