New-job alerts with Apify
Use onlyNewJobs to build a recurring feed of newly delivered job identities. The Actor collects data; email, Slack and CRM delivery belong in your downstream automation.
Ready-to-run input
Use this configuration in the Actor’s JSON input. Review the live price and set a maximum run charge before starting. Limits are maximums, not guaranteed output counts.
{
"searchTerm": "software engineer",
"location": "New York, NY",
"jobBoards": [
"indeed"
],
"countryIndeed": "USA",
"maxResultsPerSite": 20,
"maxItems": 20,
"onlyNewJobs": true,
"stateKey": "engineering-new-york"
}Define one monitor
Save a task with a specific role, location and source. Set onlyNewJobs: true and give stateKey a stable value such as engineering-austin. The first run delivers matching jobs; subsequent runs skip identities already delivered.
Schedule without overlap
Choose an interval appropriate for your use case and source limits. Avoid overlapping runs against the same monitoring state. A completed run with no unseen matches can legitimately have an empty dataset.
Deliver after successful collection
Use an Apify webhook or automation platform to wait for the run, retrieve the dataset, and send each result onward. Inspect source outcomes and deduplicate downstream before posting alerts.
Keep a small operating budget
Set a maximum run charge and a combined result cap. Empty monitoring runs can still incur a start event. Check the live Actor pricing rather than extrapolating from a free test or an old price example.
Download an n8n starter
Collect Indeed jobs into Google Sheets with n8n. This alternative uses spreadsheet URL deduplication with onlyNewJobs disabled, so downstream write failures do not consume Actor-side monitoring state. Setup and connected-account testing are required.
Sources & next step
This guide describes the Group Oject Actor. Consult its current input schema, README and pricing before running. For integration details, see the Apify API documentation.
Build your searchRun on Apify