Screening tools that integrate with Ashby: resume screening, async interviews, and assessments

Ashby is very good at the thing it is built for. The pipeline is clean, the analytics are genuinely best in class, and once a candidate is in a stage you can see everything about how they got there. What Ashby does not do, and does not claim to do, is tell you which of the four hundred people who applied on Tuesday are worth an hour of your week.

That gap is why “screening that works with Ashby” is one of the most common searches we see from teams already happily running Ashby. They aren’t shopping for a new ATS. They want a layer in front of it.

The trouble is that almost every screening vendor will tell you they integrate with Ashby, and the word is doing a lot of quiet work. Some mean a native connection through Ashby’s assessment partner API. Some mean a Zapier hop. Some mean an API key and a weekend of your engineer’s time. All three get described the same way on a pricing page.

So here is the version I wish someone had written for me: what Ashby actually exposes to a screening partner, what each of the three screening methods can and cannot put on a candidate’s profile, and the question that separates a real integration from a badge on a website.

What “integrates with Ashby” actually means

Ashby has a specific, documented slot for tools like this. It’s called an assessment partner, and it works differently from a general-purpose data sync.

Once a partner is connected, the recruiter adds it as an activity on a job’s interview plan, on whichever stage should do the screening. From then on, four things move between the systems:

• The list of available screenings. Ashby asks the partner what screenings exist on your account, and they appear in a dropdown when you add the activity. You pick the one that matches the role.
• The instruction to screen someone. When a recruiter sends the assessment from a candidate’s Ashby profile, Ashby tells the partner to screen that specific person. The partner emails the candidate directly, so nobody in your team has to chase a link.
• The status, twice. The partner posts back “In progress” when the candidate starts, and “Completed” when they finish, so the stage in Ashby is live rather than a guess.
• The result itself. This is the part that varies wildly between vendors, and it’s the part worth interrogating.

There’s no webhook URL to configure and no middleware in between. Setup is a two-key handshake: you create an API key in Ashby under Admin → Integrations → API Keys and choose the partner from the Integration Partner list, paste that key into the partner’s product, then paste the key it gives you back into Ashby under Admin → Integrations → Integrations. Ashby pre-fills the API scopes for listed partners, so you aren’t guessing at permissions.

The whole thing takes under ten minutes and needs Ashby admin access. Then your recruiters never leave Ashby again.

A Zapier connection can approximate some of this. It cannot put a scored, explained result inside the assessment block on the profile, because that block belongs to the partner API. If reading results without switching tabs is the reason you’re doing this at all, that distinction matters more than it sounds like it should.

Resume screening for Ashby

Start with the honest part, because it’s the one nobody volunteers.

Resume screening is the method that fits Ashby’s assessment slot least neatly. The assessment payload carries a score, and a resume screen produces something more like a criteria breakdown: this candidate has strong evidence for four of your six criteria, some evidence for one, none for the last, and here are the lines in the resume each judgement came from. That’s the useful output. It does not compress into a single number without throwing away the thing you wanted.

So in Truffle’s Ashby integration, resume screening runs on the Truffle side, and what Ashby gets is the completed status and a View in Truffle link straight through to the full breakdown. I’d rather say that plainly than let you find out in week two.

That leaves two sane patterns, and which one you want depends on where your applicants come from.

If applicants arrive in Ashby first, use Ashby for the pipeline and reach for resume screening only on the roles where volume is genuinely unmanageable. You’ll be clicking through to read the detail, and for a role with thirty applicants that isn’t worth the context switch.

If the volume is the problem, put the screening in front of Ashby instead of behind it. Point the job posting at a hosted apply page, let resume screening run on every applicant as they arrive, and move the shortlist into Ashby. The criteria come from the job description you already wrote, and you can edit them before anything is scored.

The second pattern is the one high-volume teams end up on, and it’s worth saying that it slightly changes what Ashby is for. Ashby stops being the place applications land and becomes the place candidates you’ve decided to take seriously land. Most teams find that an improvement. Some hate it. Worth knowing which you are before you build it.

