Infyva and Ashby: send the interview from a stage

At a glance

How you connect it

Ashby connects with an API key. There is no sign-in window. The connection covers the whole workspace, only an owner or admin can create it, and everyone on the team can import jobs afterward.

1. In Ashby, open Admin, then Integrations, then API Keys, and create a key.
2. Give it read access to jobs, candidates, applications and interviews, and write access to candidates and applications.
3. Make up a long random secret. In Ashby, add a webhook and paste that secret as its secret token.
4. In Infyva, open Settings, then Integrations, choose Ashby, and paste the key and the same secret. Use Test connection to check them.

The secret is required for Ashby, not optional. Infyva checks the signature of every webhook delivery with it and refuses unsigned ones, so nobody can fake an event to your workspace. The key and the secret are encrypted and never shown again.

What comes in from Ashby

Infyva lists your open jobs. Pick one and import it as a new Infyva job, or map it onto a job you already have. Import again whenever you like. Nobody is imported twice, because Infyva matches on the Ashby application, then the Ashby candidate, then the email address inside the job.

• The job description. Infyva reads the job's posting and uses it to write the interview questions. If there is no usable description, the job imports and resumes are parsed but not scored until you add one.
• The candidate. Name, email, phone, the LinkedIn and GitHub links on the profile, and the current interview stage. Only active applications come in.
• The resume. Infyva fetches the file when it needs it, reads it and scores it against the job.

Sending the interview from an Ashby stage

This is the part Ashby teams like most. In the job's stage mapping, choose the Ashby interview stage that should send the interview. When a candidate reaches that stage, the next sync or webhook sends them the Infyva invite. Candidates already at the stage are invited on the next sync, and each candidate is invited once. Your recruiters keep working in Ashby.

An automatic invite follows the same rules as a manual one. It uses a credit, it respects your company's AI hiring policy for the job's location, and it is skipped, with the reason in the sync log, when the Ashby record has no email address or the workspace is out of credits.

What goes back to Ashby

• Status. Interview status is added to the candidate in Ashby as an assessment status or a note.
• The result. When the report is ready, the candidate in Ashby gets the score out of 100, the band, each competency with its own score, the suggested next step, an integrity summary and a link to the full report.
• Stage moves. When you move a candidate in Infyva, Infyva changes the application's stage in Ashby to the matching one.

A report held for a person to review has no overall score, so nothing is sent rather than a made-up number. The recordings and the per-answer evidence stay in the Infyva report.

An example, start to finish

Say you hire a support lead and your Ashby job has the stages Applied, Recruiter screen, Hiring manager and Offer. You import the job, then pick Recruiter screen as the trigger stage. Jordan Lee is moved to Recruiter screen in Ashby. On the next webhook, Infyva sends Jordan the interview invite, and Ashby gets a note that the interview is on its way.

Jordan answers the questions that evening. Minutes later the report is ready, and the candidate in Ashby shows the score, the band, each competency and the report link. The recruiter reads the summary in Ashby, opens the report to hear one answer, and moves Jordan to Hiring manager in Ashby. Nobody retyped anything.

Stage mapping

Each job maps Infyva's stages (Applied, Screened, Interviewed, Offer, Hired and Rejected) to the interview stages on that Ashby job's plan. Leave a stage on "Match by name" and Infyva picks the closest Ashby stage name, or choose "Don't move in the ATS" to leave a stage alone. When nothing matches, Infyva moves nothing and writes the reason to the sync log.

How often it syncs

With the webhook in place, new applications and stage changes reach Infyva within about a minute. Mapped jobs also re-sync about every six hours as a backstop, and you can press Sync now at any time. Updates that Ashby cannot take right away are retried on their own for up to about nine hours, and the sync log lists every import, webhook and update so you can retry a failed one by hand.

What it does not do

• It does not put recordings or per-answer scores into Ashby. They stay in the Infyva report behind the link.
• It does not import closed jobs or applications that are no longer active.
• It does not hire, reject or decide anything. People make those calls.

Plans, credits and disconnecting

The Ashby connection is on Pro and Enterprise and is switched on during the 14-day Pro trial. It costs nothing extra, and interviews are paid in credits like any other. See pricing.

Disconnecting deletes the stored key, the queued updates and the Ashby links on your jobs and candidates. You can also remove imported candidates who never had an interview. Anyone who did have one stays, unlinked, because their results are your records.

On another system? See all integrations, or the Lever and Workable guides. To see the interview, watch the 30-second demo.