SlateAI’s integration with Greenhouse Recruiting allows users to automate candidate screening by generating instant, AI-powered summaries directly within the Greenhouse platform. Users can quickly review skills, qualifications, and job fit for each candidate and leverage the Applicant and Job Assistants (if enabled) to gain deeper insights and compare top candidates. This integration streamlines the evaluation process, helping recruiting teams make informed decisions more efficiently without leaving Greenhouse.

Create a Harvest API key

To configure the SlateAI integration, you’ll need to create a Harvest API key. 

Follow the steps in this article to create the key, and verify that the permissions below are selected when configuring the SlateAI integration.

Credentials

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

  • API Type: Harvest
  • Partner: SlateAI or Unlisted Vendor
  • Description: SlateAI Harvest API Key

Permissions

Verify that the following permissions are selected for the SlateAI integration: 

  • Applications:
    • Get: Retrieve Application
  • Candidates
    • GET: Retrieve Candidate
    • POST: Add Note
  • Job Posts
    • GET: List Job Posts
    • GET: Retrieve Job Post for Job
    • GET: List Job Posts for Job
  • Tags
    • POST: Add New Candidate Tags
    • PUT: Add a candidate tag

Once the API Key has been created with the above permissions, navigate to the SlateAI Dashboard where you will be prompted to enter your newly created API credentials. You may be prompted to login first.

Retrieve user ID

SlateAI will need a Greenhouse Recruiting user ID to associate with updates and changes created by the integration.

Note: We recommend creating an integration system user (ISU) to associate with partner updates. Rather than requiring a specific user at your organization to authenticate an integration, which could cause downstream errors if the person loses permissions or cannot access Greenhouse Recruiting, an ISU allows you to create a solid infrastructure for your organization's integration needs. Learn more.

Click the Configure icon on your navigation bar and then click Users on the left. 

Click Export to Excel.

A spreadsheet will be downloaded to your computer. Open the Excel file and locate the user ID in the User ID column. 

Create webhooks

Once you have successfully added the API Key, you will need to create two (2) webhooks: Candidate Delete and Application Created. Follow the steps in this article to create your webhook. SlateAI provides a helper UI to validate that everything is configured correctly. 

Use the values listed below to configure the webhook:

Candidate Delete

  • Name: SlateAI - Candidate Deleted
  • When: Delete candidate
  • Endpoint URL: Copy from the SlateAI UI above.
  • Secret Key: Copy from the SlateAI UI above.

Application Submitted

  • Name: SlateAI - Application Submitted
  • When: Candidate has submitted application
  • Endpoint URL: Copy from the SlateAI UI above.
  • Secret Key: Copy from the SlateAI UI above.

Use the SlateAI integration with Greenhouse Recruiting

Once you have added both webhooks, click the “Refresh” button in the SlateAI UI. If everything has been set up correctly, you should see the main SlateAI dashboard. Candidate Summaries, Applicant Assistants, and Job Assistants will now be created as applicants are submitted for every role your company is hiring for.

Viewing an Applicant Summary

When you click on an applicant, you will see the following view which shows the summary that was generated for a particular applicant for a specific job posting.

The summary will have the following information:

  • Score - This score describes how much of a fit this applicant is for the role. The score can range from 1-10 where 10 is a perfect candidate and 1 is an extremely poor fit.
  • Score Rationale - This briefly summarizes why the applicant received the above score.
  • Candidate Summary - This summary provides a summary of the candidate as extracted from the resume they used to submit the application.
  • Why Candidate Is A Fit - This section describes why the candidate may be a fit for a role (if at all).
  • Why Candidate Is Not a Fit - This section provides information on why the candidate might not be a fit (if any).
  • Questions for Phone Screen - This section provides additional questions that a recruiter or hiring manager could ask the candidate during a phone screen to gain additional insights or signal on the applicant.

Additionally, each candidate summary provides an additional overview of Skill Alignment or how well the candidates skills match the role.

Using an Applicant Assistant

If you subscribed to have Applicant Assistants, each candidate summary will have an option to navigate to the assistant screen.

It will take you to the following screen where users can leverage an assistant to help collate information about the candidate. You can include interview feedback, answers to phone screen questions, and anything else that you believe the AI could use to help you make a more informed decision.

Using the Job Assistant

If you subscribed to have Job Assistants, each unique job posting that is created will have a job assistant provisioned for it once an applicant has applied to that posting. Job Assistants enable hiring teams to efficiently search across a candidate pool for a specific posting for high quality applicants. Additionally, the assistant makes it easy to compare and contrast candidates and better understand the nuances between each candidate and how they might add value to your organization.

Additional resources

For additional information not covered here, reach out to support@slatehire.com.