Pricing

Rating

Developer

Actor stats

Categories

Share

🔗 LinkedIn Mass People Profile Finder

Bulk-resolve LinkedIn profile URLs from free-text queries — in seconds, at scale.

Provide a list of search queries (e.g. "Michael Dell Dell Technologies CEO") and the actor returns the first matching public LinkedIn profile URL for each. No LinkedIn login needed — results come from public search engines.

✨ Why Choose This Actor?

• ⚡ Bulk lookup — process hundreds of names in one run, in parallel
• 🌐 Smart proxy ladder — starts direct, auto-escalates to datacenter → residential only when blocked
• 🛡️ Anti-block resilient — randomized user agents, exponential backoff, sticky escalation
• 💾 Live results — every match streams to the dataset the moment it's found, so partial output is always preserved
• 🔁 Dual-engine fallback — DuckDuckGo primary, Bing fallback
• 🎯 Clean output — canonical https://www.linkedin.com/in/<slug> for every hit

🔑 Key Features

📥 Input

{
"queries":[
"\"Michael Dell\" \"Dell Technologies\" CEO",
"\"Chuck Robbins\" CISCO CEO"
],
"workers":3,
"baseDelay":0.5,
"retries":3,
"timeout":15,
"proxyConfiguration":{"useApifyProxy":false}
}

📤 Output

Each item in the dataset:

{
"linkedin":"https://www.linkedin.com/in/mdell",
"input":"\"Michael Dell\" \"Dell Technologies\" CEO"
}

For failed lookups:

{
"linkedin":null,
"input":"some unfindable query",
"error":"bing: no result"
}

🚀 How to Use (Apify Console)

1. Log in at https://console.apify.com → Actors.
2. Open LinkedIn Mass People Profile Finder.
3. Paste your queries — one per line — in the Search Queries field.
4. (Optional) Tune workers / delay / retries.
5. Click ▶ Start.
6. Watch logs in real time — found profiles appear immediately.
7. Open the Output tab when the run completes; export to JSON / CSV / XLSX.

🤖 Use via API

Run synchronously and get results in one call:

curl-X POST \
"https://api.apify.com/v2/acts/<ACTOR_ID>/run-sync-get-dataset-items?token=$APIFY_TOKEN"\
-H"Content-Type: application/json"\
-d'{
 "queries": [
 "\"Michael Dell\" \"Dell Technologies\" CEO",
 "\"Chuck Robbins\" CISCO CEO"
 ]
 }'

Or asynchronously:

curl-X POST \
"https://api.apify.com/v2/acts/<ACTOR_ID>/runs?token=$APIFY_TOKEN"\
-H"Content-Type: application/json"\
-d'{"queries":["Satya Nadella Microsoft CEO"]}'

🌐 Proxy Strategy

The actor uses a sticky tiered fallback:

1. 🟢 Direct(no proxy) ← start here
2. 🟡 Apify Datacenter Proxy ← on first block
3. 🔴 Apify Residential Proxy ← if datacenter blocked too(3 retries)

Once the actor escalates to a higher tier, it stays there for the rest of the run — no flapping. Each escalation is clearly logged so you can see exactly when and why it happened.

🎯 Best Use Cases

• 🧑‍💼 Sales & lead enrichment — turn a CSV of names + companies into LinkedIn URLs
• 📊 Market research — find executive profiles for company analysis
• 🤝 Recruiting — bulk-resolve candidate profiles from spreadsheets
• 🔬 Data enrichment pipelines — feed CRM rows with normalized LinkedIn URLs

💰 Pricing (Pay-Per-Event)

You only pay for profiles we find — failed lookups still appear in the dataset for transparency but do not bill the result-item event.

❓ Frequently Asked Questions

Q: Do I need a LinkedIn account or cookie? No. The actor only queries public search engines.

Q: Why is the output URL different from what's on Google? We canonicalize every URL to https://www.linkedin.com/in/<slug> regardless of the country subdomain (e.g. uk.linkedin.com/in/…) for easier downstream matching.

Q: What if a query has multiple matching profiles? We return the first result. Make queries as specific as possible (name + company + title) for accuracy.

Q: Will I get rate-limited? Possible if you push workers too high. The actor handles this gracefully — it slows down, switches engines, and escalates to a paid proxy tier automatically. Default workers=3 is safe.

Q: Is this legal? Yes — we only query publicly indexed search results. You are responsible for downstream compliance with LinkedIn's ToS, GDPR/CCPA, and any applicable anti-spam laws.

⚖️ Cautions / Legal

• Data is collected only from publicly available sources (search engine result pages).
• Do not scrape private accounts or content behind authentication.
• The end user is responsible for legal compliance (GDPR, CCPA, anti-spam laws, target site ToS).
• Be a good citizen — keep concurrency moderate.

💬 Support & Feedback

Issues, feature requests, or just want to chat? Open an issue or contact the maintainer through your Apify Console messages.