Greenhouse

Reactivate a previously deactivated Greenhouse user via the Harvest v3 API so they can sign in again. Use when you need to restore sign-in access for a user account that was previously deactivated, for example when an employee returns. Reactivation restores access only; job permissions that were removed during deactivation are not restored. The call is safe to repeat on an already-active user.

Tool to anonymize selected categories of personally identifiable data on a Greenhouse candidate via the Harvest v3 API, for GDPR or right-to-be-forgotten requests. Use when you must permanently redact specific classes of a candidate's PII (such as full name, contact details, tags, attachments, or notes) while retaining the candidate record. WARNING: anonymization is irreversible — the selected fields are permanently cleared or redacted and cannot be recovered, so verify the candidate id and the field selection carefully before calling.

Tool to apply an existing candidate tag to a candidate via the Greenhouse Harvest v3 API. Use when you want to label a candidate with a tag that already exists in the organization's candidate-tag dictionary. Both the candidate and the tag must already exist; the tag is not created by this action.

Tool to add multiple blocked spam sources to Greenhouse in a single request via the Harvest v3 API. Use when you need to block several IP addresses, email addresses, CIDR ranges, and/or email domains at once so future applications from them are automatically rejected. The request is processed asynchronously: Greenhouse returns a bulk request uuid and a status URL to poll for completion.

Tool to add many custom field options at once to select-type custom fields via the Greenhouse Harvest v3 API. Use when you need to create multiple options across one or more single_select/multi_select custom fields in a single call. The request is processed asynchronously: Greenhouse returns a bulk request uuid and a status URL to poll for completion and the created option ids.

Tool to asynchronously create many Greenhouse openings across one or more jobs in a single Harvest v3 call. Use when you need to add headcount slots in bulk and want a single submission that Greenhouse processes in the background. Returns a bulk_action_uuid and status_url to poll for per-row results; openings are created independently, so some rows may succeed while others fail.

Tool to asynchronously deactivate many Greenhouse users in a single Harvest v3 call, up to the bulk-endpoint cap per request. Use when you need to revoke sign-in access for several users at once (for example when offboarding a group of employees) and want one submission that Greenhouse processes in the background. Deactivation only blocks sign-in: each user's record and history are preserved and any user can be reactivated later, so the operation is reversible. Returns a bulk_action_uuid and status_url to poll for per-row results; users are processed independently, so some rows may succeed while others fail.

Tool to archive many custom field options at once by id via the Greenhouse Harvest v3 API. Use when you need to remove multiple options from one or more select-type custom fields in a single call. This is destructive: archived custom field options are removed from the field and can no longer be selected, so restoring them requires re-creating the options. The request is processed asynchronously: Greenhouse returns a bulk request uuid and a status URL to poll for completion.

Tool to asynchronously update the note on many Greenhouse blocked spam sources in a single Harvest v3 call. Use when you need to revise notes on multiple blocklist entries at once and want a single submission that Greenhouse processes in the background. Returns a bulk_action_uuid and status_url to poll for per-row results; only the note can be changed (source_type and value are immutable here), and rows are processed independently so some may succeed while others fail.

Tool to asynchronously edit many Greenhouse custom field options in a single Harvest v3 call. Use when you need to rename, reorder, or set external ids on several options at once and want a single submission that Greenhouse processes in the background. Returns a bulk_action_uuid and status_url to poll for per-row results; each option is updated independently, so some rows may succeed while others fail.

Tool to asynchronously update many Greenhouse departments in a single call via the Harvest v3 API. Use when you need to rename or re-key several departments at once, each identified by its Greenhouse id, up to Greenhouse's bulk-endpoint cap per request. The request is processed asynchronously: Greenhouse validates and updates each department independently and returns a bulk request uuid plus a status URL to poll for the final per-row outcome.

Tool to asynchronously update many Greenhouse offices in a single Harvest v3 call. Use when you need to rename offices, set or clear their location or external_id, or reposition them in the office tree in bulk, and want a single submission that Greenhouse processes in the background. Returns a bulk_action_uuid and status_url to poll for per-row results; offices are updated independently, so some rows may succeed while others fail.

Tool to asynchronously update many Greenhouse openings in a single call via the Harvest v3 API. Use when you need to re-key, open, close, or update custom fields on several openings at once, each identified by its immutable Greenhouse id, up to Greenhouse's bulk-endpoint cap per request. The request is processed asynchronously: Greenhouse validates and updates each opening independently and returns a bulk request uuid plus a status URL to poll for the final per-row outcome. Closing an opening (status 'closed') cannot be undone except by explicitly reopening it, and closing the last opening also closes the hiring plan.

