What the integration does
Two directions:
- Inbound: scheduled interviews from your ATS become InterviewWatch interviews, with the candidate, role, and timing already filled in.
- Outbound: when a monitored round finishes, the signed integrity report goes back onto the candidate's record in your ATS.
Connecting an ATS also takes the built-in pipeline out of the way: scorecards live in your ATS, and duplicating them here would leave two copies of the same notes. Everything on the ATS page is admin only.
Connecting Greenhouse
Open Applicant tracking system under Integrations. What you see depends on how your deployment is configured:
- Install with Greenhouse
If the hosted install is available, this is one click: you authorise InterviewWatch inside Greenhouse and come back connected. No keys to paste.
- Your own Harvest credentials
Otherwise, create a Harvest API credential in Greenhouse (Configure, Dev Center, API Credentials) and paste the client ID and client secret. The connection then authenticates as your own Greenhouse app rather than a shared one.
Add the on-behalf-of Greenhouse user id too if you want write-backs: Greenhouse requires it to attach notes and files.
- Sandbox
Non-production deployments offer Connect sandbox ATS, which connects instantly with seeded test candidates and no credentials. Useful for a demo or a dry run.
Syncing interviews
Sync now imports scheduled interviews. The result lists each one and what happened to it: created, updated, existing, or cancelled. Two things to look for in that list:
- Needs info: the round arrived without a meeting link or without an owner. Fill it in on the interview row before the interview happens.
- Link pushed: the candidate join link was delivered back to the ATS record, so the candidate gets it through your normal flow.
Export CSV downloads the synced interviews if you want them in a spreadsheet.
The real-time webhook
Polling alone means changes land at the next sync. To make them instant, copy the webhook URL shown on the ATS page and paste it into Greenhouse under Configure, Dev Center, Web Hooks for the Interview scheduled, Interview updated, and Interview deleted events.
With that in place, a rescheduled or cancelled interview reconciles as it happens instead of waiting.
Report write-back
When a monitored interview completes, the report is pushed back to the candidate in your ATS. Exactly what can be written depends on the provider's capabilities, and the connected status line spells out what yours supports: notes, attachments, verdict tags, or scorecards.
You can also push manually: on a completed round that came from the ATS, use Export to ATS in the ⋯ menu (it reads Re-export to ATS once it has been sent).
ATS-managed mode
The toggle on the ATS page: auto-create interviewer accounts from the ATS and auto-assign their interviews.
With it on, interviewers named on a synced interview get an InterviewWatch account created for them and the round assigned automatically, so nobody has to send manual invites. With it off, synced rounds arrive unassigned and an admin picks the owner.
Turn it on when your ATS is the source of truth for who runs which interview, which is the usual case for larger teams.
Sync health and reconnecting
The connected panel shows the last sync time, how many interviews were created, updated, or unchanged, and how many are linked in total. If a sync fails, the error is shown in its place.
A failure almost always means the ATS token expired or was revoked. Reconnect with fresh credentials to restore syncing. Interviews already imported are unaffected while it is broken.
Disconnecting
Disconnect stops syncing and stops write-backs. Interviews already imported stay, with their reports. Reconnecting later resumes from the current state rather than replaying history.