One thing that holds in both patterns: nothing is auto-rejected. Scoring ranks the pile and shows the evidence. The decision about who moves forward stays with you, which is also the answer to the compliance question your legal team will eventually ask.

Async interviews that work with Ashby

This is the method that round-trips cleanly, and if you only wire up one thing, wire up this one.

A one-way video interview asks the candidate a fixed set of role-specific questions, which they record on their own time, on any device. No scheduling, no calendar tetris, no thirty-minute call to establish something you could have learned in four minutes. For a role pulling a hundred applicants, replacing the first-round phone screen with an async interview is the single biggest hour-recovery available to a small team.

Here’s what actually lands on the Ashby profile when the candidate finishes:

• The status, set to Completed, with the finish date.
• A match score for the video screening, with a match level.
• How many questions were asked and how many the candidate answered, which is more diagnostic than it sounds. A candidate who answered two of six is telling you something.
• A written summary of how they performed, which is the reasoning behind the score rather than the score on its own.
• A link through to the full screening, including the recordings, for when the summary makes you want to watch.

That last point is the difference between a score you trust and a score you argue with. A number by itself invites the question “based on what?” and you can’t answer it from inside Ashby. A summary that says which answers carried the score, with the recordings one click away, you can act on during a stand-up.

If your team is new to async interviews, the objection you’ll hear internally is that candidates hate them. Our experience is that it depends almost entirely on length and framing. A ten to fifteen minute interview with four to six questions, sent with a clear explanation of why, completes well. A forty-minute one does not, and deserves not to.

Talent assessments that integrate with Ashby

Assessments are the third slot, and the one where the writeback design gets opinionated.

A screening assessment produces a lot of underlying detail: trait-level results, per-scenario judgements, preference alignment across several dimensions. Dumping all of that onto an Ashby profile would make the profile unreadable, so what posts back is a rolled-up assessment score of High, Mid, or Low, with the underlying scenario counts alongside it, and the link through for the full picture.

That rollup is a deliberate trade. It’s the right resolution for the decision you make inside Ashby, which is usually “does this person continue.” It is the wrong resolution for the decision you make before an interview, which is “what should I probe on.” For the second one you’ll want to open the detail, and that’s fine, because you’re doing it for four people rather than four hundred.

Three kinds are worth knowing apart, because they measure genuinely different things and the marketing around them tends to blur:

Personality assessments. Truffle’s is built on the International Personality Item Pool, a validated public-domain instrument measuring the Big Five traits. What you set is five traits with the trade-off of each direction shown, so you’re describing the work rather than picking a “good” profile. There is no profile marked best. Treat the result as a conversation starter for the interview, never as a reason to reject someone.

Work scenarios. These are situational judgement scenarios drafted for the specific role, each arriving with an approach already selected, which you accept, swap, or replace with your own. Candidates are scored on how closely their judgement aligns with the approach you chose. These are proprietary scenarios rather than a validated psychometric instrument, so read them as a measure of alignment with how you want the work done.

Environment fit. A preference-matching step built on realistic job preview principles. It surfaces where a candidate’s stated preferences line up with the actual conditions of the job, which is the thing that quietly drives early attrition in shift-based and field roles. Also proprietary rather than validated, and also diagnostic rather than decisive.

All three run about twelve to thirteen minutes for the candidate, which is the budget you have before completion rates start falling off a cliff.

How to connect Truffle and Ashby

The full walkthrough with screenshots is in the Ashby setup guide, and the Ashby integration page has the summary. The short version, so you can judge the effort before you start:

1. In Ashby, go to Admin → Integrations → API Keys, create a key, and select Truffle as the Integration Partner. Ashby pre-fills the scopes. Copy the key on the last step, because Ashby shows it once.
2. In Truffle, open Integrations → Ashby, click Connect, and paste the Ashby key. Truffle generates a key of its own and reveals it once.
3. Back in Ashby, go to Admin → Integrations → Integrations, find Truffle, and paste that key in. The connection is now live.
4. Per job, open the interview plan, add Truffle as an activity on the stage that should screen, and pick which screening to run from the dropdown.

