What connects to Greenhouse

Greenhouse is the applicant tracking system where jobs, candidates, applications, interviews and offers live. Its integrations cluster around two moments.

The first is the hire. When a candidate accepts, the offer, personal data and start date have to reach the HR system of record. For companies on BambooHR that means a new employee record with job information and compensation. For groups on Workday it means opening the Hire or Pre-Hire business process against the right supervisory organization and position, and receiving approved requisitions back as Greenhouse jobs with a shared requisition ID.

The second is the switch. Teams moving from Lever bring candidates, opportunities, stages, feedback and resumes across, so recruiting history is not lost on day one.

Where Greenhouse integrations break

Hired is not offer resolved. A candidate can sit at the Hired stage before the offer is approved. Read too early and there is no start date and no salary, so the trigger has to wait for a resolved offer.
There is no shared ID. A Greenhouse candidate and an HRIS employee have nothing in common until the pipeline links them. Without a stored mapping and a check for rehires, a retry creates a second person.
Harvest API write rules. The Harvest API is rate limited and requires an On-Behalf-Of user on create and update calls. A naive loop drops records mid-batch or attributes every action to a service account.
Data models disagree. Greenhouse stages belong to each job’s interview plan, and one candidate can hold several applications. Mapping from Lever opportunities, or onto a fixed set of HRIS statuses, is a per-job decision.
Demographic data stays put. EEO and equal-opportunity answers are special-category data under the GDPR. What moves is decided per field, and diversity data stays in Greenhouse by default.