LinkedIn Multi-Mode Scraper

Overview

This actor scrapes data from LinkedIn in five distinct modes: profiles, companies, and posts. It outputs all data from the original LinkedIn payload, but flattens it by duplicating each field at the top level with a data_ prefix (e.g., data_followers), making it easier to query and filter without navigating nested objects.

Key Features

• Multi-Mode Operation: One actor handles multiple use cases: profileByUrl, profileByName, companyByUrl, postByUrl, and postsByProfile.
• Raw-Expanded Output: All original data fields are available at the top level with a data_ prefix alongside a cleaned, structured version.
• Performance & Safety:
  • Caching: Repeated identical requests return instantly with a "status": "cached" indicator.
  • Rate Limiting: A safety clamp enforces a limit of 50 or fewer items for multi-result modes.
  • Tenant Scoping: Optional userId input partitions the cache per tenant or workspace.
• Operational Note: For reliable completion on fresh, uncached targets, allocate a timeout budget of around 20 minutes.

How to Use

Provide a JSON object as input. The mode field is required. Only include other fields relevant to your chosen mode.

Input Structure

Common Fields
* mode (string, required): One of: profileByUrl, profileByName, companyByUrl, postByUrl, postsByProfile.
* limit (integer, optional, 1-50): Cap for multi-result modes (profileByName, postsByProfile). Default is 10.

Batching Fields (use arrays for multiple items)
* urls: For profileByUrl, companyByUrl, postByUrl.
* fullNames: For profileByName.
* profileUrls: For postsByProfile.

Single-Value Fields (alternative to batching)
* url: For profileByUrl, companyByUrl, postByUrl.
* fullName: For profileByName.
* profileUrl: For postsByProfile.

Tip: Use canonical URLs (https://www.linkedin.com/...). Avoid country-specific subdomains and tracking parameters for best results.

Quick Start Examples

Fetch a single profile:

{
  "mode": "profileByUrl",
  "url": "https://www.linkedin.com/in/reidhoffman/"
}

Search for profiles by name:

{
  "mode": "profileByName",
  "fullName": "Ada Lovelace",
  "limit": 3
}

Get recent posts from a profile:

{
  "mode": "postsByProfile",
  "profileUrl": "https://www.linkedin.com/in/satyanadella/",
  "limit": 10
}

Batch process company URLs:

{
  "mode": "companyByUrl",
  "urls": [
    "https://www.linkedin.com/company/ibm/",
    "https://www.linkedin.com/company/microsoft/"
  ]
}

Input/Output

The actor returns a JSON object for each processed item. The structure includes both cleaned fields and the original raw data.

Output Example (Profile):

{
  "jobId": "68cfc1562c409e61554902e1",
  "mode": "profileByUrl",
  "status": "succeeded",
  "type": "entity",
  "key": "li:profile:https://www.linkedin.com/in/ada-lovelace",
  "canonicalUrl": "https://www.linkedin.com/in/ada-lovelace",
  "fetchedAt": "2025-09-21T09:20:00.000Z",
  "fullName": "Ada Lovelace",
  "headline": "Pioneer of Computing",
  "location": "London, United Kingdom",
  "experiences": [...],
  "educations": [...],
  "data_full_name": "Ada Lovelace",
  "data_headline": "Pioneer of Computing",
  "data_location": "London, United Kingdom",
  "data_experiences": [...],
  "data_education": [...]
}

Key output fields:
* status: Indicates "succeeded", "cached", or an error state.
* Cleaned fields like fullName, headline, experiences.
* Duplicated raw fields prefixed with data_ (e.g., data_full_name, data_experiences).