Greenhouse
Comprehensive Greenhouse ATS connector for managing candidates, jobs, applications, scorecards, and recruiting workflows.
What you can ask
- List candidates in the
On-sitestage for the Senior Engineer role, sorted by interview date. - Find offers extended in the last 30 days that haven't been accepted yet.
- Pull a breakdown of candidates by source for Q1 hires.
Set up
Greenhouse connects with credentials from your Greenhouse account. Have these values ready:
- Client ID
- Client secret
- Go to Organization > Connectors and find Greenhouse.
- Click Enable and choose which tools to allow.
- Each member enters their own values the first time they use it.
To use one account for the whole organization, turn on Share one connection with everyone. Every member's agents then act as that account, with exactly the access it has.
Tools
Greenhouse offers 71 tools. Admins choose which ones agents can use. See Tool permission groups.
Read (29)
View and search information without changing it.
| Tool | What it does |
|---|---|
check_hire_readiness | Validate application meets all hiring prerequisites. |
discover_custom_and_required_fields | Show the required, recommended and optional fields, plus org custom fields, for creating a candidate, job, application, department, office or user. |
get_application | Get one application by ID: candidate ID, job ID, current stage, status, source, recruiter and coordinator IDs and dates. |
get_application_scorecards | List the scorecards for one application: overall rating (strong_yes to definitely_not), status, interviewer and submitted date. |
get_candidate | Get a candidate profile by ID: name, contacts, tags, custom fields, timestamps. |
get_department | Retrieve detailed information about a specific department by ID including department name, parent department, child departments, external ID, and complete hierarchical relationships. |
get_job | Get one job by ID: name, status, requisition ID, department ID, office IDs, custom fields and dates. |
get_job_approval_flows | Get a job's approval flows: approval type (e.g. offer_candidate), status (pending or approved), whether approval is sequential, and dates. |
get_job_stages | List the interview stages of one job (job_id) or several (job_ids) in pipeline order, each with its interview slots and their job_interview_id, which create_interview needs. |
get_office | Retrieve detailed information about a specific office by ID including office name, physical location, primary contact user, parent office, child offices, external ID, and complete hierarchical relationships. |
get_scorecard | Get one interview scorecard with the overall rating, notes, each interview question with the interviewer's answer, and each attribute rating (for example a skill) with its note. |
get_scorecard_summary | Count one application's scorecards: total, submitted, and how many of each overall recommendation (strong_yes, yes, no, definitely_not, no_decision). |
get_user | Get one Greenhouse user by ID: name, primary email, employee ID, site admin and deactivated flags, linked candidate IDs and dates. |
get_user_permissions | Get whether a Greenhouse user is a site admin and whether they are deactivated. |
list_applications | List applications. |
list_candidates | List candidates, newest first. |
list_close_reasons | List all reasons available for closing job openings to track why positions are no longer active (e.g., 'Hire - New Headcount', 'Position Eliminated', 'Filled Internally', 'Budget Frozen'). |
list_custom_fields | List custom field definitions for every object type: name, type, whether required, and options for dropdowns. |
list_departments | List all departments in the organization including department names, IDs, parent-child relationships, external IDs, and child department hierarchies. |
list_interviews | List scheduled interviews. |
list_job_openings | List a job's openings (headcount slots): opening ID, external opening_id, open or closed, opened and closed dates, close reason and the application that filled it. |
list_jobs | List jobs, newest first. |
list_offices | List offices with ID, name, location text, parent and child offices, primary contact user ID and external ID. |
list_reject_reasons | List rejection reasons with IDs, names and type (We rejected them, They rejected us, ...). |
list_scorecards | List interview scorecards across all applications: overall rating, status, interviewer, application and dates. |
list_sources | List candidate sources (e.g. LinkedIn, Referral, Career Site) with IDs and types. Use these IDs for source_id when creating candidates or applications. |
list_tags | List every candidate tag with ID and name. |
list_users | List Greenhouse users (recruiters, hiring managers, admins) with ID, name, email, site admin and deactivated flags. |
validate_credential | Validate Greenhouse credentials. |
Write (15)
Create or send data.
| Tool | What it does |
|---|---|
add_application_note | Add a note anchored to one application: a NOTE, an ACTIVITY entry, or a logged EMAIL (needs subject and email_from/to/cc). visibility is public, private or admin_only. |
add_attachment | Attach a file (resume, cover letter, take-home test, offer document, other) to an application, as base64 content or a public url (exactly one). |
add_candidate_education | Add an education entry to a candidate: school, degree and discipline by name (matched to the org's option lists) or option ID, plus dates. |
add_candidate_employment | Add a work-history entry (company, title, start date, optional end date; no end date means current job) to a candidate. |
add_candidate_note | Add a candidate-level note: a NOTE, an ACTIVITY entry, or a logged EMAIL (needs subject and email_from/to/cc). visibility is public, private or admin_only. |
add_candidate_tags | Add tags to a candidate by tag name. |
create_application | Create an application for an existing candidate: on a job (job_id), or a prospect (prospect true, optional job_ids and pool). |
create_candidate | Create a candidate (first_name and last_name required) with contacts, tags and custom fields, and optionally their first application in the same call: application.job_id for a job, or application.prospect true for a prospect. |
create_department | Create a department. |
create_interview | Record an already-scheduled interview on an application. |
create_job | Create a job by copying a template job (template_job_id), which supplies stages, departments and offices. |
create_job_opening | Add openings (headcount slots) to a job. |
create_office | Create an office. |
create_user | Create a Greenhouse user with first_name, last_name and email. |
invite_user | Create a Greenhouse user and send them an invitation email. |
Delete or overwrite (27)
Remove or replace existing data.
| Tool | What it does |
|---|---|
advance_application | Advance an application to the next interview stage, or to to_stage_id / to_stage_name on the same job. from_stage_id is read automatically when omitted. |
anonymize_candidate | Erase selected personal data groups from a candidate (e.g. full_name, email_addresses, phone_numbers, attachments, notes) for privacy requests, keeping hiring activity for reporting. |
convert_prospect | Convert a prospect application into a candidate application on a job. |
delete_application | Permanently delete one application with its stages, scorecards and rejection and prospect details. |
delete_attachment | Permanently delete an attachment from its application; deleting a resume also clears its resume score. |
delete_candidate | Permanently delete a candidate with all their applications, attachments, scorecards and notes. |
delete_candidate_education | Delete one education entry from a candidate. |
delete_candidate_employment | Delete one work-history entry from a candidate. |
delete_interview | Delete an interview, with its panel, in-progress scorecards and reminders. |
disable_user | Deactivate a Greenhouse user so they cannot sign in; their history stays. |
enable_user | Reactivate a deactivated Greenhouse user so they can sign in again. |
hire_application | Mark an application hired and fill an opening on its job. |
merge_candidates | Merge a duplicate candidate into a primary one. |
move_application | Move an application to any stage, forward or back (to_stage_id or to_stage_name), or onto another job (to_job_id). from_stage_id is read automatically when omitted. |
reject_application | Reject an active application with a reason, optional internal note, custom fields and a templated rejection email (template by ID or name, now or scheduled). |
remove_candidate_tags | Remove tags from a candidate by tag name. |
transfer_application | Transfer an application to a different job, optionally into a stage on that job (target_stage_id or target_stage_name; defaults to the first stage). |
unreject_application | Restore rejected application to active status. |
update_application | Update an application's source, referrer, recruiter, coordinator, prospect pool or stage, dates or custom fields. |
update_application_rejection | Change the rejection reason or rejection-question answers of an already-rejected application without changing its rejection date. |
update_candidate | Update a candidate's name, title, company, contacts, time zone, privacy, tags, linked users or custom fields. |
update_department | Update an existing department's information including name, parent department relationship, and external ID. |
update_interview | Change an interview's start/end time, location, video link, external_event_id or panel. |
update_job | Update a job's name, requisition ID, notes, departments, offices, confidentiality or custom fields. |
update_job_opening | Update a job opening: close it (status 'closed' plus an optional close_reason_id from list_close_reasons), reopen it (status 'open'), or change its external opening_id or target start date. |
update_office | Update an existing office's information including name, location, primary contact user, parent office relationship, and external ID. |
update_user | Update an existing Greenhouse user's information including first_name, last_name, email, employee_id, and linked_candidate_ids. |