Accounting & HR
Set up Ashby (recruiting)
Connect Ashby to make hiring searchable — job postings in full text, and candidates with their applications, each carrying its current stage and linked to its candidate — so “where is the Head of Sales search” and “which applications came in through referrals” answer from the ATS itself. Read-only.
Before you start
- The credential is an API key, created by an Ashby admin under Admin → Integrations → API keys → New API key.
- Choose the read permissions for jobs, candidates and applications only — nothing else is used. Copy the key right away; Ashby shows it once.
- Every Ashby API call is technically a POST, but only read operations are ever issued — nothing is created or changed.
- Ashby → Admin → Integrations → API keys → create a key with read permissions for job postings, candidates and applications.
- Documents → Ashby, paste the key.
- Choose access groups, Test, then Sync.
What comes in
- Job postings become documents in full text — the whole ad, with status (listed or unlisted), department, team, location and employment type at the top. Listed and unlisted postings both come in; a posting's date is the day it was last updated, or else its publish date.
- Candidates become situated records: name, email, company, position and the date added.
- Applications link to their candidate and carry the current interview stage, status, application date and source; a candidate's own record shows how many applications they have and the date of the latest.
- A posting's compensation block is never read — pay figures stay out entirely.
- The recruiting team — Ashby's own users, never candidates — is importable as accounts from this source (see “Import your team”).
Access
Ashby 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, candidates and applications at 3,000 each. Anything past a cap is left off that sync rather than reading as deleted — the sync summary says which cap was hit — and it catches up once the account is back under the cap. Every Ashby API call is a POST by design, so an error can arrive inside an otherwise successful reply; the source reads it and reports it as an Ashby error with Ashby's own message, never a raw body. Test lists job postings and reports how many are visible; a wrong or deleted key makes it say Ashby rejected the credentials, and a blank one asks you to set the Ashby API key.
Last updated 20 Sep 2026