LinkedIn Network Connections Scraper with Current Job Location

🔗 LinkedIn Network Connections Scraper With Current Job & Location

Export every profile in your personal LinkedIn network into a clean, structured table — first/last name, headline, profile photo, vanity URL, connection date — and optionally enrich each connection with their current job title, current company and location, pulled from their public profile page. Built for founders, sales pros, recruiters, and RevOps teams who want to turn a raw connections list into a filterable, exportable lead list. 🚀

⚖️ This Actor only reads your own network connections, using your own authenticated session (a LinkedIn li_at cookie). Enrichment reads only public profile pages (no login used for that step). You are responsible for complying with LinkedIn's Terms of Service.

Keywords: LinkedIn network scraper, LinkedIn connections scraper, export LinkedIn connections, LinkedIn contacts to CSV, LinkedIn lead generation, LinkedIn current job title scraper, LinkedIn employer scraper, LinkedIn connections by company, LinkedIn connections by location, LinkedIn network export API, LinkedIn CRM export, LinkedIn li_at cookie scraper.

---

✨ Why Choose This Actor?

• 🎯 One row per connection — sortable, filterable, exportable to JSON / CSV / Excel.
• 🧩 Current job & company enrichment — turns a static headline into a structured current_job_title + current_company + location, so you can actually segment your network.
• 🎯 Job title / company / location filters — keep only the connections that match, e.g. every "Founder" at a company containing "Ventures" based in "London".
• 💾 Live saving — every connection is saved the instant it's found; a partial run is never wasted.
• 🌐 Self-healing network layer — starts direct, escalates to Datacenter → Residential proxies only if LinkedIn pushes back.
• 📅 Date monitoring — capture only today's new connections, or everything up to a chosen date.
• 🧘 Honest coverage — enrichment is best-effort against public profiles only; unreachable/private profiles are left null, never faked.

---

🔑 Key Features

Feature	Description
👤 Profile details	First name, last name, headline
🧩 Current job & company	current_job_title, current_company, current_company_url, current_company_location
📍 Location	Connection's city/region/country from their public profile
📈 Follower count	LinkedIn's own displayed follower count
📚 Full work history & education	Optional work_history[] / schools[] arrays
🎯 Keyword filters	Filter by job title, company, and/or location
🗓️ Connection date	Both a pretty label and an ISO date
🖼️ Profile photo	Highest-resolution available image URL
📄 Pagination	Walks your entire network, 40 per page
🛡️ Proxy fallback	direct → datacenter → residential, sticky

---

📥 Input

Field	Type	Description
liAtCookie 🍪	string	Required. Your LinkedIn li_at session cookie. Masked in the UI, never logged.
starting_page 📄	integer	Page to start from (40 connections/page). Default 1.
max_connections 🔢	integer	Stop after this many connections. 0 = unlimited.
waiting_time ⏱️	number	Base delay (seconds) between pages/enrichment fetches; randomized up to ×2. Default 2.
date_limit_today 📅	boolean	Capture only connections added today.
date_limit_str 🗓️	string	Stop once connections are older than this YYYY-MM-DD date.
enrichProfiles 🧩	boolean	Fetch each connection's public profile for current job/company/location. Default true.
includeWorkHistory 📚	boolean	Include full work_history[] / schools[] arrays. Default false.
jobTitleKeywords 🎯	array	Keep only connections whose current job title contains one of these words.
companyKeywords 🏢	array	Keep only connections whose current company contains one of these words.
locationKeywords 📍	array	Keep only connections whose location contains one of these words.
proxyConfiguration 🌐	object	Proxy / residential country settings.

Example input

{
  "liAtCookie": "AQEDA...your-li_at-cookie...",
  "enrichProfiles": true,
  "jobTitleKeywords": ["founder", "recruiter"],
  "companyKeywords": [],
  "locationKeywords": ["London"],
  "waiting_time": 2,
  "proxyConfiguration": { "useApifyProxy": true }
}

🍪 How to get your li_at cookie

