Skip to content
NEWMarketplace and your team: sell what you build, and get plans and changes that are tested before you see them. See what is new

Library / Web Scraping & Research

Web Scraping & Research

Track Greenhouse job board changes with Apify and Data Tables

Runs an Apify Greenhouse job feed scrape for one board on manual trigger, verifies the run, and upserts job changes into an n8n Data Table.

What it does

# Track Greenhouse job changes in an n8n Data Table Who this is for: teams that monitor public Greenhouse job boards and want a persistent, reviewable change feed. What it does: runs the public Greenhouse Job Edit Feed Actor for one configured board, checks that the run and every requested board completed, verifies the SUMMARY manifest against dataset readback, and upserts the latest event by the stable (board, post_id) key. Description-only edits update the text and hash; closed jobs become hidden; reopened and reappeared jobs become visible again. Incomplete or mismatched runs stop before job rows are written. Set up: choose your board slug and namespace in “Run Greenhouse Edit Feed Actor”; use an Apify Bearer credential in the three HTTP Request nodes; keep the HTTP credential in n8n Credentials. Set the same credential on all three nodes. The Data Table is created if missing. Importantly, the first run may create the table before dataset validation; row upserts only occur after validation. Usage and costs: the template is free. The Actor itself is a separate Apify product and is billed to your Apify account. The workflow caps each Actor run at $0.05 and requests 256 MB. On 12 Oct 2026, the public listing showed $0.01 per board snapshot plus $0.001 per Actor start; confirm the listing before use. Your n8n hosting plan may also have its own cost. Limits: manual, on-demand checks; no email or Slack notifications. Review uncertain/missing candidates before acting. Public job data only. Do not put API keys in node fields or workflow exports.

The steps

  1. Run Greenhouse Edit Feed Actor
  2. Read Actor completion SUMMARY
  3. Validate completed Actor SUMMARY
  4. Ensure persistent job table exists
  5. Read completed Actor dataset
  6. Validate dataset and map producer events by stable job ID
  7. Upsert one persistent job row
  8. Run job board check

Similar automations