Tool to asynchronously update many Greenhouse users in a single call via the Harvest v3 API. Use when you need to change fields on several users at once (for example an HRIS sync updating job titles, offices, departments, or custom fields), each identified by its Greenhouse id, up to Greenhouse's bulk-endpoint cap per request. The request is processed asynchronously: Greenhouse validates and updates each user independently and returns a bulk request uuid plus a status URL to poll for the final per-row outcome.

Tool to create a new application for an existing Greenhouse candidate via the Harvest v3 API. Use when you need to attach a candidate to a job (supply candidate_id and job_id) or register a sourced candidate as a prospect (supply candidate_id and prospect: true). The two request shapes are mutually exclusive: a job application uses job_id while a prospect uses prospect: true with optional prospect-specific fields.

Tool to create a multi-step approval flow on a Greenhouse job via the Harvest v3 API. Use when you need to gate a job opening or offer behind one or more tiers of approvers, supplying the job_id, approval_type, whether the tiers resolve sequentially, and the seeded approver_groups. The flow is created with approval_status=pending; offer_candidate flows additionally require the offer_id.

Tool to attach a file to an existing Greenhouse application via the Harvest v3 API. Use when you need to upload a document (resume, cover letter, offer letter, etc.) to a candidate's application, supplying the application_id, filename, type, and exactly one of content (base64-encoded bytes) or url (a publicly fetchable link). The returned download URL is time-limited and expires after seven days.

Tool to add a new IP address, CIDR range, email address, or email domain to the organization's spam blocklist via the Greenhouse Harvest v3 API. Use when you need to block a sender or network source so that future applications and emails from it are automatically rejected. The source_type field controls how value is interpreted (single IP, IP range, single email address, or whole email domain).

Tool to create a new candidate profile in Greenhouse via the Harvest v3 API. Use when you need to add a candidate to your organization, optionally creating their first application (an applicant on a specific job, or a prospect) in the same call. Only first_name and last_name are required; all other profile and application fields are optional.

Tool to add a new education entry to a Greenhouse candidate's profile via the Harvest v3 API. Use when you need to record a candidate's schooling, including the school, degree, and discipline (referenced by custom-field option ids) along with start and end dates. Only candidate_id is required; school, degree, and discipline are optional but must reference existing custom-field option ids.

Tool to add a new work-history (employment) entry to a Greenhouse candidate's profile via the Harvest v3 API. Use when you need to record a candidate's past or current role. The candidate id, company name, job title, and start date are required by Greenhouse; omit end_date to represent a current, ongoing position.

Tool to add a new tag to the organization's candidate-tag dictionary via the Greenhouse Harvest v3 API. Use when you need to register a reusable candidate tag (by name) so it can later be applied to candidates. Tag names are case-insensitive; if a matching tag already exists Greenhouse returns the existing tag rather than creating a duplicate.

Tool to add a new custom field to your organization's dictionary via the Greenhouse Harvest v3 API. Use when you need to define a new custom data point (text, number, currency, select, date, etc.) on jobs, candidates, applications, offers, openings, or other Greenhouse resources. field_type, value_type, and name are required; select-type fields (single_select/multi_select) require custom_field_options.

Tool to restrict a custom field's visibility to one additional department via the Greenhouse Harvest v3 API. Use when you want a custom field to appear only on jobs, offers, or candidates that belong to specific departments and need to add another department to that allow-list. Each call adds a single department association; repeat the call to grant visibility to more departments.

Tool to restrict a custom field's visibility to one additional office via the Greenhouse Harvest v3 API. Use when you need to make an existing job, opening, or offer custom field visible for one more office without replacing its existing office restrictions. Supply the target custom_field_id and the office_id; only one office can be added per call.

Tool to add a new selectable value to a single_select or multi_select custom field via the Greenhouse Harvest v3 API. Use when you need to extend a custom field with an additional option (for example syncing option values from an external HRIS). Supply the target custom_field_id and the option name, plus an optional sort_order and external_id; the field must be of a select type for the option to apply.

Tool to create a new department for the organization via the Greenhouse Harvest v3 API. Use when you need to add a department with an optional external_id and an optional parent department (by id or external_id) to nest it in the department tree. The name is required and must be unique among active departments; parent_id and external_parent_id are mutually exclusive.

Tool to create a scheduled interview against a candidate application in Greenhouse Harvest. Use when you need to place a candidate's interview onto the schedule with a start/end time, panel of interviewers, and the corresponding calendar event. The interview is created for a specific interview-plan slot (job_interview_id) and tied to an external calendar event id.

Tool to create a new Greenhouse job from an existing template via the Harvest v3 API. Use when you need to spin up a new requisition that inherits its interview plan, scorecards, hiring team, and approval workflow from a template job. template_job_id and number_of_openings are required; department/office can be set by Greenhouse id or by partner external_id (the two forms are mutually exclusive), and the legacy confidential flag cannot be set here.