You need Ashby admin access and a paid Truffle plan. On a trial the Ashby card shows as locked, which catches people out, so it’s worth knowing before you plan a Friday afternoon around it.

After that, sending a screening and reading the result both happen on the candidate’s Ashby profile. Cancelling the activity in Ashby disqualifies the application on the Truffle side, so the two systems don’t drift.

What to check before you pick any Ashby screening partner

If you’re evaluating more than one tool, these are the five questions that separate them, and only the first one usually gets answered on a website.

1. What is actually in the result payload? Ask for a screenshot of a completed record on a real Ashby profile. If a vendor can only show you their own dashboard, the integration is a status sync with extra steps.

2. Is there reasoning attached to the score? A match level with no explanation moves the argument rather than settling it. You want the summary on the profile and the source material one click away.

3. Who emails the candidate? If the partner sends the invite directly off the Ashby trigger, nobody on your team is chasing links. If your team has to send it, you’ve bought a scoring tool rather than a screening step.

4. What happens when someone is cancelled or moved? Pipelines change. Find out whether cancelling in Ashby cleans up on the partner side, or whether you’ll accumulate ghost screenings.

5. Does anything get auto-rejected? Ask directly, and get the answer in writing. Automated rejection is a legal exposure you do not want to inherit by accident, and any partner worth using will tell you plainly that ranking is theirs and the decision is yours.

Where this nets out

Ashby is a good enough ATS that replacing it to solve a screening problem would be a strange trade. Adding a layer that reads the pile, ranks it against what you actually asked for, and writes the reasoning back onto the profile you already work in is the cheaper move by a wide margin.

Just go in knowing which of the three methods round-trips fully and which one asks you to click through. One-way interviews and assessments post scores and summaries onto the Ashby profile. Resume screening lives one link away, which is the right trade at high volume and an annoyance at low volume.

Frequently asked questions about Ashby screening integrations

Does Truffle integrate with Ashby natively?

Yes. Truffle connects to Ashby through Ashby’s assessment partner API, with no Zapier or middleware in between. You create an API key in Ashby, paste it into Truffle, and paste the key Truffle generates back into Ashby. Setup takes under ten minutes and needs Ashby admin access plus a paid Truffle plan.

Does resume screening show up on the Ashby candidate profile?

Not as a score inside the Ashby assessment block. Resume screening produces a criteria-by-criteria breakdown rather than a single number, so it runs on the Truffle side and Ashby receives the completed status and a View in Truffle link through to the detail. One-way video interview match scores and rolled-up assessment scores do post onto the profile.

Can I run async video interviews from inside Ashby?

Yes, and this is the method that fits Ashby’s model best. Add Truffle as an activity on the job’s interview plan, send it from the candidate’s Ashby profile, and Truffle emails the candidate their link. When they finish, the match score, the number of questions answered, and a written summary of how they performed land back on the Ashby profile.

What do talent assessment results look like in Ashby?

They come back as a rolled-up score of High, Mid, or Low with the underlying scenario counts alongside it, plus a link through to the full detail. That resolution suits the continue-or-not decision you make in the pipeline. For interview prep, open the full result to see the trait-level and scenario-level breakdown.

Does the Ashby integration work on a free trial?

No. The Ashby integration is available on any paid Truffle plan, and on a trial the Ashby card shows as locked with an “Available on paid plans” label. Ashby’s own API access also sits on Ashby’s paid plans, so check with Ashby for current availability there. The 7-day Truffle trial still lets you test resume screening, one-way interviews, and assessments standalone with 30 credits and no card.

Will anyone be automatically rejected?

No. Truffle scores and ranks candidates against the criteria you set and shows the evidence behind each result. Nothing is auto-rejected, and every decision about who moves forward stays with your team.

Running Ashby and drowning in applicants anyway? Start the free trial, 30 credits and no card, and screen one real role end to end before you wire anything into your pipeline.