Track Greenhouse job board changes with Apify and Data Tables

Description

Quick overview This workflow runs the Apify Greenhouse Job Edit Feed Actor for a configured Greenhouse board and stores the latest change event per job in an n8n Data Table, after verifying the Actor run status, SUMMARY manifest, and dataset readback. How it works Runs manually when you execute the workflow. Starts an Apify Actor run (Greenhouse Job Edit Feed) for the configured Greenhouse board slug and namespace. Fetches the Actor run’s SUMMARY record from the Apify key-value store and validates that the run succeeded and the board manifest is complete. Creates the “Greenhouse Job Watchlist” n8n Data Table if it does not already exist. Downloads the completed Actor dataset from Apify and verifies the dataset row count and source run IDs match the validated SUMMARY. Deduplicates and maps events to a stable job key (board + post_id), deriving visibility and capturing fields like title, location, URL, description text/hash, and changed fields. Upserts one row per job into the n8n Data Table so re-runs update the existing job record with the latest event details. Setup Create an Apify account and add an Apify API token as an HTTP Bearer credential in n8n, then select it on all three Apify HTTP Request steps. Update the Actor input JSON to set your Greenhouse board slug(s) and the namespace used by the Actor. Ensure your n8n instance has access to n8n Data Tables and keep (or rename) the target table name “Greenhouse Job Watchlist” as needed. An n8n automation workflow template by dfsav.

Community Metrics

Categories

• Automation

Tags

• n8n
• workflow
• http-request
• code

Capabilities

• 2 nodes

Information