Integrations: calendars, ATS, and CSV import

Connect Google Calendar, Microsoft 365, Greenhouse, and Lever, or run standalone with CSV import. Scoped, revocable access with encrypted credentials.

Updated July 17, 2026

Calendars

Interview scheduling is only as good as its calendar data, so Cadence connects to each interviewer's real calendar with individually authorised, revocable OAuth connections.

Mixed teams work naturally: a panel can span one interviewer on Google and another on Microsoft 365, and the availability intersection just works.

Applicant tracking systems

Keep your ATS as the system of record while Cadence runs scheduling and candidate communication. Candidates sync in, and scheduling outcomes write back, so nobody re-keys data.

No ATS? CSV import

Teams without an ATS bring candidates in with CSV upload: per-row validation with clear error reporting, injection-safe parsing of untrusted files, encrypted storage of the uploaded file while the import runs, and provenance recorded on every imported candidate. It is the fastest way to get a real pipeline into Cadence in an afternoon.

How connections are secured

Every integration credential, OAuth tokens and API keys alike, is encrypted at rest, scoped to the workspace, and revocable in one action. Access uses the narrowest scopes each provider offers for the job, connection health is surfaced in the app, and a reconnect is requested the moment a provider reports a token problem, before it breaks an interview. Integration activity lands in the audit log keyed by internal identifiers, in line with the practices in privacy-safe recruiting.

Start connecting

See the full feature overview for how integrations power scheduling, no-show defense, and status pages, or sign in from the Cadence home page to connect your first calendar.