Connect Your ATS

Most companies already have an applicant tracking system, and nobody wants two of them. Stori is where you source people and watch them interview; your ATS is where the record lives. This integration joins the two: once an admin connects your ATS, every candidate card and candidate page in Stori gets a Send to your ATS action.

Sending a candidate does four things in your ATS:

• Creates the person, or finds them if they are already there and attaches them to the job instead of creating them twice.
• Puts them on the open job you choose.
• Attaches their resume when Stori has one.
• Records the source as Stori and writes a note with a link back to their Stori record, so anyone reading the ATS can get to the interview evidence in one click.

Nothing flows the other way. Stori never reads candidates out of your ATS and never changes anything except what you send.

System	What your admin creates
Greenhouse	A Candidate Ingestion API key (Dev Center → API Credential Management, type "Candidate Ingestion", partner "Custom") and the email of the Greenhouse user candidates should be recorded under
Lever	An API key with read and write on Opportunities, read on Postings and Users, and file uploads allowed
Ashby	An API key with Candidates (read and write), Jobs (read) and Organization (read)
Workable	An access token with the r_jobs, r_candidates and w_candidates scopes, plus your subdomain
SmartRecruiters	An API key from Apps & Integrations → Credentials
Teamtailor	An admin-scope API key with read and write
BambooHR	An API key from your name menu → API Keys, plus your subdomain
JazzHR	The API key under Settings → Integrations
Recruitee	A personal API token and your company ID
Workday	An API client for integrations with the Recruiting scope, a non-expiring refresh token and your country reference ID. Workday is in beta until a customer tenant has confirmed it

Every one of these is a credential you issue and can revoke in your ATS at any time. Stori stores it encrypted and never shows it back.

1. Go to Settings → Integrations → Your ATS.
2. Find your system and click Connect.
3. Paste the credential your admin created. Stori checks it against your ATS before saving anything; a wrong key is refused on the spot with the reason.
4. The card shows what the key can act as (for example the Greenhouse or Lever user candidates will be recorded under).

Only admins can connect or disconnect. Anyone on the team can send candidates once a system is connected.

From a job's Hiring board, use the send icon on any card. From a candidate's page, use Send to [your ATS] under Your ATS.

• If more than one system is connected, pick which one.
• Pick the open job in your ATS. The list is read live, and the job this Stori job last sent to is preselected.
• Click Send. The result stays on screen: created, already there and attached, or exactly what your ATS said if it refused.

Each send is logged. A candidate's page lists where and when they were sent, with a link to open them in your ATS.

The same two actions are available to any assistant connected to Stori: list_ats_jobs shows your connections and their open jobs, and send_candidate_to_ats sends a candidate. "Send the three people we liked to the Greenhouse backend req" is a sentence an assistant can finish.

• The card says "Needs reconnecting." Your ATS refused the key on the last call, usually because it was revoked or its permissions changed. Create a fresh key and click Reconnect.
• The job list is empty. Stori only lists open, published jobs. Check the job's status in your ATS.
• The send failed. The message is your ATS's own reason. The commonest ones are a missing required field on the ATS side (an email address, or in Workday the country) and a key without write permission on candidates.
• The resume did not attach. Some systems refuse files over a size limit or in an unusual format. The candidate is still created; the message says the resume was left off.