Accounting & HR
Set up Lever (recruiting)
Connect Lever to make hiring searchable — job postings in full text, and the candidate pipeline with each opportunity's stage, headline and owner — so “who is in final round for the Berlin role” and “which postings are open in Sales” answer from the ATS itself. Read-only.
Before you start
- The credential is an API key, created by a Super Admin in Lever under Settings → Integrations and API → API Credentials → Generate New Key.
- Choose the read permissions for postings and opportunities only — nothing else is used. Copy the key right away; Lever shows it once.
- Only reads are ever issued — the key can never write to Lever.
- Lever → Settings → Integrations and API → API Credentials → generate a key with read permissions for postings and opportunities.
- Documents → Lever, paste the key.
- Choose access groups, Test, then Sync.
What comes in
- Published postings become documents in full text — the description and every list section of the ad, with state, team, location and commitment at the top. Only published postings are read; a posting's date is the day it was last updated.
- Opportunities become situated records: name, stage, headline, location, owner and the date added — stage and owner resolved to their names.
- An opportunity is not linked to the posting it applied to; its headline, stage and location stand in, which is what pipeline questions ask about.
- Only postings and opportunities are read — no interview feedback or notes.
Access
Lever exposes no per-record sharing to mirror, so the access groups chosen on this source decide who can ask, allow-only. Candidate data is personal data — pick access groups accordingly; a hiring-team group is the natural choice.
Postings are capped at 500 and opportunities at 3,000, and the sweep keeps the newest under each cap: Lever's own listing has no reliable newest-first order, so it over-fetches — up to twice the cap — and sorts by each row's latest activity or update stamp before cutting, rather than freezing the cap on whatever the API returns first. When a cap is hit the sync summary says so, and everything beyond it stays as already ingested rather than reading as deleted. An opportunity refreshes here when its last interaction moves, a posting when it is updated. Test lists published postings and reports how many are reachable; a wrong or deleted key makes it say Lever rejected the credentials, and a blank one asks you to set the Lever API key.
Last updated 20 Sep 2026