Integrations — ATS
Twynit + Ashby
Teams choose Ashby for clean data and good reporting. Twynit respects that: it works alongside Ashby, adds the evidence-first judgment layer on top, and keeps every record straight in both systems.
Your analysts keep their dashboards. Your recruiters get their mornings back.
What your Twin does with it
- Imports and continuously syncs your Ashby pipeline into evidence-ranked searches
- Prepares one decision at a time on your Desk — verdict, evidence, confidence, consequence
- Writes every approved action back to Ashby, named and undoable for 72 hours
- Keeps your Ashby reporting truthful — stage data stays current without manual updates
- Remembers every person you've met, across both systems, in one talent memory
Every write-back is named, logged, and undoable for 72 hours. If one fails, it surfaces as a warning with a retry — never silently.
How the connection works
01
Connect and import
Connect Ashby from Settings in about a minute. Your Twin imports your existing candidates and open roles in the background, narrating progress as it reads. People are matched and de-duplicated, so the same human across two systems becomes one person with one history.
02
Confirm the mapping
Before anything goes live, your Twin shows you how Ashby jobs map to Twynit searches and asks you to confirm — one review card, not a settings maze. Nothing syncs until you approve the mapping.
03
Work anywhere, both systems agree
From then on, sync runs both ways. A stage change in Ashby appears in your Twynit timeline as a receipt; a decision in Twynit writes back to Ashby and names its destination: "Updated Ashby: Sarah → Onsite." Conflicts follow the policy you set, and every resolution leaves a receipt showing both sides.
Questions
Does Twynit replace Ashby?
No. Twynit works alongside Ashby. Ashby stays your system of record; Twynit is where the judgment work happens — reading, ranking, evidence, decisions. Everything you decide writes back, so your team and your reporting keep working exactly as before.
What exactly gets written back?
Stage changes, decisions, notes, and scheduling updates — each one recorded with a visible receipt that names the destination. If a write-back fails, it surfaces as a warning with a retry, never silently.
What if a sync does something I didn't want?
Every action your Twin takes is undoable for 72 hours from its receipt. Undoing an automated action also demotes that action type back to ask-first mode — your Twin asks what went wrong, and the answer becomes a remembered preference.
Keep Ashby. Add the judgment.