Accounting & HR
Set up Greenhouse (recruiting)
Connect Greenhouse to make hiring searchable — jobs, candidates and applications, each application carrying its current stage and linked to both its job and its candidate — so "where is the Berlin search" answers from the ATS itself. Read-only.
Before you start
- The credential is a Harvest API key, created by a Greenhouse user with Developer permission under Configure (gear) → Dev Center → API Credential Management → Create new API key, type Harvest.
- Tick the GET permissions for Jobs, Candidates and Applications only — nothing else is used. Copy the key right away; Greenhouse shows it once.
- Only GET calls are ever issued — the key can never write to Greenhouse.
- Greenhouse → Configure → Dev Center → API Credential Management → create a Harvest key with GET permissions for Jobs, Candidates and Applications.
- Documents → Greenhouse, paste the key.
- Choose access groups, Test, then Sync.
What comes in
- Jobs: title, status, departments, offices and the date opened.
- Candidates: name, company, title, email and the date added.
- Applications: linked to both their job and their candidate, carrying the current stage, status, application date and source.
- Only jobs, candidates and applications are read — no interview notes or scorecards, no offer or feedback data.
Access
Greenhouse exposes no per-record sharing to mirror, so the access groups chosen on this source decide who can ask, allow-only. Candidate data is personal data — a hiring-team group is the natural choice.
Jobs are capped at 500 and candidates at 3,000, and the sweep always keeps the newest records under the cap — it probes a recent window first and widens it until enough rows turn up, rather than freezing on whatever the API happens to list first, so new hiring activity never gets stuck behind an old backlog.
Last updated 20 Sep 2026