LinkedIn Talent Flow Mapper
Pricing
from $40.00 / 1,000 flow rows
LinkedIn Talent Flow Mapper
See where a company's talent comes from and where it goes. Enter a LinkedIn company URL; the Actor reads recent job-change events — who joined, who left, who was promoted — and maps feeder companies, destination companies, notable movers, and net flow. No cookies, no login.
Pricing
from $40.00 / 1,000 flow rows
Rating
0.0
(0)
Developer
Data Slayer
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
19 days ago
Last modified
Categories
Share
See where a company's talent comes from — and where it goes.
Watch the demo
YouTube video coming soon.
What this Actor does
Enter one LinkedIn company URL. The Actor reads recent job-change events for that company — people who joined, people who left, and people promoted — then resolves each mover's counterparty company and returns a flow map:
- Feeder companies — where the new hires came from.
- Destination companies — where the leavers went.
- Notable movers — the individual moves, most recent first.
- Net flow — joined minus left over the window.
It uses public data only, requires no cookies and no login, and does not invent a company that was never on a profile.
Input
| Field | Type | Required | Description |
|---|---|---|---|
company_url | string | Yes | LinkedIn company page URL or slug (e.g. https://www.linkedin.com/company/globex or globex) |
days_ago | integer | No | Look-back window for job-change events, 1–365 (default 90) |
max_people | integer | No | Hard cap on movers whose counterparty company is resolved — the main cost control, 1–100 (default 25) |
max_pages | integer | No | How many event pages to read, up to 50 events per page, 1–10 (default 3) |
Example:
{"company_url": "https://www.linkedin.com/company/globex","days_ago": 90,"max_people": 25,"max_pages": 3}
How to use it
- Paste the LinkedIn company URL (or just the slug).
- Set how far back to look and how many movers to resolve.
- Click Start.
- Read the feeder/destination companies and the individual movers.
Output
One row per flow insight:
{"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,"peopleSampled": 18,"insightType": "feeder_company","counterpartyCompany": "Acme Corp","counterpartyCompanyUrl": "https://www.linkedin.com/company/acme-corp","peopleCount": 4,"share": 0.2222,"personName": "","personProfileUrl": "","previousTitle": "","newTitle": "","transitionedOn": "","collectedAt": "2026-09-25T10:00:00+00:00"}
insightType is one of feeder_company, destination_company, notable_mover, or net_flow.
The OUTPUT key-value-store record reports events, joined/left/title-change counts, movers enriched, and rows written.
Pricing
| Event | Price |
|---|---|
| Actor start | $0.05 |
| Flow row | $0.04 |
You pay per insight row returned. A typical run over one company produces 10–40 rows.
Common uses
- Competitive intelligence — see where a rival is hiring from and losing people to.
- Recruiting — target the feeder companies that supply a role you need.
- Retention risk — watch where your own people go.
- Market mapping — find the talent hubs around a category.
Limits
- Events cover public, tracked companies; a company we do not track returns no events.
- Feeder/destination companies come from each mover's public experience, so they are resolved only for the movers within your
max_peoplecap. - Title changes are reported as events; they do not add a feeder or destination company.
- Detection lag varies — a change can surface later than it happened.
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:
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.