Greenhouse · Connector
How do we connect Greenhouse to AI agents on our own infrastructure?
Katonic connects to Greenhouse, reads candidates and jobs and indexes them in the Knowledge Engine on infrastructure you control. An agent can then compare candidates with a role's criteria using a model you serve, so candidate records are not sent to a public AI service.
What it reads.
From Greenhouse.
- 01Candidates
- 02Jobs
Through: Greenhouse Harvest API v1
Where the content goes
Into a knowledge store you run.Content is pulled into the Knowledge Engine on infrastructure you own or control, and indexed there. Agents answer from it with a model you serve. The documents, the index and the questions are not sent to a public AI service.
How it signs in
OAuth 2.0. The connector also supports a Harvest API key.
Permissions
Access is set on the source in Katonic: everyone given access to the source can retrieve its documents. The permissions Greenhouse holds for each item are not read.
Sync
Incremental, by updated time.
You set how often the source is read again, in minutes, hours, days or weeks.
Limits
- Candidate records are personal data. Everyone given access to the source in Katonic can retrieve them, so give that access to the recruiting team only.
Use case pages that name Greenhouse.
Does it change a candidate's stage?
No. The connector reads candidates and jobs. It writes nothing to Greenhouse.
Who can retrieve the candidate records?
Everyone given access to the source in Katonic. Greenhouse's own permissions are not read.
Where are the records indexed?
In the Knowledge Engine, on infrastructure you own or control. They are not sent to a public AI service.