Connect your ATS

Connect Greenhouse or Ashby in a few minutes, so Elsin verifies their candidates and writes the result back.

Admins connect an ATS in Settings, under Integrations. It needs a plan with ATS write-back: Starter, Integration or Enterprise. Platform does not include it.

Greenhouse

  1. In Greenhouse, open Configure, Dev Center, API Credentials and create Harvest v3 credentials. Give them these permissions: candidate tags list and create, applied candidate tags list, create and destroy, and notes create.
  2. In Elsin, click Connect on Greenhouse and paste the client ID and secret. Add a Greenhouse user ID if you want notes posted as that user.
  3. Copy the webhook address and secret Elsin shows. The secret is shown once.
  4. In Greenhouse, open Configure, Dev Center, Web Hooks. Add one for Candidate or Prospect Applied, and one for Candidate Stage Change, both with that address and secret.
  5. Back in Elsin, press Test connection. Saving the keys does not test them on its own.

Ashby

  1. In Ashby, open Admin, API Keys and create a key with candidate read and write access, plus API Keys: Write.
  2. In Elsin, click Connect on Ashby and paste the key. Elsin adds the Application Submitted and Candidate Stage Change webhooks itself.
  3. Press Test connection.

Without API Keys: Write, Elsin shows a webhook address and a secret, shown once. In Ashby, open Admin, Webhooks. Add one for Application Submitted and one for Candidate Stage Change, both with that address and secret.

The stage change webhook matters. Elsin only sends the verification email when a candidate moves past screening in your ATS, so without it candidates are scored but never asked to verify.

What happens next

Each new applicant arrives as an Elsin candidate under an unpublished copy of the job, and is scored straight away. Their first tag, such as Elsin: Low risk, is written back within minutes. The full flow is in Greenhouse and Ashby.

Lever and Workable

Both connect from the same screen, under Applicant tracking. See Lever and Workable for the steps and what differs.

The ATS connections are tested against recorded sample events from each system, not yet against live customer accounts. Run Test connection, then move a test candidate through a stage and check the tag appears.