Files
santifer--career-ops/plugins/apify/skill.md
T
wehub-resource-sync d083df1fdb
CodeQL Analysis / Analyze (javascript-typescript) (push) Failing after 2s
Web CI / web typecheck + build (push) Failing after 1s
Release Please / release-please (push) Failing after 1s
CodeQL Analysis / Analyze (go) (push) Failing after 16s
chore: import upstream snapshot with attribution
2026-07-13 12:02:43 +08:00

985 B

name, description, license
name description license
career-ops-plugin-apify How to scan a job source through an Apify actor as a keyed provider. MIT

apify plugin

A keyed provider: runs an Apify actor and maps its dataset items into the scanner. It fires ONLY on a portals.yml entry that sets provider: apify — never via auto-detection. Put APIFY_TOKEN in .env.

portals.yml entry

tracked_companies:
  - name: "Indeed — VP Engineering (Chicago)"
    provider: apify
    actor: misceres/indeed-scraper
    input: { position: "VP of Engineering", location: "Chicago, IL", maxItems: 25 }
    field_map:
      title:    [positionName, title]    # array = first non-empty wins
      url:      url
      company:  [company, companyName]
      location: [location, formattedLocation]

Then

node scan.mjs runs the provider for that entry and writes the results to the pipeline like any other source. An optional field_map.description caches the JD locally under jds/.