Integrations — ATS
Twynit + Greenhouse
Greenhouse is a strong system of record. Twynit adds the layer it was never built to be: a Twin that reads every application against your scorecard, prepares each decision with evidence, and keeps Greenhouse updated without you touching it.
Connect once. Your Twin imports your existing pipeline, asks you to confirm how jobs map to searches, and from then on the two systems agree — every change mirrored, every write-back receipted.
What your Twin does with it
- Imports your Greenhouse pipeline and reads every candidate against your scorecard, with the evidence shown
- Queues decisions to your Desk when screening or new applications arrive
- Writes stage changes back: "Updated Greenhouse: Sarah → Onsite" — named, logged, undoable for 72 hours
- Mirrors external changes into your timeline: "Greenhouse moved Devon to Rejected — mirrored here"
- Finds people already in your Greenhouse history who match a new search before it even publishes
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 Greenhouse 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 Greenhouse 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 Greenhouse appears in your Twynit timeline as a receipt; a decision in Twynit writes back to Greenhouse and names its destination: "Updated Greenhouse: Sarah → Onsite." Conflicts follow the policy you set, and every resolution leaves a receipt showing both sides.
Questions
Does Twynit replace Greenhouse?
No. Twynit works alongside Greenhouse. Greenhouse 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 happens to candidates already in Greenhouse?
They're imported into People, Twynit's talent memory — de-duplicated, with their history intact. When you open a new search, your Twin checks them first: the strongest sourcing channel is usually the people you've already met.
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 Greenhouse. Add the judgment.