Greenhouse integration
Every opening starts as an approved position
Greenhouse owns candidates and openings. Kinnect owns the approved, funded position behind each one, and the two stay in sync both ways.
Standard APIs. Your Recruiting stays the system of record for what it owns.
Greenhouse and Kinnect connected: Requisition, on Start Recruiting for an approved position, outbound from kinnect; Candidate stage changes, inbound to kinnect; Hired event via the Candidate-Hired endpoint, inbound to kinnect; Candidates, interviews, offers, inbound to kinnect.
What moves
What moves, which way, and who stays the record
Into Kinnect
- Candidate stage changes
- Hired event via the Candidate-Hired endpoint
- Candidates, interviews, offers
- Position approval, budget line, History
Out to Greenhouse
- Requisition, on Start Recruiting for an approved position
- Position approval, budget line, History
Who stays the record
Greenhouse is the system of record for recruiting activity: candidates, interviews and offers. Kinnect is the record of the approved position the opening belongs to. Workday, where connected, stays the record for workers and positions.
| Data | Direction | System of record |
|---|---|---|
| Requisition, on Start Recruiting for an approved position | Outbound from Kinnect | Kinnect (position), Greenhouse (opening) |
| Candidate stage changes | Inbound to Kinnect | Greenhouse |
| Hired event via the Candidate-Hired endpoint | Inbound to Kinnect | Greenhouse |
| Candidates, interviews, offers | Inbound to Kinnect | Greenhouse |
| Position approval, budget line, History | Both directions | Kinnect |
What it does
Greenhouse and Kinnect, on one position
- Start Recruiting creates the requisitionGreenhouse is the applicant tracking system where recruiters run pipelines, interviews and offers. It holds candidates and openings; it does not hold positions or budgets.
- Candidate movement syncs backAs candidates move through Greenhouse stages, the movement syncs into the requisition detail in Kinnect: the Candidate tab shows pipeline stage and details, and the Recruiting page stat cards update. Days open against a target hire date with no candidate movement is the signal a Finance or HR lead uses to intervene.
- The Candidate-Hired endpoint closes the loopWhen a candidate is marked hired in Greenhouse, the hire event reaches Kinnect through the Candidate-Hired endpoint. The requisition closes and the position flips to Filled.
The Kinnect record Greenhouse connects to: the requisition detail with its attached position
Setup
How setup works
Select Greenhouse as the ATS in Settings > System. The Integrations hub then shows the Greenhouse card.
On the ATS card in Settings > Integrations, enter credentials and run Test connection.
Add the webhook secret and the Candidate-Hired endpoint so hire events reach Kinnect.
Set the hire-type mapping and arrange the drag-and-drop field-mapping board for your requisition fields.
Greenhouse is on every Kinnect plan per the pricing page. Specific field names are configured on the mapping board per customer and are not listed here; no sync-frequency figure is published.
Kinnect Settings, Integrations: Greenhouse connected under Recruiting
Who uses it
One integration, three teams
Finance
Finance sees every Greenhouse opening tied to a budgeted position and can tell, from the Finance page, which open reqs are in the plan and what they cost.
HR and HRIS
HR sees the request, its approvals, the requisition and the hire in one History, and answers "was this authorized" without a thread.
Recruiting
Recruiting keeps working in Greenhouse and never works a ghost req. Every opening arrived from an approved position and closes itself on hire.
See it live
See Greenhouse connected on a live workspace
Tell us how Greenhouse is set up and how a seat moves today. We will show one approved, funded and in Greenhouse, and the number that results.
- Thirty minutes
- Demo data, shaped by your requirements
- No obligation
A Kinnect position request at the approval step, with the approver's required comment recorded against the decision
Greenhouse integration questions
Which direction does the Greenhouse integration run?
Both. Requisitions go from Kinnect to Greenhouse when recruiting starts on an approved position; candidate stage changes and the hired event come back to Kinnect.
What stays in Greenhouse?
Candidates, interviews and offers. Greenhouse is the system of record for recruiting activity; Kinnect is the record of the approved position the opening belongs to.
How is it set up?
In Settings > Integrations: credentials, test connection, a webhook secret, the Candidate-Hired endpoint, hire-type mapping and a field-mapping board. The ATS selector in Settings > System points the hub at Greenhouse.
What happens when a candidate is hired?
The hire event closes the requisition and flips the position to Filled; with Workday connected the hire flows on to Workday.
What if we use Workday Recruiting instead?
Select it in Settings > System; the hub then configures Workday Recruiting rather than Greenhouse. See the Workday Recruiting page.
See the Greenhouse integration in the product
A demo walks through Start Recruiting, the Candidate tab and the hire closing the position, on a live workspace.