Apify Greenhouse Job Change Tracker in n8n Data Table

Track Greenhouse job changes automatically in n8n—stored as a live “watchlist” table

This n8n workflow runs the Apify Greenhouse Job Edit Feed Actor, verifies the Actor run results, deduplicates events per job, and upserts the latest change into an n8n Data Table named “Greenhouse Job Watchlist”. Re-run it anytime to keep your data current.

What this workflow does

• Manual execution: Start the workflow when you want to fetch the latest Greenhouse job edits.
• Runs the Apify Actor: Launches the Greenhouse Job Edit Feed Actor using your configured Greenhouse board slug(s) and namespace.
• Validates run success: Fetches the Actor run’s SUMMARY record from Apify key-value storage and confirms the run succeeded and the board manifest is complete.
• Creates/uses the Data Table: Creates the Greenhouse Job Watchlist n8n Data Table if it doesn’t exist.
• Reads and cross-checks dataset output: Downloads the completed Actor dataset and verifies row counts and that source run IDs match the validated SUMMARY.
• Deduplicates and maps events: Builds a stable job key (board + post_id) and derives job visibility while capturing key fields such as title, location, URL, description text/hash, and which fields changed.
• Upserts one row per job: Updates existing rows with the latest event details so your table reflects current job edit activity.

Use cases

• SaaS operators syncing Greenhouse job changes into internal reporting dashboards.
• Automation engineers auditing what changed (e.g., description/visibility/metadata) per Greenhouse post.
• Teams that need a persistent, queryable dataset of job edits without manual monitoring.

Technical details

• Nodes: Manual Trigger, HTTP Request, Code, Data Table, Sticky Note
• Integrations: Apify via HTTP Bearer token (used on all three Apify HTTP Request steps)
• Target storage: n8n Data Table named Greenhouse Job Watchlist (create/keep or rename as needed)

Get started: Add your Apify token in n8n as an HTTP Bearer credential, update the Actor input JSON with your board slug(s) and namespace, then run.