Greenhouse scheduling integration guide
Let candidates schedule within recruiting workflows. The intended connection would let a candidate choose an appropriate interview time while keeping stage, interviewer, and scheduling state aligned.
PROVIDER SETUP GUIDE. Documented workflow, not a live Greenhouse connection.
Greenhouse at a glance
| Category | Recruiting and ATS |
|---|---|
| Status | Provider setup guide |
| Job | Let a candidate choose an appropriate interview time while keeping stage, interviewer, and scheduling state aligned |
| Data exchanged | Candidate and job identifiers; interview stage, panel, and duration; confirmed time, change state, and preparation details |
| Related capability | Team scheduling software |
What the Greenhouse connection is designed to do
For recruiting and ats workflows, the important job is to let a candidate choose an appropriate interview time while keeping stage, interviewer, and scheduling state aligned. Let candidates schedule within recruiting workflows. It sits beside the other recruiting and ats connections and supports the team scheduling software requirements.
Greenhouse-specific integration decisions
Preserve Greenhouse candidate, application, job, stage, interview plan, scorecard, panel, and user identity rather than matching on email alone.
Check these against current Greenhouse documentation and your account edition; the verification standard explains how provider claims are reviewed.
Greenhouse provider review points
- Preserve greenhouse candidate
- Interview plan
- User identity rather than matching on email alone
Scheduling data and actions in the workflow
For Greenhouse, these are the data groups the connection exchanges. Record the source, destination, and owner of each before granting access:
- Candidate and job identifiers
- Interview stage, panel, and duration
- Confirmed time, change state, and preparation details
Common Greenhouse scheduling use cases
- Sending self-scheduling from a candidate record
- Coordinating a panel without exposing interviewer calendars
- Returning confirmed interview activity to the hiring workflow
Greenhouse setup and verification checklist
- Test candidate records with identical email addresses.
- Verify panel availability and interviewer substitutions.
- Review what candidate information appears in calendar invitations.
Availability, permissions, and limits
Hiring data can be sensitive and subject to retention rules. Limit fields, permissions, and calendar exposure to what the interview needs.
Retry and duplicate handling is covered in the API and webhook guide; ask about Greenhouse to confirm production status before building on it.
Map the Greenhouse workflow before connecting it.
Bring the trigger, required data, failure path, and desired guest outcome.
Discuss the connectionGreenhouse integration questions
Provider-specific answers for teams planning a Greenhouse scheduling connection.
Which Greenhouse stage should trigger scheduling?
Tie the booking to a specific interview stage rather than a general application update, so the candidate is never invited to schedule something they have not reached.
How are Greenhouse interview kits and scorecards affected?
Confirm that a scheduled interview attaches the right kit and creates the expected scorecard. An interview without a scorecard produces no hiring signal at all.
What happens when a candidate is rejected after booking?
Cancellation must reach the candidate promptly and respectfully. An interview invitation that stays live after rejection is the worst possible candidate experience.
Greenhouse data and lifecycle decisions
1. Choose the identity model
Anchor the workflow to the Greenhouse candidate, application, job, and interview plan rather than an email address alone. A person can have several applications, and an interview scheduled against the wrong application can expose the wrong stage, panel, scorecard, or preparation context.
2. Protect business ownership
Model the panel as named interviewers with explicit roles and calendar responsibility. Test replacements, optional participants, deactivated users, rooms, remote links, and a required interviewer who becomes unavailable after the candidate has already selected a time.
3. Map the full lifecycle
Keep scheduling state distinct from recruiting judgment. Confirmation may update the intended interview record, but cancellation must not reject a candidate, advance a stage, complete a scorecard, or trigger another recruiting action unless a separately owned rule explicitly requires it.
4. Keep traceable evidence
Trace the candidate-facing invitation through application ID, interview ID, interview kit, scheduled timestamps, participant calendars, and notification result. Verify Greenhouse edition, API permissions, custom fields, rate limits, privacy retention, and retry behavior in a non-production job first.
