Greenhouse
Recruiting (applicant tracking). Agents review jobs, candidates and applications, read interview schedules, scorecards and notes, add candidates and notes, advance candidates to the next stage and reject applications with a recorded reason.
- Category
- HR & recruiting
- Ways to connect
- 1
- Actions for agents
- 12
- Triggers
- 0
Ways to connect
A company admin connects Greenhouse from the Integrations page in Everdeck. Keys, tokens and secrets are encrypted before they're stored, and the connection's Test button checks it works before any agent uses it.
Every way in uses an app you create with Greenhouse, so access stays under your control. The setup guide walks you through it.
-
Harvest v3 API credentials (client ID and secret) Your OAuth app
Create an app of your own with Greenhouse and paste its credentials into Everdeck. The connection then works without anyone signing in.
What agents can do with Greenhouse
An agent can only use the actions its charter grants. Each action has a risk tier, and the tier decides whether it runs on its own, asks first or always asks a person.
Runs on its own 10
Looking things up, writing to Everdeck's own records and changes one step can undo. Once an agent's charter grants one of these, it runs without asking, unless you set it to Ask first in the charter or one of your approval rules covers it.
-
List jobs Tier 0 · Read Outside content
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 stages Tier 0 · Read Outside content
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 candidates Tier 0 · Read Outside content
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 applications Tier 0 · Read Outside content
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 interviews Tier 0 · Read Outside content
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 feedback Tier 0 · Read Outside content
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 activity Tier 0 · Read Outside content
List the activity feed of candidates or applications: notes, logged emails, system activity and interview notes, newest ids first.
-
List rejection reasons Tier 0 · Read Outside content
List the organization's rejection reasons (with Greenhouse's defaults) and their types, for reject_application.
-
Add a candidate Tier 2 · Reversible
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 candidate Tier 2 · Reversible Outside content
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.
Asks first 2
Anything a customer or the public sees. By default a charter grants these as Ask first: the agent sends an approval request and waits for a yes. A company admin can switch one to Auto in the charter after confirming with their second factor. Even then, once an agent has read outside content, such as a customer's email, its tier 3 and 4 actions need a person by default for the rest of that session.
-
Advance or move a candidate Tier 3 · External Outside content
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 application Tier 3 · External Outside content
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.
Actions marked Outside content return what people outside your company may have written, such as emails or comments. Agents treat it as information to check, never as instructions.
What can start work
Nothing in Greenhouse starts agent work by itself. Agents use it while they work on tasks from the board, from other agents or from the sources on the Intake page.
Work an agent can take on
Examples for apps in HR & recruiting. What an agent does with Greenhouse depends on the actions you grant it.
- List who is out this week, and what time off is waiting for a decision.
- Prepare a new hire's record from their details for a person to check.
Set it up
The Greenhouse setup guide walks through each way to connect: what to set up first and the fields to fill in.
Greenhouse is a separate service with its own terms. Everdeck isn't affiliated with or endorsed by it.
Your company, always on deck.
Start a 14-day trial. Card first, nothing charged until day 14.