1. 🌐 Log in to linkedin.com in your browser.
2. 🛠️ Open DevTools (F12) → Application → Cookies → https://www.linkedin.com.
3. 📋 Copy the Value of the cookie named li_at.
4. 📌 Paste it into the liAtCookie field. ✅

---

📤 Output

Each item is one connection:

{
  "vanityName": "jane-example",
  "firstName": "Jane",
  "lastName": "Example",
  "componentRef": "auto-component-...",
  "connection_date": "Connected on May 21, 2026",
  "formated_connection_date": "2026-05-21",
  "picture": "https://media.licdn.com/dms/image/.../photo.jpg",
  "headline": "Senior Product Manager at Acme",
  "url": "https://www.linkedin.com/in/jane-example",
  "profile_enriched": true,
  "enrichment_source": "public_page",
  "current_job_title": "Senior Product Manager",
  "current_company": "Acme Corp",
  "current_company_url": "https://www.linkedin.com/company/acme",
  "current_company_location": "London",
  "location": "London, England, United Kingdom",
  "country_code": "GB",
  "profile_about": "Building developer tools.",
  "follower_count": 4200,
  "matched_filters": ["jobTitle", "location"]
}

Field	Description
vanityName	Public profile slug
firstName / lastName	Connection's name
connection_date	Human-friendly "Connected on …" label
formated_connection_date	ISO YYYY-MM-DD date
picture	Best available profile photo URL
headline	Their LinkedIn headline
url	Direct profile link
profile_enriched	true if the public-profile fetch succeeded
enrichment_source	"public_page" when enriched, else null
current_job_title	Current job title, from their public profile (null if unavailable)
current_company / current_company_url / current_company_location	Current employer details
location / country_code	Connection's location
profile_about	Their profile "About" text, if present
follower_count	LinkedIn's own displayed follower count
work_history[] / schools[]	Full history, only when includeWorkHistory is on
matched_filters	Which filter dimension(s) this row matched (empty array if no filters set)

Coverage note: enrichment relies on the connection's profile being publicly viewable. In practice a meaningful share of profiles (roughly a third, in line with general public-page reachability) won't enrich — those rows keep profile_enriched: false and null enrichment fields rather than a guessed value.

---

🚀 How to Use (Apify Console)

1. Log in at console.apify.com → Actors.
2. Open LinkedIn Network Scraper With Current Job & Location.
3. Paste your li_at cookie, set your filters, and tune the options.
4. Click Start. ▶️
5. Watch the real-time log fill up with captured, enriched connections. 👀
6. Open the Output tab when the run finishes.
7. Export to JSON / CSV / XLSX. 📦

---

💡 Best Use Cases

• 🧲 Lead generation — filter your network down to founders/recruiters/decision-makers at target companies.
• 📈 Network growth tracking — run daily with date_limit_today to log new connections and their current role.
• 🧑‍💼 Recruiting — find connections currently working in a target function or location.
• 🗂️ Personal CRM backup — a structured archive of who you know, where they work, and where they're based.

---

💳 Pricing

This Actor uses the Pay-Per-Event model. You're charged per connection saved to the dataset, plus standard Apify platform usage.

---

❓ FAQ

Is my cookie safe? Yes — li_at is marked secret, never written to logs, and only used to authenticate your own requests. The enrichment step uses no cookie at all — it reads public profile pages.

Why is current_job_title empty for some rows? Their profile isn't public, or LinkedIn didn't serve the structured profile data for that request. It's left null — never guessed.

Why did it stop early? You hit a date limit or max-connections cap, reached the end of your network, or your li_at cookie expired.

Do the filters need enrichment on? Yes — jobTitleKeywords/companyKeywords/locationKeywords filter against enriched fields, so they're ignored (with a log warning) if enrichProfiles is off.

Will this get my account flagged? The Actor uses polite, randomized delays, but you are responsible for respecting LinkedIn's Terms of Service and your local laws.

---

🛟 Support & Feedback

Found a bug or want a new field in the output? Open an issue on the Actor's Issues tab.