ACTION_ID: person_enrich_using_people_data_labs
NAME: People Data Labs: Person Enrich
CATEGORY: scrape
CREDITS: 5

Enrich a person's profile with data sourced from People Data Labs
(PDL). Given any combination of identifying signals (email, social
media profile URL, or person_name + company_name), the action returns
a broad set of person attributes, including:

  - LinkedIn URL
  - Facebook URL
  - Twitter URL
  - Multiple person names / aliases
  - Likely work emails (an array of candidates, not a single
    verified email)
  - Person emails (verified)
  - Phone numbers
  - Location data (street addresses, locations)
  - Skills, education, experience, interests, industries
  - Birth date (and a fuzzy variant)
  - PDL confidence score

Use it as a fallback or breadth-focused enrichment source when
Apollo or other paths miss a prospect, or when you specifically need
PDL's wider social-URL coverage or the multi-candidate likely-email
array.

INDEX:
  1. Inputs
  2. Outputs
  3. How to configure
  4. Key notes
  5. Where it fits in a workflow
  6. When to use
  7. When not to use

================================================================================
1. INPUTS
================================================================================

email (type: email, optional) — Email
  Email of the person you are looking for.

social_media_profile_url (type: url, optional) — Social Media Profile URL
  Social media profile URL — LinkedIn, Twitter, Facebook, etc.

person_name (type: string, optional) — Person Name
  Full name of the person. Can be passed as a single string, or
  composed inline from two upstream variables joined with a space —
  e.g. "{{input.first_name}} {{input.last_name}}". Must be used in
  conjunction with Company Name if Email and Social Profile URL are
  not provided.

company_name (type: string, optional) — Company Name
  Must be used in conjunction with Person Name if Email and
  Social Profile URL are not provided.

================================================================================
2. OUTPUTS
================================================================================

id (type: string) — ID
  PDL's internal identifier for the person.

person_names (type: raw_array) — Person Names
  Array of name variants / aliases PDL has on file for this person.

person_emails (type: string) — Person Emails
  Verified email(s) for the person.

person_linkedin_url (type: string) — Person LinkedIn URL
  LinkedIn profile URL of the person.

person_facebook_url (type: string) — Person Facebook URL
  Facebook profile URL of the person.

person_twitter_url (type: raw_array) — Person Twitter URL
  Twitter handle(s) / URL(s) for the person (returned as an array).

skills (type: raw_array) — Skills
  Skills associated with the person.

primary (type: raw_array) — Primary
  PDL "primary" record for the person — the canonical identity
  block that PDL considers the best match.

person_social_profiles (type: raw_array) — Person Social Profiles
  All social profiles PDL has linked to this person, beyond just
  LinkedIn / Facebook / Twitter.

education (type: raw_array) — Education
  Education history.

interests (type: raw_array) — Interests
  Interests / topics associated with the person.

locations (type: raw_array) — Locations
  Locations associated with the person.

birth_date (type: string) — Birth Date
  Birth date in ISO format.

experience (type: raw_array) — Experience
  Work history.

person_industries (type: raw_array) — Person Industries
  Industries associated with the person.

confidence_score (type: number) — Confidence Score
  PDL's match confidence score for this person.

person_gmail_domains (type: raw_array) — Person Gmail Domains
  Gmail / Google domains associated with the person.

person_phone_numbers (type: raw_array) — Person Phone Numbers
  Array of phone numbers PDL has on file. Use the dedicated phone
  waterfall (personal_phone_number_by_linkedin_url_waterfall) for
  primary phone enrichment — see KEY NOTES.

birth_date_fuzzy (type: string) — Birth Date Fuzzy
  Approximate / fuzzy birth date (year-only or partial).

street_addresses (type: raw_array) — Street Addresses
  Street addresses associated with the person.

likely_work_emails (type: raw_array) — Likely Work Emails
  Array of likely work email candidates. Not verified — use this
  when you want multiple candidates rather than a single verified
  address (use person_work_email_waterfall for that).

================================================================================
3. HOW TO CONFIGURE
================================================================================

Configure Action body:

{
  "inputs": {
    "person_name": "{{input.first_name}} {{input.last_name}}",
    "company_name": "{{input.company_name}}",
    "social_media_profile_url": "{{input.linkedin_url}}"
  }
}

Pass at least one identifying signal: `email`, `social_media_profile_url`,
or `person_name` + `company_name` together.

================================================================================
4. KEY NOTES
================================================================================

- PDL is the broader provider for social-URL coverage (Facebook,
  Twitter, multiple LinkedIn aliases) and the multi-candidate
  `likely_work_emails` array. For verified email or phone enrichment
  alone, use `person_work_email_waterfall` /
  `personal_phone_number_by_linkedin_url_waterfall` — those produce
  a single high-confidence value rather than a candidate list.
- `confidence_score` is PDL's match likelihood. Filter on it with
  `format_data_using_js_expression` if you need a confidence floor
  before downstream steps.

================================================================================
5. WHERE IT FITS IN A WORKFLOW
================================================================================

Pattern: linkedin_url -> person_enrich_using_people_data_labs ->
person_work_email_verification_by_zerobounce (or another verifier) ->
outreach.

================================================================================
6. WHEN TO USE
================================================================================

Use person_enrich_using_people_data_labs as a fallback or
breadth-focused enrichment source. Particularly useful when:

  - You have a person's first_name + last_name + company_name and
    need to resolve their LinkedIn URL — PDL covers many profiles
    that other providers miss.
  - You need a Facebook URL for a person — PDL has broader social
    coverage than Apollo or LinkedIn-scraping actions.
  - You want multiple email candidates — PDL returns a Likely Work
    Emails array, useful when one verified email isn't enough and
    you want to test/permutate addresses.

Not the right fit when:

  - You only need a phone number — use the dedicated
    personal_phone_number_by_linkedin_url_waterfall instead. PDL's
    phone coverage is shallower and not the canonical phone path.
  - You only need a single verified work email — use
    person_work_email_waterfall. Reach for PDL only when you need
    the full multi-candidate Likely Work Emails array.

================================================================================
7. WHEN NOT TO USE
================================================================================

Need only a work email
  -> person_work_email_waterfall
     (https://floqer.com/docs/action-detail/person_work_email_waterfall.txt)

Need Apollo person data
  -> person_enrich_using_apollo
     (https://floqer.com/docs/action-detail/person_enrich_using_apollo.txt)

================================================================================

This file is maintained manually. Last updated: 2026-04-30.
Full interactive reference: https://floqer.com/docs/reference
Action catalog: https://floqer.com/docs/action-catalog.txt