Interview scheduling in Greenhouse works through connected calendars: Greenhouse can suggest slots automatically, send candidates a self-schedule link, and stays in sync via calendar integrations, but several limits apply (30-day window, 24 hours' notice, one-stage automation only for single interviews). You only need an add-on where those limits cost you real coordinator time. This page shows how Greenhouse scheduling works, where the effort comes from, how an external add-on connects (API and webhooks), and how to calculate whether it pays off.
Which questions this page answers
- How does interview scheduling work in Greenhouse, and is it automated?
- Which Greenhouse features exist: automated scheduling, self-scheduling, calendar integrations?
- What are the documented limits?
- Where does the manual coordination effort come from?
- How does an external add-on talk to Greenhouse (API, webhooks)?
- What does it save? A worked example with stated assumptions.
- What about data protection?
How scheduling works in Greenhouse
Greenhouse does not host its own primary calendar. According to its scheduling model, it compiles changes from interviewers' calendars into a source of truth and pushes updates to candidates by email. Three things must be in place: a calendar file from the interviewer, an authenticated user whose email Greenhouse recognises, and the interview kit URL that identifies candidate and interview. Google Calendar and Outlook 365 integrations handle much of this automatically; other clients need manual .ics uploads.
On top of that sit three scheduling paths:
- Manual scheduling from the candidate profile, best when details are still open.
- Automated scheduling: Greenhouse searches the calendar for the best time slots using interviewers' availability, working hours, interview limits and buffer time. The recruiter reviews the suggestions and sends invites. The candidate has to accept before the interview shows as scheduled.
- Candidate self-scheduling: the recruiter sends a self-schedule request with interviewers, length and calendar; the candidate picks one slot. Since the November 2025 release, one request can include several interviewers, with slots shown only when all are free.
Step by step: scheduling an interview with automated scheduling
- Open the candidate, click Automated scheduling (for several interviews in one stage: Schedule All, then Automated scheduling).
- Add interviewers by name, group or hiring-team role. Default interviewers from the interview plan are suggested automatically.
- Review the suggested slots. If the candidate submitted availability, suggestions stay within it.
- Add location and video conferencing, choose one email template for all invites or one per interview.
- Send the invites to interviewers and finish in Google Calendar or Outlook. Leave before sending and the interviews are not scheduled.
Prerequisites per Greenhouse: Job Admin permission or higher, the new subscription tiers (Core, Plus, Pro), and a connected calendar using the primary email address, not an alias. Check your own plan before planning around any feature.
The documented limits (and what they mean in practice)
| Limit (Greenhouse documentation) | Effect on your process |
|---|---|
| Suggestions and self-schedule slots only up to 30 days ahead | Long lead times (executive hires, relocation) still need manual handling |
| Self-schedule: at least 24 hours' notice; default hours Mon-Fri 9:00-17:00 in the interviewer's time zone if none set | Fast-turnaround and cross-time-zone interviews depend on clean working-hours data |
| Stage-transition automation sends self-schedule requests only for single-interview stages | Multi-interview stages and panels stay semi-manual |
| Groups and roles: only members with connected calendars count; groups over 50 connected members return an error | Fewer slots than expected if interviewers never connected their calendar |
| Interviewers at their interview limit appear lower in the list instead of being excluded | Someone still has to judge whether to use them |
| The documentation does not describe what happens on a decline | Rescheduling logic needs a defined owner (see below) |
Source: Greenhouse Support articles linked above, read October 2026.
Where the coordination effort actually comes from
Seeing availability is rarely the bottleneck. The effort sits in the loop around it: a panel member declines, a candidate asks to move, an interviewer never connected a calendar, the candidate does not accept the invitation, or the status in the ATS lags behind the calendar. Because Greenhouse treats the calendar as the source of truth, every change starts outside Greenhouse.
Survey figures give a feel for the scale, but they come from vendors with an interest. A 2019 Cronofy and JobAdder survey of 272 external recruiters found that 60 % had to send three or more emails or make three or more calls to schedule one interview. Treat such numbers as indicative and measure your own: pull ten recent interviews and count the touchpoints.
Worked example: what coordination costs per week
Assumptions (replace with your own numbers): 40 interviews per week, 30 one-on-ones and 10 panels; 5 minutes per touchpoint (email, message, calendar fix); 3 touchpoints per one-on-one, 6 per panel; loaded cost 45 € per hour; 46 working weeks.
| Item | Calculation | Result |
|---|---|---|
| One-on-ones | 30 x 3 x 5 min | 450 min |
| Panels | 10 x 6 x 5 min | 300 min |
| Coordination per week | 750 min | 12.5 h |
| Share automated (assumption) | 60 % | 7.5 h per week |
| Saving per year | 7.5 h x 46 weeks x 45 € | about 15,500 € |
If native Greenhouse automation already removes half of that, the add-on's share shrinks accordingly. The honest rule: if you run fewer than about 10 interviews per week, or mostly single-interview stages inside the 30-day window, native Greenhouse scheduling is usually enough. A connected add-on pays off for panels, high volume and many reschedules.
How an add-on connects to Greenhouse (technical view)
Any external scheduling tool needs three channels. Check each against the current Greenhouse documentation before you buy or build:
- Trigger: Greenhouse webhooks such as candidate_stage_change (payload includes the stage and its interviews). Requests are signed with HMAC-SHA256 over the whole body; failed deliveries are retried up to seven times over 15 hours. A separate interview_deleted event fires on cancellation.
- Read and write: the Harvest v3 API offers GET/POST/PATCH/DELETE /v3/interviews, where POST records an interview already scheduled on an external calendar. v3 uses OAuth 2.0; Greenhouse announced removal of Harvest v1/v2 for 31 August 2026, so new integrations must target v3.
- Calendars: Google or Microsoft calendar access for each interviewer, because Greenhouse itself relies on them.
A typical flow: stage change fires the webhook, the tool reads interviewers and availability, books the event, then writes the result back to Greenhouse so reports stay correct. Define who owns a decline, whether the tool or the coordinator reschedules, and when a human must approve (for example senior candidates).
Where Sprad fits
Sprad does not replace Greenhouse's interviewer scheduling and makes no claim to write into Greenhouse calendars. What is documented on sprad.io: Screening lists Greenhouse among the ATS systems it works with, and candidates can pick their own interview slot in the portal through your booking link. The candidate-journey step (updates, reminders, appointments) costs 9 credits per application; the ATS integration costs 100 credits per connection (current prices). At 100 applications per month, the journey step is 900 credits, which is 72 € at the Atlas Base credit price of 0.08 €. Which parts of your Greenhouse scheduling flow it can take over depends on your setup; clarify that in a demo before relying on it.
Data protection and fairness
Scheduling processes names, contact details, calendar availability and interview times, so GDPR applies. Practical points: have a data processing agreement with every tool that reads calendars, grant minimum calendar scope (free/busy where possible), set deletion periods, and keep interview invitations free of unnecessary information. Under Article 5 GDPR, data must be limited to what is necessary. Pure slot booking makes no selection decision; as soon as AI ranks or rejects candidates, stricter rules apply (see our guide on AI candidate interviews in the EU and the AI ethics page).
Common mistakes
- Interviewers never connect their calendar, so the slot search shows too few times.
- Working hours and time zones are not set; defaults of Mon-Fri 9-17 apply silently.
- Calendar connected via an alias instead of the primary email address.
- No owner for declines, so rescheduling falls back to ad-hoc messages.
- Building on the Harvest v1/v2 API instead of v3.
FAQ
Does Greenhouse have built-in interview scheduling?
Yes: manual scheduling, automated scheduling and candidate self-scheduling, all based on connected calendars. Plan availability differs, so check your subscription.
Can Greenhouse schedule panel interviews automatically?
Automated scheduling supports panels over one or several days. Stage-transition automation for self-scheduling covers single-interview stages only.
How far ahead can candidates book?
Self-schedule slots run from 24 hours in advance up to 30 days ahead.
Do I need an add-on?
Only if the limits above cost you measurable time. Count touchpoints per interview first, then use the calculation above.
Which Greenhouse API does an add-on use?
Webhooks for triggers and the Harvest v3 API with OAuth 2.0 for reading and writing interviews.
Is calendar-based scheduling GDPR compliant?
It can be, with a data processing agreement, minimal calendar scope and defined retention. Your data protection officer should confirm the setup.
Sources (as of October 2026)
Greenhouse Support (scheduling model, automated scheduling, self-schedule request), Greenhouse developer documentation (webhooks, Harvest v3), Regulation (EU) 2016/679, Sprad product and pricing pages.
Jürgen Ulbrich
Jürgen Ulbrich has more than a decade of experience in developing and leading high-performing teams and companies. As an expert in employee referral programs as well as feedback and performance processes, Jürgen has helped over 100 organizations optimize their talent acquisition and development strategies.
