Clera for Ashby: meet Clera’s candidates without leaving Ashby

Clera now works inside Ashby. The candidates Clera finds for you arrive on your Ashby jobs in the right stage, with Clera as the source. Every applicant gets a fake profile check before anyone books a call. And when you pass on someone or hire them in Ashby, Clera knows.

Your team doesn't learn a new tool. They keep working in the pipeline they already run.

Key takeaways

• Clera for Ashby connects with one Ashby API key. No engineering needed.
• Clera writes four things to Ashby: new applications, the source, a move to first interview after the intro, and archive reasons. Nothing else.
• Clera reads your roles, stages and hires, so you never set up a job twice.
• Applicants get checked for fake profiles inside the same pipeline. Nobody is rejected automatically.

Why build this inside Ashby?

Hiring managers live in their ATS. Every tool that sits next to it adds a tab, a login and a copy-paste step. The copy-paste step is where candidates go missing.

It usually goes like this. A great intro happens in one tool. The candidate never makes it into the ATS. Nobody updates the stage. The candidate waits, hears nothing, and takes another offer.

So we stopped asking teams to come to Clera. Clera for Ashby puts Clera's work where the decisions already happen. You see Clera's candidates next to your own applicants, in the same stages, with the same buttons.

What does Clera write to Ashby?

Clera writes very little, on purpose. Four things, and only these:

1. New applications. The people you choose to meet show up as applications on the job you linked, in the right stage.
2. The source. Each one is marked with Clera as the source, so your reports count them correctly.
3. A move to first interview. After the intro, Clera moves the candidate forward. Nobody has to update the stage by hand.
4. An archive with a reason. When you pass in Clera, or the candidate withdraws, Clera archives them in Ashby with the reason.

Everything else in Ashby stays yours. Clera doesn't touch your other applicants, your interview plans or your notes.

What does Ashby tell Clera?

The sync runs both ways. What you do in Ashby updates Clera.

• Open roles and stages. Clera reads your jobs from Ashby, so you never set up a role twice.
• Stage changes and hires. When you move someone or hire them, Clera knows where each person stands.
• Your applicants. Clera runs a fake profile check on the people who apply to your jobs, before you book a call.
• Live updates. With the right key permission, changes arrive in real time. Without it, Clera checks Ashby every hour.

This is the part that keeps candidates from getting stuck. Clera follows up with people based on where they really are in your pipeline, not on a stale copy of it.

How do fake profile checks work in Ashby?

Fake candidates are no longer a fringe problem. Gartner expects that by 2028, 1 in 4 candidate profiles worldwide could be fake (HR Dive on Gartner's July 2025 survey). In the same survey of about 3,000 job seekers, 6% admitted to taking part in interview fraud. They cluster on remote engineering roles, where nobody meets in person until the offer.

The fraud check inside an ATS can only compare your applicants with each other. Clera compares them with the hundreds of thousands of profiles it has seen and every fake it has already caught. A repeat fake gets flagged on their first application to you.

Clera looks at things like:

• Contact details shared by applicants under different names
• Emails that follow a generated pattern
• CVs that contradict LinkedIn
• LinkedIn profiles that don't exist
• Reports from other employers
• Matches against profiles Clera has already confirmed as fake

In Ashby, the result shows up as a flag on the applicant, with the evidence behind it. Nobody is rejected automatically. You see the flag and you decide what happens next. Real candidates don't upload a passport or take a selfie. The checks run in the background.

If you want the full picture, read how Clera catches fake candidates, or start with the six signs of fake job applicants.

How do you set it up?

Three steps. Or book a 15-minute call and we do it with you.

1. Create a key in Ashby. Go to Admin, then Integrations, then API Credentials. Tick the permissions Clera asks for.
2. Paste it into Clera. Clera checks every permission on the key and tells you exactly which box is missing.
3. Link your roles. Pick the jobs Clera works on. From then on, people and flags show up in that pipeline.

The key needs:

• Read on Jobs, Interviews and Candidates
• Write on Candidates
• Read on Hiring Process Metadata, so a pass in Clera can archive the candidate in Ashby with a reason
• Write on API Keys, which turns on real-time updates. Without it, Clera checks Ashby every hour.

To disconnect, delete the key in Ashby. Clera loses access straight away.

What changes for your team?

Not much, and that's the point.

Recruiters and hiring managers keep working in Ashby. Clera's candidates, their status and any fake flags appear in the same pipeline. Nobody copies a profile from one tool to another. Nobody has to remember to move a stage after an intro.

What changes is the pipeline itself. Clera's candidates come in with Clera as the source, so you can see what they turn into. Passes carry their reasons in both tools. And the applicants you already get are checked before anyone spends an hour on a call.

What if you're not on Ashby?

Clera works with Greenhouse, Lever, Workable and more than 50 other hiring tools the same way. It can also move you to a new one without losing a profile. See every integration.

Connect Ashby on a call

Bring your Ashby key. In 15 minutes we connect it together and link your first role. Set up Clera for Ashby.