ACTION_ID: enrich_person_linkedin_profile
NAME: Scrape Person's LinkedIn Profile
CATEGORY: scrape
CREDITS: 0.2

Scrape a person's LinkedIn profile for information.

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
================================================================================

linkedin_url (type: url, required)
  LinkedIn URL of the prospect to scrape. Must be a person profile
  URL (i.e. contains /in/) — company URLs (/company/...) and other
  LinkedIn surfaces will not work.

  Both ID styles are accepted:
    - Flagship / public vanity:
        https://www.linkedin.com/in/gabbyokunz9
    - Sales Navigator opaque ID:
        https://www.linkedin.com/in/ACoAAEYKKBIBsAxhZxJ0KR832fW7MeAnhp3G3oI

  The http(s):// protocol and the www. subdomain are both optional.
  All of these are valid forms:
    - https://www.linkedin.com/in/<id>
    - http://www.linkedin.com/in/<id>
    - www.linkedin.com/in/<id>
    - linkedin.com/in/<id>

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

first_name (type: string) — First Name.
last_name (type: string) — Last Name.
person_linkedin_title (type: string) — Person LinkedIn Title. This is what LinkedIn
  surfaces as the user's headline (the free-text tagline below their
  name), not their job title. For the actual current job title, see
  the `person_current_job_title` field below.
person_linkedin_summary (type: string) — Person LinkedIn Summary.
person_linkedin_connections (type: number) — Person LinkedIn Connections.
person_linkedin_followers (type: number) — Person LinkedIn Followers.
country (type: string) — Country.
city (type: string) — City.
state (type: string) — State.
skills (type: raw_array) — Skills.
experiences (type: raw_array) — Work history. Each item represents a
  stint at one company and contains:
    - company: object with id, name, logo, url, domain, profileType
    - date: { start, end } ISO timestamps for the overall stint
            (end may be null for a current role)
    - profilePositions: array of position objects within that company,
        each with company, description, title, employmentType, location,
        and a per-position { date.start, date.end }. Multiple entries
        appear when the person changed roles inside the same company;
        otherwise there's one entry mirroring the parent stint.
  Treat as nested JSON — pass to the next action as-is, or extract
  specific fields with format_data_using_js_expression.
education (type: raw_array) — Education.
accomplishments (type: raw_array) — Accomplishments.
volunteer_work (type: raw_array) — Volunteer Work.
certifications (type: raw_array) — Certifications.
birth_date (type: string) — Birth Date (ISO format).
person_linkedin_profile_picture (type: url) — Person LinkedIn Profile Picture.
person_linkedin_url (type: url) — Person LinkedIn URL.
person_current_job_title (type: string) — Person Current Job Title.
current_company_name (type: string) — Current Company Name.
current_company_linkedin_url (type: url) — Current Company LinkedIn URL.
current_company_domain (type: string) — Current Company Domain.

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

Configure Action body:

{
  "inputs": {
    "linkedin_url": "{{input.linkedin_url}}"
  }
}

Pass the prospect's LinkedIn URL as `linkedin_url`.

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

- Sales Nav -> flagship URL conversion. This action accepts either
  the Sales Navigator opaque-ID form (linkedin.com/in/ACoAA...) or
  the flagship vanity form (linkedin.com/in/<handle>) on input, but
  the linkedin_url output is always the flagship form. That makes
  this action useful as a pre-step for downstream actions that
  require a flagship URL — many phone-number enrichment providers,
  for example, only accept flagship URLs and will reject Sales Nav
  IDs. Run this action first on a Sales Nav URL, then pipe the
  linkedin_url output into the enrichment step.

- current_company_domain is not always populated. Profiles where the
  current company hasn't been resolved to a verified entity (or
  where the person doesn't have a current role) will return an empty
  current_company_domain. If the downstream action is
  person_work_email_waterfall — which requires a company domain — you'll
  need to resolve the domain another way before that step. Common
  fallbacks: scrape the domain off current_company_linkedin_url
  via enrich_company_linkedin_profile, or use a separate
  domain-finder action keyed off current_company. Don't assume the
  domain is always there.

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

Pattern: linkedin_url -> enrich_person_linkedin_profile ->
person_work_email_waterfall -> outreach.

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

Use enrich_person_linkedin_profile to pull a person's full LinkedIn
profile.

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

Need company page data, not a person
  -> enrich_company_linkedin_profile
     (https://floqer.com/docs/action-detail/enrich_company_linkedin_profile.txt)

Need recent posts from this person
  -> get_company_or_person_linkedin_posts
     (https://floqer.com/docs/action-detail/get_company_or_person_linkedin_posts.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