一键导入
career-ops-plugin-apify
How to scan a job source through an Apify actor as a keyed provider.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
How to scan a job source through an Apify actor as a keyed provider.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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/.