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. This page documents the provider workflow. It does not claim that a Greenhouse account is connected until authorization and lifecycle tests succeed.
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. A dependable connection must also make authorization, retries, lifecycle changes, and administrator-visible failures understandable.
Greenhouse-specific integration decisions
Preserve Greenhouse candidate, application, job, stage, interview plan, scorecard, panel, and user identity rather than matching on email alone.
Verify these provider-specific assumptions against current primary documentation, the exact account edition, administrator policy, and a non-production test. Record the required permission, authoritative identifier, fallback state, and owner for reconnects. The Meetin.gs verification standard explains how change-sensitive provider claims are treated.
Greenhouse provider review points
- Preserve greenhouse candidate. Turn this provider-specific dependency into an acceptance criterion with a named owner, expected result, and safe fallback.
- Interview plan. Turn this provider-specific dependency into an acceptance criterion with a named owner, expected result, and safe fallback.
- User identity rather than matching on email alone. Turn this provider-specific dependency into an acceptance criterion with a named owner, expected result, and safe fallback.
Scheduling data and actions in the workflow
The connection should exchange only what the scheduling job requires. For Greenhouse, review these three data groups before granting access:
- Candidate and job identifiers. Document its source, destination, owner, and behavior after a cancellation or deletion.
- Interview stage, panel, and duration. Document its source, destination, owner, and behavior after a cancellation or deletion.
- Confirmed time, change state, and preparation details. Document its source, destination, owner, and behavior after a cancellation or deletion.
Common Greenhouse scheduling use cases
Sending self-scheduling from a candidate record
This use case should be tested from the organizer's action through the guest-facing result. Include a changed meeting and a failed downstream action, not only a successful new booking.
Coordinating a panel without exposing interviewer calendars
This use case should be tested from the organizer's action through the guest-facing result. Include a changed meeting and a failed downstream action, not only a successful new booking.
Returning confirmed interview activity to the hiring workflow
This use case should be tested from the organizer's action through the guest-facing result. Include a changed meeting and a failed downstream action, not only a successful new booking.
Greenhouse setup and verification checklist
- Test candidate records with identical email addresses.Record the expected result and the person responsible when it does not occur.
- Verify panel availability and interviewer substitutions.Record the expected result and the person responsible when it does not occur.
- Review what candidate information appears in calendar invitations.Record the expected result and the person responsible when it does not occur.
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.
Meetin.gs currently lists this connection as part of its integration architecture. Use the connection request to confirm current production status, supported accounts, scopes, pricing, and rollout timing. This avoids designing a critical workflow around an unverified roadmap item.
Map the Greenhouse workflow before connecting it.
Bring the trigger, required data, failure path, and desired guest outcome.
Discuss the connectionGreenhouse in one clear flow
Greenhouse sends the needed scheduling state to the right system. It keeps the organizer and guest on one record. This prevents a booking change from becoming a silent data mismatch.
Compare this flow with the team scheduling software requirements. Then use the API and webhook help guide to plan retries and recovery.
Simple rule: one booking creates one stable identity. Every later change updates that identity instead of creating a second record.
Greenhouse lifecycle acceptance criteria
Use a non-production Greenhouse account and one disposable meeting to prove the full connection. Record provider object identifiers beside the Meetin.gs event or booking identifier so every later change can be traced to the same relationship.
| State | Greenhouse expectation | Failure to prevent |
|---|---|---|
| Authorization | The intended account grants only the scopes required to let a candidate choose an appropriate interview time while keeping stage, interviewer, and scheduling state aligned. | A personal, test, or former employee account silently owns production records. |
| Confirmation | One provider object is created or updated with the required scheduling data. | A retry creates duplicates or exposes fields that the provider does not need. |
| Reschedule | The original Greenhouse relationship moves to the new time and preserves identity. | Old and new records both appear active. |
| Cancellation | The provider reaches the documented cancelled, refunded, removed, or inactive state. | The guest receives stale details or capacity remains blocked. |
| Connection failure | The booking stays understandable, the failure is visible, and retry is safe. | A connected action disappears without an owner or participant-facing fallback. |
Provider-specific boundary
Preserve Greenhouse candidate, application, job, stage, interview plan, scorecard, panel, and user identity rather than matching on email alone. This is the configuration most likely to distinguish a dependable Greenhouse connection from a generic successful API response.
Minimum data review
Confirm the purpose and retention of candidate and job identifiers, interview stage, panel, and duration, and confirmed time, change state, and preparation details. Do not copy free-text responses, calendar descriptions, participant identifiers, or internal links when the stated connection job does not require them.
Greenhouse 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.
Before you commit to this connection
Whatever the provider, four checks decide whether a connection is dependable. Test authorization with the identity that will own it in production, one normal confirmation, one reschedule, and one cancellation. Then break it deliberately: revoke access, send a duplicate, and simulate a provider outage.
The meeting must stay visible and manageable even when the connected action fails. Preserve the booking record, show the participant something useful, alert a named owner, and make retry safe. The API and webhook guide covers idempotency and retry design, and the integration directory lists every connection reviewed to the same standard.
A Greenhouse operator brief
Preserve Greenhouse candidate, application, job, stage, interview plan, scorecard, panel, and user identity rather than matching on email alone.
Sending self-scheduling from a candidate record needs a named Greenhouse object, authoritative identifier, permitted data set, expected lifecycle result, and recovery owner before it belongs in a production workflow.
Coordinating a panel without exposing interviewer calendars needs a named Greenhouse object, authoritative identifier, permitted data set, expected lifecycle result, and recovery owner before it belongs in a production workflow.
Returning confirmed interview activity to the hiring workflow needs a named Greenhouse object, authoritative identifier, permitted data set, expected lifecycle result, and recovery owner before it belongs in a production workflow.
The operator should be able to trace a guest action from Meetin.gs to the exact provider response and back again. That trace is more useful than a green connection badge because it also explains delayed, duplicated, rejected, and cancelled work.
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.
