Menu
How to scan a job source through an Apify actor as a keyed provider.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
AI job search command center -- evaluate offers, generate CVs, scan portals, track applications
How to mirror the career-ops tracker to a Notion database and read records back as job leads.
How to pull job leads from a Gmail label into the career-ops pipeline.
How to use the {{NAME}} plugin and the data it produces.
AI job search command center -- evaluate offers, generate CVs, scan portals, track applications
| name | career-ops-plugin-apify |
| description | How to scan a job source through an Apify actor as a keyed provider. |
| license | MIT |
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.
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]
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/.