Tool to assign a user as a hiring manager on a Greenhouse job via the Harvest v3 API. Use when you need to add an existing organization user to a job's hiring team in the hiring manager role. Both job_id and user_id are required and must reference resources that already exist in your organization; the call returns the assignment's row id, which is needed to later revoke it.

Tool to create a free-form note attached to a Greenhouse job via the Harvest v3 API. Use when you need to record context, hiring decisions, or status updates on a specific job (identified by job_id) rather than on a candidate or application. The note's author is set by user_id and its access level by visibility (privately_visible or admin_only_visible).

Add a Greenhouse user to a job's hiring team as a recruiter, sourcer, or coordinator via the Harvest v3 API. Use when you need to assign someone an owner role on a specific job so they participate in its recruiting workflow. Requires job_id, user_id, and the role type.

Tool to create a candidate note, log an email, or record an activity-feed entry on a Greenhouse candidate via the Harvest v3 API. Use when you need to attach a note (note_type NOTE), a logged email (note_type EMAIL, which also requires subject, email_from, email_to and email_cc), or an activity-feed entry (note_type ACTIVITY) to a candidate, supplying candidate_id, body and visibility. The entry is appended to the candidate's activity feed and attributed to the authenticated user unless user_id is provided.

Tool to create a new offer on an existing Greenhouse application via the Harvest v3 API. Use when you need to extend an offer to a candidate, supplying the application_id plus optional starts_on and custom_fields (compensation components and any configured offer custom fields). The new offer is created with status=Created at version=1; if the application already has an offer, the submission is applied to the same offer chain rather than creating a competing record.

Tool to create a new office for the organization via the Greenhouse Harvest v3 API. Use when you need to add a recruiting location (e.g. for scoping jobs, candidates, or custom fields) to a Greenhouse organization. Only name is required; supply parent_id or external_parent_id to nest the office under a parent (Advanced/Expert package), and external_id for HRIS-driven reconciliation (Expert package).

Tool to add a new opening (headcount slot) to an existing Greenhouse job via the Harvest v3 API. Use when a job needs additional headcount and you want to create one more opening that can be filled by a single hire. job_id is required; an optional partner-supplied opening_id and custom field values may also be set. A job cannot hold more than 100 open openings.

Create a new user in your Greenhouse Recruiting organization via the Harvest v3 API. Use when you need to onboard a recruiter, hiring manager, interviewer, coordinator, or other team member, optionally assigning offices/departments, an external employee_id, and custom field values. first_name, last_name, and primary_email are required and the email must be unique across the organization.

Attach an additional email address to an existing Greenhouse user via the Harvest v3 API. Use when a recruiter, hiring manager, or other team member needs a secondary email address associated with their Greenhouse account, optionally triggering a verification email. The email must be unique across the organization and cannot already belong to another user.

Grant a Greenhouse user a Job Admin role on a single job via the Harvest v3 API. Use when you need to give a recruiter, hiring manager, coordinator, or interviewer scoped access to manage one specific job at a defined permission level. Requires user_id, job_id, and role_id; retrieve valid role ids from the Greenhouse user roles endpoint.

Tool to deactivate a Greenhouse user via the Harvest v3 API, preventing that user from signing in while preserving their historical data. Use when you need to offboard or temporarily disable a recruiter, hiring manager, interviewer, coordinator, or admin account. This is a reversible state change: the user can be restored later via the separate activate-user endpoint, but while deactivated they lose all access. The endpoint returns HTTP 204 No Content on success.

Tool to permanently delete a single Greenhouse application via the Harvest v3 API, along with its interview stages, scorecards, rejection details, and prospect details. Use when you need to remove an application entirely; the parent candidate is left intact. WARNING: this operation is irreversible and the deleted application and all of its associated data cannot be recovered.

Tool to detach a single tag from a candidate in Greenhouse via the Harvest v3 API, identified by its applied candidate tag id. Use when you need to remove a tag association from a candidate. This action is irreversible: once deleted the tag association cannot be recovered (re-applying the tag creates a new association), so confirm the id before calling.

Tool to permanently remove an attachment from its Greenhouse application via the Harvest v3 API, identified by its attachment id. Use when you need to delete a document (resume, cover letter, offer letter, etc.) that was previously uploaded to a candidate's application. This action is irreversible: once deleted the attachment and its underlying file cannot be recovered, so confirm the attachment id before calling.

Tool to permanently remove a single blocked spam source from Greenhouse via the Harvest v3 API. Use when an IP address, email address, CIDR range, or email domain was blocked by mistake or should no longer be blocked, so future applications from it are accepted again. This action is irreversible: once removed the blocked spam source entry cannot be recovered, so confirm the id before calling.

Tool to permanently delete a candidate from Greenhouse via the Harvest v3 API. Use when you need to fully remove a candidate and all of their associated applications, attachments, scorecards, notes, and other records identified by the candidate id. This action is irreversible: once deleted the candidate and every associated record cannot be recovered, so confirm the id before calling.

