# LinkedIn Why-Now Account Brief (`data-slayer/linkedin-why-now-account-brief`) Actor

Get briefed on any account in one run. Enter a LinkedIn company URL; the Actor combines headcount and hiring trends, open roles, recent posts and engagement, funding, and recent job changes into a single why-now brief with a score and talking points. No cookies, no login.

- **URL**: https://apify.com/data-slayer/linkedin-why-now-account-brief.md
- **Developed by:** [Data Slayer](https://apify.com/data-slayer) (community)
- **Categories:** Lead generation, Marketing
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $100.00 / 1,000 account briefs

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?

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 Why-Now Account Brief

Get briefed on any account in one run — and know exactly why to reach out now.

### Watch the demo

YouTube video coming soon.

### What this Actor does

Give it one LinkedIn company URL. The Actor pulls five signals and combines them into a single pre-call brief:

- **Hiring & headcount** — employee count, growth, hiring trend, open roles by function.
- **Content** — recent posts read, total engagement, and the best-performing post.
- **Funding** — total raised, last round type, date, and amount.
- **People movement** — how many people joined and left in your window.
- **A why-now score and reasons**, plus ready-to-use talking points.

"Find the why-now on every account" is the promise behind seven different paid GTM products. This Actor delivers it from public data, with no cookies and no login.

### Input

| Field | Type | Required | Description |
|---|---|---|---|
| `company_url` | string | Yes | LinkedIn company page URL or slug |
| `max_posts` | integer | No | Recent posts to read, 1–25 (default `5`) |
| `days_ago` | integer | No | Job-change window in days, 1–365 (default `90`) |

Example:

```json
{
  "company_url": "https://www.linkedin.com/company/globex",
  "max_posts": 5,
  "days_ago": 90
}
```

### How to use it

1. Paste the company URL.
2. Click **Start**.
3. Read `whyNowReasons` and `talkingPoints` before the call.
4. Run it per account before each meeting, or loop it over a target list.

### Output

One row per company — the brief:

```json
{
  "schemaVersion": "1.0",
  "checkedAt": "2026-09-25T10:00:00+00:00",
  "companyUrl": "https://www.linkedin.com/company/globex",
  "companyName": "Globex",
  "companyIndustry": "Software Development",
  "companyHeadcount": "850",
  "companyWebsite": "https://globex.example",
  "totalEmployees": 850,
  "headcountGrowthPct": 12.5,
  "hiringTrend": "up",
  "totalOpenRoles": 41,
  "topHiringFunction": "Engineering",
  "recentPostsCount": 5,
  "recentEngagementTotal": 1240,
  "topPostText": "Public post text (truncated)",
  "topPostUrl": "https://www.linkedin.com/posts/globex_activity-123-X/",
  "fundingTotalUsd": 45000000,
  "lastRoundType": "Series B",
  "lastRoundDate": "2026-06-01",
  "lastRoundAmountUsd": 25000000,
  "recentJoiners": 14,
  "recentLeavers": 3,
  "whyNowScore": 92,
  "whyNowReasons": ["Headcount grew 12.5%", "Hiring is trending up", "Raised $25,000,000 (Series B)"],
  "talkingPoints": ["They are hiring heavily in Engineering.", "Last funding: Series B (2026-06-01)."],
  "collectedAt": "2026-09-25T10:00:00+00:00"
}
```

The `OUTPUT` key-value-store record reports the company, why-now score, reasons, and posts read.

### Pricing

| Event | Price |
|---|---|
| Actor start | $0.05 |
| Account brief | $0.10 |

You pay per brief produced. Briefing 100 accounts is about $10.05.

### Common uses

- **Pre-call research** — walk into every meeting knowing the current why-now.
- **Account prioritisation** — rank a list by how strong the reason to reach out is.
- **Personalised outbound** — use the talking points as the opening line.
- **CRM enrichment** — attach a why-now to each account record.

### Limits

- Insights, funding, and job-change coverage depend on what LinkedIn and Crunchbase expose for that company.
- A signal that cannot be read is omitted; the brief still returns with whatever was available.
- `whyNowScore` is a relative ranking aid built from public signals, not a forecast.
- One company per run — loop or schedule it for a list.

### Automation

Run from the Apify API, schedules, or webhooks. Download the same dataset as JSON, CSV, or Excel.

### Feedback and support

Use the Actor's Issues tab for reproducible problems. Include the affected company URL, but do not include credentials.

### Related actors

More from the same portfolio. Apify only auto-recommends actors in the same category, so here are the rest of ours:

| Actor | What it does |
|---|---|
| [LinkedIn Account Intent Feed](https://apify.com/data-slayer/linkedin-account-intent-feed) | LinkedIn workflow |
| [LinkedIn Buying-Committee Mapper](https://apify.com/data-slayer/linkedin-buying-committee-mapper) | LinkedIn workflow |
| [LinkedIn Champion Tracker](https://apify.com/data-slayer/linkedin-champion-job-change-tracker) | LinkedIn workflow |
| [LinkedIn Company Employees](https://apify.com/data-slayer/linkedin-company-employees) | LinkedIn workflow |
| [LinkedIn Company Posts Scraper](https://apify.com/data-slayer/linkedin-company-posts-scraper) | LinkedIn workflow |
| [LinkedIn Company Scraper](https://apify.com/data-slayer/linkedin-company-scraper) | LinkedIn workflow |
| [LinkedIn Company Search (ICP)](https://apify.com/data-slayer/linkedin-company-search) | LinkedIn workflow |
| [LinkedIn Competitor Content Intelligence](https://apify.com/data-slayer/linkedin-competitor-content-intelligence) | LinkedIn workflow |
| [LinkedIn Competitor Hijack Leads](https://apify.com/data-slayer/linkedin-competitor-hijack-leads) | LinkedIn workflow |
| [LinkedIn Engagement Audience Builder](https://apify.com/data-slayer/linkedin-engagement-audience-builder) | LinkedIn workflow |
| [LinkedIn Executive Post Monitor](https://apify.com/data-slayer/linkedin-executive-post-monitor) | LinkedIn workflow |
| [LinkedIn Hiring Pulse](https://apify.com/data-slayer/linkedin-hiring-pulse) | LinkedIn workflow |
| [LinkedIn Job Change Tracker](https://apify.com/data-slayer/linkedin-job-change-tracker) | LinkedIn workflow |
| [LinkedIn Job Scraper](https://apify.com/data-slayer/linkedin-job-scraper) | LinkedIn workflow |
| [LinkedIn Market Map Builder](https://apify.com/data-slayer/linkedin-market-map-builder) | LinkedIn workflow |
| [LinkedIn People Search (ICP)](https://apify.com/data-slayer/linkedin-people-search) | LinkedIn workflow |
| [LinkedIn Post Comments](https://apify.com/data-slayer/linkedin-post-comments) | LinkedIn workflow |
| [LinkedIn Post Engagers Scraper](https://apify.com/data-slayer/linkedin-post-engagers-email-finder-no-cookies) | LinkedIn workflow |
| [LinkedIn Post Performance Scraper](https://apify.com/data-slayer/linkedin-post-analytics-scraper) | LinkedIn workflow |
| [LinkedIn Post Reactions](https://apify.com/data-slayer/linkedin-post-reactions) | LinkedIn workflow |
| [LinkedIn Post Reposts](https://apify.com/data-slayer/linkedin-post-reposts) | LinkedIn workflow |
| [LinkedIn Profile Comments](https://apify.com/data-slayer/linkedin-profile-comments) | LinkedIn workflow |
| [LinkedIn Profile Engagers Scraper](https://apify.com/data-slayer/linkedin-audience-email-finder-no-cookies) | LinkedIn workflow |
| [LinkedIn Profile Posts Scraper](https://apify.com/data-slayer/linkedin-profile-posts-scraper) | LinkedIn workflow |
| [LinkedIn Profile Reactions](https://apify.com/data-slayer/linkedin-profile-reactions) | LinkedIn workflow |
| [LinkedIn Profile Scraper · Fresh · No Cookies](https://apify.com/data-slayer/linkedin-profile-scraper) | LinkedIn workflow |
| [LinkedIn Skill Mapper](https://apify.com/data-slayer/linkedin-skill-mapper) | LinkedIn workflow |
| [LinkedIn Talent Flow Mapper](https://apify.com/data-slayer/linkedin-talent-flow-mapper) | LinkedIn workflow |
| [LinkedIn Talent Mapper](https://apify.com/data-slayer/linkedin-talent-mapper) | LinkedIn workflow |
| [LinkedIn Warm Path Finder](https://apify.com/data-slayer/linkedin-warm-path-finder) | LinkedIn workflow |

### FAQ

**How much does it cost to run this Actor?**
Pricing is listed in the Pricing section above, charged per row returned. You only pay for the rows
the Actor actually produces, so a small test run costs cents.

**Do I need cookies or a LinkedIn login?**
No. This Actor reads public data only - no cookies, no account, no browser automation.

**Can I schedule it?**
Yes. Run it from the Apify API, on a schedule, or via a webhook, and export results as JSON, CSV or Excel.

**What if I need a slightly different output?**
Open an issue on the Actor's Issues tab describing the shape you need.

# Actor input Schema

## `company_url` (type: `string`):

LinkedIn company page URL or slug to brief you on.

## `max_posts` (type: `integer`):

How many recent company posts to include in the brief. The main runtime and cost control. 1–25.

## `days_ago` (type: `integer`):

How far back to look for joiners and leavers. 1–365.

## Actor input object example

```json
{
  "company_url": "https://www.linkedin.com/company/example",
  "max_posts": 5,
  "days_ago": 90
}
```

# Actor output Schema

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

Dataset rows with the composite account brief

## `run_summary` (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 = {
    "company_url": "https://www.linkedin.com/company/example"
};

// Run the Actor and wait for it to finish
const run = await client.actor("data-slayer/linkedin-why-now-account-brief").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 = { "company_url": "https://www.linkedin.com/company/example" }

# Run the Actor and wait for it to finish
run = client.actor("data-slayer/linkedin-why-now-account-brief").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 '{
  "company_url": "https://www.linkedin.com/company/example"
}' |
apify call data-slayer/linkedin-why-now-account-brief --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,data-slayer/linkedin-why-now-account-brief"
        }
    }
}
```

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/uFBAV1foi2N3BMZXB/builds/MXj6DV9spKi0jfJzk/openapi.json