Skip to content

Ashby integration

Move the candidate in Ashby. Kendor sends the screen or the interview.

When a candidate enters the Ashby stage you choose, Kendor sends their coding screen, or a link to book a live coding interview. Status, result, a review link and the decision are written back to the application as fields, with notes, so recruiters see where things stand without leaving Ashby.

01

A stage you choose is the trigger.

Pick an Ashby job, one of its stages and a live Kendor screen. Recruiters keep working in Ashby; moving an application into that stage emails the candidate their screen.

  • A rule covers one job, or a stage name on any job
  • A rule for one job wins over one for any job
  • The invite lands on your Kendor roster, marked as sent from Ashby

02

Or book a live coding interview.

Point a stage rule at a live coding interview and give it weekly hours: the days, the times, a time zone and how many days ahead. When an application enters the stage, Kendor emails the candidate a link to book a time, and the interview's panel runs the session. The Kendor status field in Ashby follows along from Invited to Scheduled to Completed, with a note at each step.

  • Times never clash with the panel's other Kendor sessions
  • Declined, a no-show, or nothing booked before the hours run out: Ashby hears that too
  • Screened from Ashby earlier? A later live coding session leaves its notes on the same application
  • The roster, profile and interview show the Ashby job and stage, and warn when a write to Ashby fails

03

Signed webhooks. Duplicates ignored.

Ashby tells Kendor about stage changes through a webhook signed with a secret only your org and Ashby know. Kendor checks the signature on every request and rejects anything that doesn't match. If Ashby delivers the same change twice, the candidate still gets one invite.

  • Each org has its own webhook URL and secret, stored encrypted
  • A failed write to Ashby is retried for a day
  • No email address in Ashby? Kendor leaves a note instead of an invite

04

Set up with one API key.

Create an API key in Ashby and paste it into Kendor's integration settings. Where the key allows, Kendor registers the webhook and creates its five fields on the application, then shows a checklist of what's done. Anything the key can't do comes with the steps to finish it in Ashby.

  • Changed the key's permissions in Ashby? Check again
  • Replace the key any time; the webhook keeps working
  • Disconnecting removes the key and the rules; invites already sent stay valid

How it works

Ashby stays the system of record.

  1. Connect with an API key

    Kendor checks the key's permissions and sets up the webhook and its fields where the key allows.

  2. Map a stage to a screen or interview

    For one job, or a stage name on any job, choose which screen a stage sends or which live coding interview it books.

  3. Read results in Ashby

    Fields update as the candidate books, starts, finishes and is decided, with notes along the way.

Questions

Which plan includes Ashby?

Pro and Enterprise include it. Connect Ashby from Integrations in your dashboard.

Does Kendor work with other ATSs?

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

Can an Ashby stage book a live coding interview?

Yes. Point the stage rule at a live coding interview and set the hours candidates can book: weekdays, times, a time zone and up to 30 days ahead. The candidate gets an email to pick a time, and times already taken by the panel's other Kendor sessions aren't offered. If nothing is booked before the hours run out, Ashby hears Expired. Kendor doesn't read your calendars.

How much does Kendor write to Ashby?

Fields on the application (status, result, a review link and the decision), a note once a screen's result is in, and a note at each step of a live coding interview. Code, activity and reviewer notes stay in Kendor.

Do we have to move our jobs into Kendor?

No. Keep your jobs and pipeline in Ashby; Kendor runs the screens and interviews and reports back.

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.

Hiring at scale? Talk to us