Skip to content

Greenhouse integration

Move the candidate in Greenhouse. Kendor takes it from there.

When a candidate enters the Greenhouse stage you choose, Kendor emails them a coding screen or a link to book a live coding interview. Every step, from the invite to your decision, lands as a note on the Greenhouse application, so recruiters see where things stand without leaving Greenhouse.

Start hiringSee pricing

01

A stage sends a screen or a live coding interview.

Pick a Greenhouse job, one of its stages, and what it sends: a live Kendor screen or a live coding interview. Moving an application into that stage emails the candidate their screen, or a link to book a time within the weekly hours you set on the rule.

  • A rule covers one job, or a stage name on any job; one job wins
  • Bookable times avoid the panel's other Kendor sessions
  • Not booked in time? The invite expires and Greenhouse gets a note

02

A note on the application at every step.

Kendor writes back as notes, one per milestone: invited, the booked time or the submission with a review link, the result, the decision, or an invite that was cancelled or expired. A candidate screened from Greenhouse who is later invited to a live coding session gets those notes on the same application.

  • Each note is written once, visible to everyone who can see the candidate
  • A note Greenhouse refuses is retried for a day
  • In Kendor, the roster and profile show the Greenhouse job and stage, and what Greenhouse last heard

03

Set up with API credentials and one web hook.

Create Harvest V3 API credentials in Greenhouse with three scopes and paste the client ID and secret into Kendor. Greenhouse can't create web hooks through its API, so Kendor shows you an endpoint URL and a secret key to add as a “Candidate has changed stage” web hook. A checklist shows what's in place.

  • Every stage change is signed; a request that doesn't match is rejected
  • The same stage change delivered twice still sends one invite
  • Replace the credentials any time; the web hook URL and key stay the same

How it works

Greenhouse stays the system of record.

  1. Connect with API credentials

    Paste a Harvest V3 client ID and secret, then add the web hook Kendor shows you.

  2. Map a stage to a screen or live coding

    For one job, or a stage name on any job, choose what the stage sends. A live coding rule carries the hours candidates can book.

  3. Follow along in Greenhouse

    A note lands on the application as the candidate is invited, books, submits and is decided.

Questions

Which plan includes Greenhouse?

Pro and Enterprise include it. An owner connects Greenhouse from Integrations in your Kendor dashboard, with a Site Admin in Greenhouse to create the credentials and the web hook.

Why notes and not custom fields?

Greenhouse replaces an application's custom fields as a set, so writing Kendor's could clear yours. Kendor adds one note per step instead, each written once and visible to everyone who can see the candidate. The code and the full review stay in Kendor, behind the review link.

How does a candidate book a live coding interview?

The stage rule carries weekly hours: days, a time range, a time zone and how many days ahead. The candidate gets an email to pick a time within them, and times that clash with the panel's other Kendor sessions aren't offered. If nothing is booked in time, the invite expires and Kendor notes it on the application. The offered hours don't check the panel's calendars.

Does Kendor work with other ATSs?

Yes. Ashby and Lever work the same way: a stage you choose sends the screen or the live coding interview, and Kendor writes back to the application. Without an ATS, you invite candidates directly. If you use another ATS, tell us — it shapes what we build next.

Read the docs

More of Kendor

All features

Run your next screen on Kendor. Read what the code says.

Create your workspace, import a repository or start from a template, and send your first screen today.

Start hiringSee pricing
Hiring at scale? Talk to us