How to run AI first-round interviews from Greenhouse
Step by step: connect Hure to Greenhouse, import a job's candidates or start an AI voice interview from a stage, and get each result back on the candidate's profile.

Round one is where Greenhouse pipelines stall. Applications pile up in the first stage, someone has to book a phone screen with each one, and the people who apply on a Sunday night wait until Tuesday to hear anything. This guide shows how to hand that first round to Hure, an AI voice interviewer, without leaving Greenhouse: candidates come in from a job or a stage, each one gets the same voice interview, and the result lands back on their Greenhouse profile.
Integrations are enabled per team during early access. If you are setting this up for the first time, request access and tell us you run Greenhouse.
What the Greenhouse integration does
The connection works in both directions:
- Greenhouse to Hure: import. Pick a job, pick a Hure role, select candidates, and Hure creates one interview for each, up to 200 per import.
- Greenhouse to Hure: stage rules. “When a candidate reaches this stage of this job, interview them for this role.” Greenhouse tells Hure through a signed web hook, and Hure creates the interview and sends the invitation.
- Hure to Greenhouse: results. When the scorecard is ready, Hure posts the result to the candidate’s profile as a private, admin-only note, with a link to the full scorecard.
Before you start
You need a Greenhouse user who can reach Dev Center (to create an API key and a web hook) and a role in Hure whose rubric your team has sealed. Sealing matters: every candidate for a role is interviewed and scored against the same rubric version, so their scorecards stay comparable, and Hure only starts interviews on sealed roles.
Step 1: Create a Harvest API key
In Greenhouse, open Dev Center, then API Credential Management, and create a new API key of type Harvest. Give it access to:
- Candidates: read, and posting to a candidate’s notes.
- Users: read. Hure uses the user list so you can choose who the result notes are posted as.
Copy the key. You will paste it once, in the next step.
Step 2: Connect Greenhouse in Hure
In the Hure console, open Integrations, choose Greenhouse and paste the key. Hure checks the key with Greenhouse before saving it, and stores it encrypted. Use Test on the connection to confirm it works. The test proves the key is alive; because the sample result has no real candidate behind it, the delivery log shows it as skipped, which is expected.
Step 3: Import the candidates already in a job
If a job already has a backlog, start there. On the connection’s page, choose Import candidates, pick the Greenhouse job and the Hure role, and select who should be interviewed. Hure creates one interview per candidate, up to 200 per import, and Load more pages through bigger jobs. Anyone already interviewed for that role is skipped, so running the same import twice is safe.
Step 4: Start interviews from a stage
For new applicants, let the pipeline do the work. On the same page, add a trigger rule: pick the Greenhouse job, the stage, and the Hure role. A good first choice is the stage where you would otherwise book a phone screen.
Hure then shows a web hook URL and a secret. Paste both into Greenhouse under Dev Center, Web Hooks, for the event Candidate has changed stage. Copy the secret right away: Hure shows it once, and only a rotation replaces it.
From then on, when a candidate reaches that stage, Greenhouse notifies Hure, Hure checks the signature, creates the interview and sends the invitation. A candidate with no email address on file is skipped, since there is nobody to invite, and a candidate already interviewed for the role is never booked twice, even if Greenhouse sends the same event again.
Step 5: Read results in Greenhouse
Each finished interview produces a scorecard in Hure: a score for each competency on the role’s sealed rubric, each tied to a moment in the transcript. Hure posts the result to the candidate’s Greenhouse profile as an admin-only note with a link to the full scorecard. A person on your team reads it and decides who moves forward. Hure never rejects anyone.
What candidates experience
Candidates get an invitation with one link. They open it on a phone or laptop, with no app and no account, and start right away or pick a time. The interview is a live voice conversation of about 8 to 10 minutes, in their own language, and Hure follows up on what they say. Hure judges what candidates say, never how they look or sound. If they search for us before they start, our candidate page answers what they usually ask.
For the details of each step, see the Greenhouse integration page. The same setup works for Lever and Ashby.
Frequently asked questions
Which permissions does the Greenhouse API key need?
A Harvest API key with access to Candidates (read, and posting to a candidate's notes) and Users (read). Hure uses the list of users to pick who the result notes are posted as.
Can Hure move candidates to the next stage in Greenhouse?
Not today. Hure reads stage changes to start interviews and writes each result back as a note. Your team reads the scorecard and moves the candidate forward in Greenhouse.
What do candidates receive?
An invitation with one link. They take a live voice interview of about 8 to 10 minutes from a phone or laptop, with no app and no account, right away or at a time they pick.
Do I need Greenhouse to use Hure?
No. You can add candidates to a role by hand in the Hure console. The Greenhouse connector is for teams that already run Greenhouse and want candidates to flow in from there.


