Greenhouse Recruiting Make integrationAutomate Greenhouse Recruiting with Make.
Can Make react the second a candidate applies in Greenhouse? Yes. The Greenhouse Recruiting Make integration ships 23 modules, including 5 instant triggers. This guide is for recruiting ops teams: link your account, then build and switch on a first scenario.
Enterprise app This app is reserved to Make's Enterprise plan.
Verified Trustpilot reviews · AI, automation & growth agency
What can the Greenhouse Recruiting Make integration do?
The Greenhouse Recruiting Make integration links your applicant tracking system to Make, a no-code tool where you chain modules (one brick each: a trigger, an action or a search) into a scenario, the automation that runs for you. It covers applications, candidates, prospects, jobs, job posts, offers, approval flows and notes.
Candidates from anywhere land in Greenhouse. A sourcer finds a profile in another tool: Create a Prospect files it, and Add Application to Prospect attaches it to the right opening, so nobody retypes a name.
Hiring managers hear about offers first. Watch Offers fires when an offer is created, approved, updated or deleted. Your scenario can pass that news to the next app in the chain, and Get a Job adds the job details the message needs.
Candidate files stay complete. When an application moves, Watch Applications wakes the scenario, and Add a Candidate Note or Add Attachment to Application writes back what your other tools collected.
Two limits to know before you start. The app is reserved to the Enterprise plan of Make, and the connection only works with Harvest v3, since Greenhouse is retiring Harvest v1 and v2. Greenhouse Onboarding is not supported. The same app may also exist as an n8n node: n8n vs Make lays out how the two tools differ. For a guided start, see our Make training, or the Make pricing page to check what the Enterprise plan includes.
How do you connect Greenhouse Recruiting to Make?
- 01
Add a Greenhouse module
In your scenario, add any Greenhouse Recruiting module, then click Create a connection. A connection is your Greenhouse account linked to Make once and reused by every Greenhouse module you add afterward.
- 02
Name it and authorize Make
Give the connection a clear name if you like, such as the team that owns it. Then authorize Make on the Greenhouse page that opens, or paste the key Greenhouse gives you, depending on what the window asks for.
- 03
Save and reuse it
Click Save. Make can now read your Greenhouse objects, so the module fields start offering jobs, candidates and posts from your account instead of asking you to type identifiers by hand.
Your first scenario with Greenhouse Recruiting
GoalWhen a new application arrives in Greenhouse Recruiting, Make fetches the details of the job it targets.
- 01
Create the scenario
Open the Scenarios page, create a new scenario and click the big +. Search for Greenhouse Recruiting and pick Watch Applications as the first module.
- 02
Pick your connection
Select the connection you saved earlier, or click Create a connection now. Fill the trigger fields; Make lists what it can read from your account once the link exists.
- 03
Add the job lookup
Click the + on the right of the trigger and add Get a Job. Map the job ID from the trigger's bundle, if it carries one (check after a test), so each bundle, one application here, brings back its job.
- 04
Test with Run once
Click Run once, then create or update an application in Greenhouse. Open the bubbles above each module to read the bundles they received and confirm the job came back.
- 05
Switch it on
Turn the scenario on. Each module run is an operation, the unit Make counts on your plan, so a test with a few applications shows you what the scenario will cost in operations.
Greenhouse Recruiting triggers in Make
5 modules start a scenario when something happens in Greenhouse Recruiting. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Greenhouse Recruiting as soon as it happens.
Watch Applications
Instant triggerIn Make“Triggers when an application is created, updated, deleted, or approved.”
Starts your scenario as soon as an application is created, updated, deleted or approved in Greenhouse, so the rest of the chain works on fresh pipeline data instead of a stale export.
Watch Candidates
Instant triggerIn Make“Triggers when a candidate or prospect is created, updated, deleted, submitted an application or other status is changed.”
Hands your scenario every change on a person: a candidate or prospect created, updated, deleted, submitting an application, or changing another status. It is the widest lens on people in the account.
Watch Job Posts
Instant triggerIn Make“Triggers when a job post is created, updated, deleted or a job interview stage is deleted.”
Tells Make when a public job post is created, updated or deleted, and also when an interview stage of a job is deleted. Handy for anything that must mirror what candidates can see.
Watch Jobs
Instant triggerIn Make“Triggers when a job is created, updated, approved, or deleted.”
Fires when a job is created, updated, approved or deleted, so the internal side of a requisition can drive the next steps of your hiring workflow.
Watch Offers
Instant triggerIn Make“Triggers when an offer is created, approved, updated or deleted.”
Reacts to the last stretch of a hire: an offer created, approved, updated or deleted. Your scenario gets the offer right away and can pass it on to the people who prepare a start date.
What Greenhouse Recruiting can do in Make
Greenhouse Recruiting gives you 18 modules in 2 groups. For each one: what it does for you, when to reach for it, and what to watch out for.
If your scenario uses Greenhouse v1.
2 modulesUpdate the connection — create/select a greenhouse2 connection and attach it to each migrated module.
Attachments: stop using applications[].attachments / inline attachments; use Add attachment to application or Add attachment to candidate (with required application_id).
Notes: stop using activity_feed_notes on create/update; use Add a candidate note.
Search filters: remove job_id from Search candidates; remove opening_id, external_department_id, external_office_id from Search jobs.
Retype referrer / owner IDs — where referrer value / prospect_owner_id were free text, map numeric IDs (uinteger).
Re-test webhook payloads on the Watch modules after migrating the connection.
Replace removed inputs
ActionIn the docs onlyThis module appears only in the doc section for scenarios still built on Greenhouse v1, with no description of its own. That section lists the inputs that went away: inline attachments, activity_feed_notes, and some filters of Search Candidates and Search Jobs.
Fix output references
ActionIn the docs onlySits next to Replace removed inputs in the Greenhouse v1 migration section of the doc, again without a description. The notes around it ask you to map numeric IDs where referrer or prospect owner values were free text, and to re-test the Watch modules.
Other modules
16 modulesAdd a Candidate Note
ActionIn Make“Adds a note to the candidate by their ID.”
Writes a note on a candidate profile from its ID, so feedback gathered in a form, a chat or an interview tool ends up where recruiters actually look.
activity_feed_notes on create or update must switch to this module.Add Application to Candidate
ActionIn Make“Creates a new application for a candidate by their ID.”
Opens a new application for someone who is already a candidate, using their ID. The person stays one record while their history gains another job.
Add Application to Prospect
ActionIn Make“Creates a new application for a prospect by their ID.”
Attaches a new application to a prospect, again by ID. The sourced profile gets tied to a real opening, which is often the moment it enters the formal process.
Add Attachment to Application
ActionIn Make“Uploads an attachment to an application by its ID.”
Uploads a file onto one application, so a take-home test or a portfolio sits right next to the job it was made for instead of in someone's inbox.
Add Attachment to Candidate
ActionIn Make“Uploads an attachment to a candidate or prospect by their ID.”
Adds a file to a candidate or a prospect profile by ID. Resumes, cover letters and certificates collected elsewhere get stored on the person.
Create a Candidate
ActionIn Make“Creates a new candidate.”
Builds a brand new candidate record, which is how people applying through a channel Greenhouse does not listen to still end up in your tracking system.
Create a Prospect
ActionIn Make“Creates a new prospect.”
Files a new prospect, the person you would like to hire but who has not applied. Sourcing work from other tools stops living in private spreadsheets.
Get a Job
ActionIn Make“Retrieves the details of a job by its ID.”
Fetches the details of one job from its ID, which gives later modules the context a raw event lacks, like the role behind an application or an offer.
Get a Job Post
ActionIn Make“Retrieves the details of a job post by its ID.”
Reads one job post by ID, meaning the public version of a role that candidates see, as opposed to the internal job behind it.
Make a Harvest API Call
ActionIn Make“Performs an arbitrary authorized Harvest API call.”
Sends a request of your choice to the Harvest API of Greenhouse, signed with the connection you already set up, for cases the other modules leave out.
Update a Candidate
ActionIn Make“Updates a candidate by their ID.”
Changes an existing candidate from their ID, keeping Greenhouse in step when a detail about the person changes in another system.
List Approval Flows
SearchIn Make“Lists approval flows by the job ID.”
Returns the approval flows attached to a job, so you can see who has to sign off on it without opening Greenhouse.
Search Applications
SearchIn Make“Lists applications and filter by criteria.”
Pulls a list of applications that match your criteria. Each match comes out as its own bundle, ready for the next module to process one at a time.
Search Candidates
SearchIn Make“Lists candidates and filter by criteria.”
Looks up candidates by the criteria you set and returns zero, one or several matches. It is the usual check before creating a person.
job_id filter from this module, so older scenarios filtering by job need another route.Search Job Posts
SearchIn Make“Lists job posts and filter by criteria.”
Brings back the job posts that match your filters, one bundle per post, which is handy for syncing what is published with another channel.
Search Jobs
SearchIn Make“Lists jobs and filter by criteria.”
Lists jobs by criteria, giving you the internal requisitions rather than their public posts, each as a separate bundle.
opening_id, external_department_id and external_office_id from its filters, so rework migrated searches.Need help automating Greenhouse Recruiting with Make?
A person reads every message.
