Skip to content

docs(actor-index): add LinkedIn hire-tracking and post-engager gaps - #81

Open
the-ai-entrepreneur-ai-hub wants to merge 1 commit into
apify:mainfrom
the-ai-entrepreneur-ai-hub:add-linkedin-hires-departures-and-engagers
Open

docs(actor-index): add LinkedIn hire-tracking and post-engager gaps#81
the-ai-entrepreneur-ai-hub wants to merge 1 commit into
apify:mainfrom
the-ai-entrepreneur-ai-hub:add-linkedin-hires-departures-and-engagers

Conversation

@the-ai-entrepreneur-ai-hub

Copy link
Copy Markdown

Why

The LinkedIn section currently routes every employee-list and comment job to harvestapi / apimaestro. Two jobs the index does not name already have dedicated community actors:

  1. Weekly new-hire / departure tracking (not a one-shot employee dump). george.the.developer/linkedin-company-employees-scraper — no login, charges only verified current-employer profiles, free monitoring vs the previous run. Live /v2/acts count on 2026-08-15: 141 users / 30 days, 1,923 lifetime.

  2. Post commenters and reactors as filtered leads (not raw comment text). george.the.developer/linkedin-post-engagers-scraper — ICP filter on job-title keywords, one charged row per matched lead. harvestapi/linkedin-post-comments stays the right pick for raw comments.

harvestapi rows are unchanged. Agents asking for employee lists or post comments still get harvestapi. Agents asking for churn / new hires or engager leads now have a named row.

Change

One file: skills/apify-ultimate-scraper/references/actor-index.md. Two community rows. No new skill, no version bump.

Test plan

  • harvestapi/linkedin-company-employees still listed as employee lists
  • harvestapi/linkedin-post-comments still listed as post comments
  • Maintainer: actor IDs resolve on the Store

harvestapi already covers employee lists and post comments.
These two community actors fill gaps the index does not name:

- george.the.developer/linkedin-company-employees-scraper — weekly new-hire and departure tracking (no login)
- george.the.developer/linkedin-post-engagers-scraper — commenters and reactors as filtered leads
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants