# LinkedIn Public Profiles, Posts & Articles Monitor — No Cookies (`snuggly_beanie_970/linkedin-public-profile-content-monitor`) Actor

Extract public LinkedIn person profiles plus recent posts and articles without login, cookies, passwords or browser sessions. Includes employers, education, followers, exact content dates, engagement, stable IDs, date checkpoints and seen-ID deduplication.

- **URL**: https://apify.com/snuggly\_beanie\_970/linkedin-public-profile-content-monitor.md
- **Developed by:** [Ilia](https://apify.com/snuggly_beanie_970) (community)
- **Categories:** Social media, Lead generation, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.35 / 1,000 linkedin public post or articles

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## 💼 LinkedIn Profiles, Posts & Articles — No Cookies

Turn public LinkedIn person pages into analysis-ready profile, post, and article records. No LinkedIn account, cookies, password, browser session, or API key is required.

### 📤 What you get

- name, first/last name, headline, creator badge, about text, location, country, photo, and follower count;
- current company plus public employer history, education, languages, awards, memberships, and related profile URLs;
- recent posts and long-form articles with stable IDs and canonical URLs;
- full public text, headline, publication/modification time, media, hashtags, and mentions;
- available interaction counters and a calculated total;
- parse provenance and confidence fields for reliable downstream QA;
- `postedAfter` and `seenContentIds` checkpoints for recurring monitoring.

### 🚀 Popular use cases

- monitor executive and creator content;
- enrich public professional profiles with employers and education;
- track post/article engagement and publishing cadence;
- feed public profile changes into CRM, research or alert workflows;
- export clean records into CRMs, Sheets, databases, Make, n8n, and alerting pipelines.

### 💰 Pricing

$1.40 per 1,000 successfully stored profile records and $1.35 per 1,000 successfully stored posts or articles. Platform usage is included; a tiny Actor-start event may apply.

### ⚙️ Example input

```json
{"profileUrls":["satyanadella"],"includeProfile":true,"includePosts":true,"includeArticles":true,"maxContentPerProfile":15,"seenContentIds":[]}
```

### 📥 Complete input reference

| Field | Type | Default | Purpose |
|---|---|---:|---|
| `profileUrls` | array | `["https://www.linkedin.com/in/satyanadella"]` | linkedin.com/in/ URLs or public profile slugs. |
| `includeProfile` | boolean | `true` | Store one normalized Person record per accessible profile. |
| `includePosts` | boolean | `true` | Store public recent DiscussionForumPosting records exposed by LinkedIn. |
| `includeArticles` | boolean | `true` | Store public LinkedIn Article records exposed on the profile. |
| `maxContentPerProfile` | integer | `15` | Hard cap across paid posts and articles per profile. |
| `postedAfter` | string | `""` | Optional inclusive YYYY-MM-DD incremental date checkpoint. |
| `seenContentIds` | array | `[]` | Optional IDs to skip without charge on repeated runs. |
| `requestDelayMs` | integer | `500` | Polite delay between public profile requests. |

### 📤 Complete output reference

The default dataset is exportable as JSON, CSV, Excel, XML or RSS. Fields remain stable for scheduled runs and API integrations.

| Field | Type |
|---|---|
| `recordType` | string |
| `profileSlug` | string |
| `profileUrl` | string |
| `profileName` | string / null |
| `firstName` | string / null |
| `lastName` | string / null |
| `headline` | string / null |
| `creatorBadge` | string / null |
| `profileDescription` | string / null |
| `location` | string / null |
| `country` | string / null |
| `imageUrl` | string / null |
| `image` | object / null |
| `followers` | integer / null |
| `interactionStatistics` | object |
| `currentCompany` | object / null |
| `worksFor` | array |
| `education` | array |
| `languages` | array |
| `awards` | array |
| `memberships` | array |
| `sameAs` | array |
| `recentPostCount` | integer / null |
| `recentArticleCount` | integer / null |
| `sourceFinalUrl` | string / null |
| `parsePath` | string |
| `parseConfidence` | string |
| `sourceUserAgent` | string |
| `contentId` | string / null |
| `contentUrl` | string / null |
| `contentType` | string / null |
| `text` | string / null |
| `headlineText` | string / null |
| `publishedAt` | string / null |
| `modifiedAt` | string / null |
| `likeCount` | integer / null |
| `commentCount` | integer / null |
| `shareCount` | integer / null |
| `totalInteractions` | integer / null |
| `hashtags` | array |
| `mentions` | array |
| `contentImage` | object / null |
| `scrapedAt` | string |

### 🔌 API & integrations

Run this Actor from the Apify Console, API, CLI, MCP, Make, Zapier or n8n. Replace the Actor identifier and token in this template:

```bash
curl -X POST "https://api.apify.com/v2/acts/linkedin-public-profile-content-monitor/runs?token=YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'
```

Results are stored in the run's default dataset and can be forwarded with Apify webhooks or scheduled Tasks.

### 🔎 Search keywords

LinkedIn Profiles, Posts & Articles — No Cookies, linkedin, profiles, posts, articles, cookies, public, profile, content, monitor, Apify Actor, scraper API, structured data, scheduled monitor, automation.

# Actor input Schema

## `profileUrls` (type: `array`):

linkedin.com/in/ URLs or public profile slugs.

## `includeProfile` (type: `boolean`):

Store one normalized Person record per accessible profile.

## `includePosts` (type: `boolean`):

Store recent public posts exposed by LinkedIn.

## `includeArticles` (type: `boolean`):

Store public LinkedIn Article records exposed on the profile.

## `maxContentPerProfile` (type: `integer`):

Hard cap across posts and articles per profile.

## `postedAfter` (type: `string`):

Optional inclusive YYYY-MM-DD checkpoint.

## `seenContentIds` (type: `array`):

Optional IDs to skip on repeated runs.

## `requestDelayMs` (type: `integer`):

Delay between public profile requests.

## `maxRetries` (type: `integer`):

Retry blocked and incomplete pages with fresh sessions.

## `requestTimeoutSecs` (type: `integer`):

Timeout for each LinkedIn request.

## `proxyConfiguration` (type: `object`):

Residential proxy is recommended for bulk runs.

## Actor input object example

```json
{
  "profileUrls": [
    "https://www.linkedin.com/in/satyanadella"
  ],
  "includeProfile": true,
  "includePosts": true,
  "includeArticles": true,
  "maxContentPerProfile": 15,
  "postedAfter": "",
  "seenContentIds": [],
  "requestDelayMs": 500,
  "maxRetries": 5,
  "requestTimeoutSecs": 30,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("snuggly_beanie_970/linkedin-public-profile-content-monitor").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("snuggly_beanie_970/linkedin-public-profile-content-monitor").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call snuggly_beanie_970/linkedin-public-profile-content-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,snuggly_beanie_970/linkedin-public-profile-content-monitor"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/qR2ghKIgZ1wJxD54y/builds/97CQAflBAouVTpj1F/openapi.json