Skip to main content
The LinkedIn Find People Enrich flow finds a LinkedIn profile from a person’s name and company information, then extracts profile and company data and enriches with verified emails and phone numbers. This flow is ideal when you have names and company context but not the profile URL.

​
Inputs

Each item in the inputs array can include:
FieldRequiredDescription
full_nameYes*Full name of the person
company_nameYes*Company name (use with full_name or domain)
domainYes*Company domain (e.g. acme.com; use with full_name or instead of company_name)
job_titleNoJob title (helps improve profile matching)
*Provide at least a way to identify the person and the company: e.g. full_name + company_name, or full_name + domain.

​
Flow Steps

The flow executes steps in the following order:
  1. Find profile URL (required): Finds the LinkedIn profile URL from the provided name and company/domain (and optional job title)
  2. Extract LinkedIn People (required): Extracts detailed information from the profile
  3. Extract company information (required): Extracts company data for the profile’s current company
  4. Full enrich (required): Enriches with contact information (emails and phone numbers). Credit costs: 2 credits for emails, 20 credits for phones, 22 credits for both.
This flow runs all steps in sequence. Results are delivered asynchronously; use a callback URL or poll the run status to get outputs.

​
Custom Data

Each item in the inputs array can include an optional custom_data object. The only valid key inside custom_data is meta. Use meta to attach a free-form object (e.g. your own IDs, tags, or context) that will be passed through and available in the flow output. Example: 
"inputs": [
  {
    ...
    "custom_data": {
      "meta": {
        "foo": "bar",
        "crm_id": 1234
      }
    }
  }
]
This feature will be improved and simplified soon without breaking changes.
Examples: 
curl --request POST \
  --url https://api.edges.run/v1/flows/linkedin-find-people-enrich/run/async \
  --header 'Content-Type: application/json' \
  --header 'X-API-Key: <your-api-key>' \
  --data '{
  "inputs": [
    {
      "full_name": "Jane Doe",
      "company_name": "Acme Inc",
      "job_title": "Head of Sales"
    }
  ],
  "identity_mode": "managed"
}'

curl --request POST \
  --url https://api.edges.run/v1/flows/linkedin-find-people-enrich/run/async \
  --header 'Content-Type: application/json' \
  --header 'X-API-Key: <your-api-key>' \
  --data '{
  "inputs": [
    {
      "full_name": "John Smith",
      "domain": "acme.com"
    }
  ],
  "identity_mode": "managed"
}'

curl --request POST \
  --url https://api.edges.run/v1/flows/linkedin-find-people-enrich/run/async \
  --header 'Content-Type: application/json' \
  --header 'X-API-Key: <your-api-key>' \
  --data '{
  "inputs": [
    {
      "full_name": "Jane Doe",
      "company_name": "Acme Inc"
    }
  ],
  "identity_mode": "managed",
  "callback": {
    "url": "https://your-app.com/webhook/flow-results",
    "headers": {
      "Authorization": "Bearer your-webhook-token"
    }
  }
}'
Instead of polling for results, you can use webhooks to receive automatic notifications when this flow completes. Learn more about webhook payloads and handling.