Job Board Change Monitor

Monitor one Greenhouse or Lever public board across scheduled runs. Each successful check produces one dataset row containing changes, listedCount, pendingRemovalCount, the observation time and an evidence URL.

{"board":"https://job-boards.greenhouse.io/webflow","snapshotStoreName":"my-job-monitor"}

Use the same named store for future runs. The store belongs to the account running the Actor. A different name starts a new baseline. Use a unique board/store pair per independent monitor and do not run overlapping writers. Scheduling must keep one run at a time; v0.1 does not implement a distributed lock.

The Actor uses limited permissions. Start with a fresh store name and let the Actor create it; do not pre-create the store yourself. Later runs by the same account can reuse that Actor-created store. An existing store created manually or by another Actor is unsupported and can fail with a permission error. If that happens, choose a fresh name. This Actor does not request additional access to unrelated stores in your account.

The first successful run saves a baseline and returns an empty changes array. Later runs report added, updated and removed. Tracked fields are title, location, canonical URL and available Lever department, commitment and workplace type. Description, salary and source update timestamps are not change triggers in this version.

A missing job is retained as pending on the first complete check where it is absent. It is reported as removed only if still absent on the next successful check. An incomplete response or outage fails the run without a board-check charge or advancing the baseline; the start fee still applies. A returning pending job is not falsely reported as newly added. Removal describes disappearance from the public board, not proof that the role was filled.

Maximum 5,000 jobs per board. Lever pagination is not an atomic source snapshot; repeated IDs are rejected, and two-run removal confirmation reduces transient false removals. Results are published before updating state. If the state write fails after publication, changes may be repeated on the next run; consumers should deduplicate event deliveries if required.

Configured price: $0.01 per successful check, including baseline checks and checks with zero changes, via board-checked, plus Apify's $0.00005 start event (one event at the default 256 MB memory). The price is per board check, not per change. Verify the current Pricing tab. The separate SUMMARY record reports counts and whether the budget stopped the run.