Greenhouse setup guide

Agents help with people, candidates and hiring.

Ways to connect

Company admins connect apps, on the Integrations page in Everdeck: open Greenhouse, choose one of the ways below, follow its steps and fill in its fields. Everdeck checks what you enter before it saves anything, and asks you to confirm it’s you (your second factor) before you type any secret. How connecting works.

Harvest v3 API credentials (client ID and secret)

Your OAuth app.

This way uses the client ID and secret of an OAuth app you create for Greenhouse. There’s no sign-in page: Everdeck asks Greenhouse for a token with them.

1. In Greenhouse, sign in as a user with the developer permission "Can manage ALL organization's API Credentials" and open Configure > Dev Center > API Credentials.
2. Click Create new API credentials, choose Harvest V3 (OAuth), name it "Everdeck" and save.
3. Manage the credential's scopes and grant: harvest:jobs:list, harvest:job_interview_stages:list, harvest:candidates:list, harvest:candidates:create, harvest:applications:list, harvest:applications:move, harvest:applications:reject, harvest:notes:list, harvest:notes:create, harvest:interviews:list, harvest:scorecards:list and harvest:rejection_reasons:list.
4. Copy the Client ID and Client Secret into the form. Every list endpoint needs a Site Admin, so unless the credential's own integration user is one, enter the numeric user id of a Site Admin the agent should act as (it is the number in that user's Greenhouse URL).

Field	What to enter
Greenhouse user id to act as (a Site Admin; optional)	Text. For example 4080001. Where to find it.

Disconnecting deletes the access token Everdeck saved for this connection. The OAuth app's client ID and secret stay saved under OAuth apps in Everdeck and keep working at Greenhouse until you delete the app or rotate its secret there.

What agents can do

An agent uses an action only when its charter grants it, on the agent’s Tools tab, where you choose whether each one runs by itself (Auto), asks first or never runs. Each action has a risk tier: tier 3 actions, which customers or the public see, ask first unless you choose otherwise, and tier 4 actions (money, deleting things, access) always need a person. How tools and tiers work.

Actions marked Reads outside content return things people outside your company may have written. Agents treat what they read as information, never as instructions, and their riskier actions later in the same session need approval.

• List jobsTier 0 · ReadReads outside contentgreenhouse_list_jobs

  List jobs (requisitions) with internal name, status (open, draft, closed), department, offices and when they opened or closed. Defaults to open jobs.

• List a job's interview stagesTier 0 · ReadReads outside contentgreenhouse_list_job_stages

  List the interview plan of one or more jobs: stage ids, names and order (Application Review first, Offer last). Use the ids as move_application targets.

• Find candidatesTier 0 · ReadReads outside contentgreenhouse_list_candidates

  Find candidates (applicants and prospects) by email, tag, ids or recent activity. Returns name, current company and title, emails, phones, tags, whether they accept email, and last activity. Applications are listed separately with list_applications.

• List applicationsTier 0 · ReadReads outside contentgreenhouse_list_applications

  List applications (a candidate on a job) with job, current stage, status (in_process, rejected, hired, converted), whether a decision is needed, source, recruiter and the candidate's answers to the application questions. Filter by job, candidate, status, stage name or recent changes.

• List interviewsTier 0 · ReadReads outside contentgreenhouse_list_interviews

  List scheduled interviews with application, job, start and end time, location, video link, organizer and status (to_be_scheduled, scheduled, awaiting_feedback, complete and so on).

• Read interview feedbackTier 0 · ReadReads outside contentgreenhouse_list_scorecards

  List scorecards for applications: the interviewer, overall recommendation (strong_no, no, yes, strong_yes, or no_decision when none was chosen), key takeaways and notes to the hiring team, status and when submitted. Private notes are left out.

• Read a candidate's notes and activityTier 0 · ReadReads outside contentgreenhouse_list_notes

  List the activity feed of candidates or applications: notes, logged emails, system activity and interview notes, newest ids first.

• List rejection reasonsTier 0 · ReadReads outside contentgreenhouse_list_rejection_reasons

  List the organization's rejection reasons (with Greenhouse's defaults) and their types, for reject_application.

• Add a candidateTier 2 · Reversiblegreenhouse_create_candidate

  Create a candidate profile, optionally applying them to a job at its first stage (or a chosen stage). Use it for referrals and sourced people; check list_candidates by email first to avoid duplicates. No email is sent to the candidate.

• Add a note to a candidateTier 2 · ReversibleReads outside contentgreenhouse_add_note

  Post a note on a candidate's Notes tab, optionally anchored to one of their applications. Notes are internal: the candidate never sees them. public = anyone who can see the candidate, private = users with the see-private-notes permission, admin_only = job and site admins.

• Advance or move a candidateTier 3 · ExternalReads outside contentgreenhouse_move_application

  Advance an application to the next stage of its interview plan, or to a chosen stage. Stage transition rules configured in Greenhouse run on every move, which can email the candidate (for example a scheduling request) from email_from_user_id.

• Reject an applicationTier 3 · ExternalReads outside contentgreenhouse_reject_application

  Reject an application with a reason from list_rejection_reasons and optional internal notes. With email_template_id the candidate is also sent that rejection email, now or at send_email_at.

Testing, problems and disconnecting

Everdeck checks the connection when you save it. On the connection’s page in Integrations, Test checks it again at any time.

If Greenhouse later refuses the connection, for example because a key was deleted or a sign-in expired, the connection shows Needs attention on the Integrations page and the people who manage connections are told. Agents can’t use it until a company admin fixes it with Edit.

To stop agents using Greenhouse, open the connection and select Disconnect. Agents stop using it at once and its saved credentials are deleted. What else happens depends on how it was connected: each way above says.