Clera home
·Dashboard
Clera for Ashby

Meet Clera's candidates
without leaving Ashby

They arrive on your jobs in the right stage, with Clera as the source, and every pass or hire syncs back.

Book a demo

Connect with an Ashby API key. No engineering needed.

Senior Backend EngineerOpen
  • New5
  • Recruiter screen2
  • First interview2

  • Maya R.

    Senior Engineer · Series B fintech

    No flags

  • Alex C.

    Backend Engineer · Remote

    Likely fake

  • Jordan P.

    Software Engineer · Seed devtools

    No flags

  • Leo M.

    Platform Engineer · Series A logistics

    No flags

  • Nina K.

    Backend Engineer · Seed health

    No flags

Two-way sync, nothing to copy over

What you do in Ashby updates Clera, and what Clera does shows up in Ashby.

Clera to Ashby

  • New applications

    People you want to meet, in the right stage of the linked job

  • Source set to Clera

    Your Ashby reports count them

  • Moved to first interview

    After the intro, so nobody updates the stage by hand

  • Archived with a reason

    When you pass or they withdraw

Ashby to Clera

  • Open roles and stages

    You never set up a job twice

  • Stage changes and hires

    Clera knows where each person stands

  • Fake profile checks

    On your applicants, before you book a call

  • Live updates

    Or every hour if the key can't set up a webhook

Set up in three steps

No new tool for your team. Everything shows up in Ashby.

  1. 1

    Create a key in Ashby

    Admin, then Integrations, then API Credentials. Tick the permissions Clera asks for.

  2. 2

    Paste it into Clera

    Clera checks every permission on the key and tells you exactly which box is missing.

  3. 3

    Link your roles

    Pick the jobs Clera works on. People and flags show up in that pipeline from then on.

Ashby key5 of 6 permissions
  • Read on Jobs
  • Read on Interviews
  • Read on Candidates
  • Write on Candidates
  • Read on Hiring Process Metadata

    This key can't read your archive reasons, so passing on someone in Clera won't archive them in Ashby. To turn that on, tick Read on Hiring Process Metadata for this key in Ashby. No need to reconnect.

  • Write on Api Keys

Not on Ashby?

Clera works with 50+ other hiring tools the same way, or moves you to a new one without losing a profile.

  • Greenhouse
  • Lever
  • Teamtailor
  • Recruitee
  • Workable
  • SmartRecruiters
See every integration

Questions about Ashby

Read on Jobs, Interviews and Candidates, and Write on Candidates. Read on Hiring Process Metadata lets passes in Clera archive the candidate in Ashby with a reason. Write on Api Keys turns on realtime updates; without it Clera checks Ashby every hour.

The people you choose to meet, as applications on the job you linked, with Clera as the source. A move to first interview after the intro, and an archive with the reason when you pass or they withdraw. Nothing else.

No. Your team keeps working in Ashby. Clera candidates, their status and any fake flags show up in the same pipeline.

Delete the API key in Ashby. Clera loses access straight away.

Yes. Clera works with Greenhouse, Lever, Workable and 50+ more hiring tools, and can move you to a new one without losing a profile. Book a demo and we'll connect yours.

Get started

Connect Ashby on a call.

Drop your work email and pick a time. In 15 minutes we connect the key together and link your first role.

Book a demo