Make is a visual platform that lets you design, build, and automate anything – from simple tasks to complex workflows – in minutes. With Make, you can send information between Greenhouse Recruiting and thousands of apps. It's fast and easy to use, visually intuitive, and it requires zero coding expertise.

Make's integration with Greenhouse Recruiting allows you to build workflows with HRIS, IT onboarding, project management solutions, and many more, without the need for programming expertise. Complex workflows can often be completed in days or weeks instead of months.

Note: To use Make with Greenhouse Recruiting, you must have a Make enterprise plan.

Create a Harvest API key

To enable the Make integration, you'll need to create a Harvest API key in Greenhouse Recruiting.

Follow the steps in this article to create the key, and verify that the credentials and permissions below are selected.


In the Create New Credential box, make the following selections:

  • API type: Harvest
  • Partner: Make (or unlisted vendor)
  • Description: Make Harvest API key

Note: If Make isn't listed in the partner dropdown, select Unlisted vendor.


Make allows you to create workflows using any of the Harvest API endpoints. To allow full use of all endpoints you will need to enable all the available permissions for your API key.

A more secure approach is to select only the particular permissions required for your specific workflow scenario. If you have different scenarios requiring different permissions, create a separate API key for each scenario with an appropriate description that summarizes the permissions granted.

Each API key will be used by one corresponding connection object in Make. Just like the API key, we suggest you include a summary of the Greenhouse Recruiting API permissions within the name of the connection object in Make.

Greenhouse Recruiting in Make currently implements modules for the applications, approvals, candidates, jobs, and job post endpoints. Other endpoints are accessible only through the Make a Harvest API Call module in Make. You should select permission groups based on the modules you plan to use in your Make scenario.

Full details on the specific API permissions required for each Greenhouse Recruiting module in Make are available in the Make help documentation.

Create a connection on Make

Next, login to Make a click the ? icon within the Greenhouse Recruiting module in Make or click here.

Open the Make scenario builder, and select the Greenhouse Recruiting module to Create a connection.

Make integration platform shows an example scenario builder with a connection created to Greenhouse Recruiting

Use the following details to create your connection:

  • Connection name: Enter a name for the connection, referencing the API permissions that you're expecting.
  • API key: Enter the API key generated in Greenhouse Recruiting.

Click Save.

Create web hooks

Next, you'll need to create web books in Make and in Greenhouse Recruiting.

First, open the Watch module in Make for the appropriate Greenhouse Recruiting data object.

Make integration platform shows an example web hook creation setup

Click Add.

Use the following details to create a web hook:

  • Web hook name: Greenhouse[EVENT]webhook. Replace [EVENT] with the event in Greenhouse Recruiting that will trigger the web hook, like "candidate hired."
  • Connection: Select the Make connection object you created earlier or add a new one.
  • Event: Select a Greenhouse Recruiting event to trigger the web hook.
  • Secret key: Create an arbitrary secret key. You will use this key when creating the web hook in Greenhouse Recruiting in the next step. A secret key adds extra security to ensure that your Make web hook is only used when authorized.

Click Save and copy the URL address.

Click Ok and save the trigger.

Next, follow the steps in this article to create a web hook in Greenhouse Recruiting. Use the values listed below to configure the web hook.

  • Name: Make integration [EVENT]
  • When: Select the events which your Make scenario requires
  • Endpoint URL: The endpoint URL saved from the web hook setup step in Make.
  • Secret Key: The arbitrary secret key you specified in the web hook setup step in Make.

Additional resources

Check out Make's support documentation for more details.

For additional information or troubleshooting not covered here, reach out to