How to start AI interviews automatically from Ashby stages

Set up Hure so a candidate who reaches a stage in Ashby gets an AI voice interview invitation on their own, with the result posted back to their Ashby profile.

The Hure team4 min read
Off-white ceramic steps with a green sphere on the top step, and a slim arc curving down to an amber bead

The best moment to interview a candidate is right after your team decides they are worth a conversation. In Ashby, that decision is a stage change. This guide connects the two: when a candidate reaches a stage you choose, Hure, an AI voice interviewer, sends them an invitation on its own, interviews them, and posts the result back to their Ashby profile. Nobody books a call.

Integrations are enabled per team during early access. If you run Ashby and want this switched on, request access.

How it works

  1. A candidate moves to a stage in Ashby, by hand or through your own Ashby automation.
  2. Ashby sends a signed Candidate Stage Change webhook to Hure.
  3. Hure checks the signature and looks for a rule that matches the job and the stage.
  4. Hure looks up the candidate’s email with your API key, creates the interview on the role the rule names, and sends the invitation.
  5. When the interview is done, Hure posts the result to the candidate’s Ashby profile as a note, with a link to the full scorecard.

Hure answers Ashby right away and does the lookups in the background, so a slow moment on either side is retried by Hure instead of being lost.

What you need

  • An Ashby admin who can create API keys and webhooks.
  • A role in Hure whose rubric your team has sealed. Rules only point at sealed roles, so every candidate for a role is interviewed and scored against the same rubric version.

Step 1: Create an Ashby API key

In Ashby, go to Admin, API, API Keys and generate a new key. Hure uses it to list your jobs and stages, look up candidates’ emails, import candidates and post results back.

Step 2: Connect Ashby in Hure

In the Hure console, open Integrations, choose Ashby and paste the key. Hure checks it with Ashby before saving it, and stores it encrypted.

Step 3: Add a trigger rule

On the connection’s page, add a rule. Pick the Ashby job, then the stage, then the Hure role. Hure reads the jobs and stages from your Ashby account, so you pick from your real pipeline. Each rule reads as a plain sentence: when a candidate reaches this stage of this job, interview them for this role. A connection holds up to 20 rules.

Step 4: Create the webhook in Ashby

Hure shows the webhook URL for this connection. In Ashby, go to Admin, API, Webhooks, create a webhook of type Candidate Stage Change, and paste that URL. Ashby then gives you a secret token: copy it back into Hure. Ashby signs every request with it, and Hure rejects anything that does not carry a valid signature.

Step 5: Move one candidate and watch

Move a test candidate into the stage. Shortly after, the interview appears in Hure and the invitation goes out. Some details worth knowing:

  • No email, no interview. Ashby’s stage-change event does not include the candidate’s email, so Hure looks it up. A candidate with no email on file is skipped, since there is nobody to invite.
  • No double booking. A candidate already interviewed for the role is never booked again, even if Ashby sends the same event twice.
  • Other events are ignored. Stage changes that no rule matches are acknowledged and dropped, so Ashby does not keep retrying them.

Candidates already in the stage

Rules act on stage changes after you set them up. For candidates already sitting in a job, use Import candidates on the same connection: pick the job and the role, select the candidates, and Hure creates up to 200 interviews per import.

Results back in Ashby

Each finished interview produces a scorecard in Hure, with a score for each competency on the role’s rubric, each tied to a moment in the transcript. Hure posts the result to the candidate’s Ashby profile as a note with a link to the full scorecard. A person on your team reads it and decides who moves forward.

For the full setup reference, see the Ashby integration page. The same rules work with Greenhouse and Lever, and our Greenhouse guide walks through imports in more detail.

Frequently asked questions

Where do I create the Hure webhook in Ashby?

In Ashby under Admin, API, Webhooks. Choose the Candidate Stage Change type, paste the webhook URL that Hure shows on the connection's page, then copy Ashby's secret token back into Hure.

What happens if Ashby sends the same stage change twice?

Hure never books a candidate twice for the same role, so a repeated or retried webhook creates no second interview and sends no second invitation.

Can one Ashby connection have several rules?

Yes. Each connection holds up to 20 rules, each naming an Ashby job, a stage and a Hure role. If one rule points at a role that is no longer available, that rule is skipped and the others keep working.

Do candidates already past the stage get an interview?

Rules act on stage changes from the moment you set them up. For candidates who were already in the job, use Import candidates on the same connection to interview them in bulk.