# LinkedIn Job Change Detector & Alerts (`oday/mawsool-linkedin-job-change-watch`) Actor

Monitor LinkedIn URL lists for company and headline changes. Schedule daily, weekly or monthly checks and send changed-profile verdicts to your webhook.

- **URL**: https://apify.com/oday/mawsool-linkedin-job-change-watch.md
- **Developed by:** [Mawsool Intertaional FZCO](https://apify.com/oday) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.40 / 1,000 linkedin job checks

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## LinkedIn Job Change Detector & Alerts

**Schedule a LinkedIn URL list and receive a `needsUpdate` verdict when a company or headline changes.**

**Mawsool LinkedIn data suite:** use **Current Company Checker** for one-time CRM audits, **Profile Details from URL** to enrich changed records, and **Mass LinkedIn Profile Scraper** for large backfills.

### How does scheduled job-change monitoring work?

1. Save an Actor task containing your LinkedIn URLs.
2. Add an Apify Schedule: daily, weekly, or monthly.
3. The first run stores the baseline.
4. Later runs compare the current company and headline with the previous snapshot.
5. Changed rows appear in the dataset and can be POSTed to your HTTPS webhook.

State is kept in a named key-value store in your Apify account. Your CRM database and custom attributes do not leave your account; only submitted LinkedIn URLs are checked.

### What do I pay if I check weekly?

Every scheduled run checks every URL once. Every URL checked is billed, whether changed or unchanged.

`monthly cost ≈ URLs × plan price per URL × runs per month`

At the FREE tier ($0.60 / 1,000 checks):

- 1,000 weekly URLs: $0.60/week.
- 1,000 daily URLs: about $18 in a 30-day month.
- 10,000 monthly URLs: $6/month.

### Output

The baseline run writes baseline rows. Later runs write changed rows only: previous/current company, previous/current headline, `needsUpdate`, and `changeType`.

### Alerts

Set `webhookUrl` to receive changed rows. You can also connect the scheduled task to Apify email, Slack, Make, or Zapier integrations.

# Actor input Schema

## `urls` (type: `array`):

Add linkedin.com/in/... profile URLs.

## `urlsCsv` (type: `string`):

Header: url. Current Company Checker also accepts previousCompany.

## `fileUrl` (type: `string`):

CSV with a url or linkedinUrl column.

## `maxUrls` (type: `integer`):

Cost-control cap. Maximum 10,000.

## `concurrency` (type: `integer`):

How many watched profile URLs to check at the same time.

## `watchId` (type: `string`):

Stable ID for this list. Reuse it on every scheduled run.

## `stateStoreName` (type: `string`):

Named persistent key-value store holding the previous snapshot.

## `webhookUrl` (type: `string`):

HTTPS endpoint receiving changed rows only. The baseline run sends no webhook.

## Actor input object example

```json
{
  "urls": [
    "https://www.linkedin.com/in/osama-abdelhadi/"
  ],
  "urlsCsv": "url\nhttps://www.linkedin.com/in/osama-abdelhadi/",
  "maxUrls": 100,
  "concurrency": 5,
  "watchId": "default",
  "stateStoreName": "mawsool-linkedin-job-watch"
}
```

# Actor output Schema

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

No description

## `flatView` (type: `string`):

No description

## `runSummary` (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 = {
    "urls": [
        "https://www.linkedin.com/in/osama-abdelhadi/"
    ],
    "urlsCsv": `url
https://www.linkedin.com/in/osama-abdelhadi/`
};

// Run the Actor and wait for it to finish
const run = await client.actor("oday/mawsool-linkedin-job-change-watch").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 = {
    "urls": ["https://www.linkedin.com/in/osama-abdelhadi/"],
    "urlsCsv": """url
https://www.linkedin.com/in/osama-abdelhadi/""",
}

# Run the Actor and wait for it to finish
run = client.actor("oday/mawsool-linkedin-job-change-watch").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 '{
  "urls": [
    "https://www.linkedin.com/in/osama-abdelhadi/"
  ],
  "urlsCsv": "url\\nhttps://www.linkedin.com/in/osama-abdelhadi/"
}' |
apify call oday/mawsool-linkedin-job-change-watch --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,oday/mawsool-linkedin-job-change-watch"
        }
    }
}
```

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/7NMFymW10I0yR7Zzw/builds/gULU3WihnZNVd5KbY/openapi.json