Tool to remove a single education entry from a Greenhouse candidate's profile via the Harvest v3 API. Use when you need to delete one specific education record from a candidate, identified by the education entry id. WARNING: this operation is destructive and irreversible - the education entry is permanently erased and cannot be recovered.

Tool to permanently delete a single employment entry from a candidate's profile in Greenhouse via the Harvest v3 API. Use when you need to remove an incorrect or outdated employment record identified by its candidate employment id. This action is irreversible: once deleted the employment entry cannot be recovered, so confirm the id before calling.

Tool to delete a tag from your organization's candidate-tag dictionary in Greenhouse via the Harvest v3 API, identified by its candidate tag id. Use when you need to permanently remove a tag from the dictionary. This action is irreversible: deletion enqueues an asynchronous job that first strips the tag from every candidate it is applied to (which can take up to 24 hours) and then removes the tag itself, and the data cannot be recovered, so confirm the id before calling.

Tool to remove an office from a custom field's visibility scope via the Greenhouse Harvest v3 API. Use when an existing job, opening, or offer custom field should no longer be restricted to a particular office and that office's association needs to be deleted. This is a permanent, irreversible deletion: the office is dropped from the field's allowed offices and can only be restored by creating the association again, so confirm the association id before calling.

Tool to archive a single custom field option via the Greenhouse Harvest v3 API so it can no longer be selected on new records. Use when an option of a select-type custom field should be retired while preserving it on existing records. This is a soft delete (the option is set inactive) rather than a hard delete, but it still removes the option from future selection, so confirm the id before calling.

Tool to cancel and permanently delete a scheduled interview in Greenhouse via the Harvest v3 API, identified by its interview id. Use when an interview needs to be called off and removed entirely rather than rescheduled. This action is irreversible: once deleted the scheduled interview and its associated calendar event cannot be recovered, so confirm the interview id before calling.

Unassign a hiring manager from a Greenhouse job by deleting the job hiring manager join row, identified by its id, via the Harvest v3 API. Use when you need to remove a specific user from a job's hiring team in the hiring manager role. This is destructive and IRREVERSIBLE: the job hiring manager record is permanently removed and must be re-created to restore the assignment.

Permanently delete a Greenhouse job note, identified by its id, via the Harvest v3 API. Use when you need to remove a note that was attached to a job (for example because it was added in error or is no longer relevant). This is destructive and IRREVERSIBLE: the job note is permanently removed and must be re-created to restore it.

Remove a Greenhouse user from a job's hiring team in a single role by deleting the job owner join row, identified by its id, via the Harvest v3 API. Use when you need to take a specific user off a job's hiring team for one role (recruiter, sourcer, or coordinator). This is destructive and IRREVERSIBLE: the job owner record is permanently removed and must be re-created to restore the membership.

Tool to revoke a single Greenhouse user job permission by its id via the Harvest v3 API, removing that user's Job Admin role on the associated job. Use when you need to take away a specific user's Job Admin access to a particular job. This is destructive and IRREVERSIBLE: the permission grant is permanently removed and must be re-created to restore the user's access.

Get the Greenhouse user represented by the connected Harvest OAuth token. The action reads the user id from the token and retrieves that exact user from Greenhouse.

Tool to mark a Greenhouse application as hired and close out the matching opening on the job via the Harvest v3 API. Use when a candidate has accepted an offer and you need to finalize the hire, optionally specifying the start date, the opening to fill, and the close reason for that opening. If no opening_id is supplied, Greenhouse auto-selects an open opening on the job. This is a terminal action: the application leaves the interview pipeline and its status becomes "hired", so it should only be run once the hire is confirmed.

List the applications in your Greenhouse organization, which associate candidates with jobs (candidate applications attach to exactly one job; prospect applications attach to zero or more). Use when you need to look up application ids, statuses, current pipeline stages, or the candidate/job/source/referrer ids tied to each application, or to filter applications by time range, status, stage, or kind. Supports rich filtering, field selection, and cursor-based pagination.

List the application stage history rows in your Greenhouse organization — one row per interview stage an application has occupied, with entered_at and exited_at timestamps. Use when you need the canonical source for stage-history reporting, such as time-in-stage analysis or reconstructing a candidate's pipeline movement for one or more applications. Supports filtering by application ids, interview stage ids, current/past, time ranges, and cursor-based pagination.

Tool to list the approval flows in a Greenhouse organization via the Harvest v3 API. Use when you need to enumerate or search the multi-step approval definitions attached to jobs or candidate offers, optionally filtering by approval flow ids, job_ids, offer_ids, approval_type, or creation/update date ranges. Results are paginated; pass the cursor from the previous response to fetch the next page.