Metaview integrates seamlessly with Greenhouse. This makes it possible for Metaview to automatically capture scheduled interviews in Greenhouse so we can provide AI-generated summaries.

​
Set up integration

1. Configure > Dev Center > API Credential Management Go to the”API Credential Management” section of Greenhouse’s Dev Center page. You can do this by either using this link, or by following the steps in the recordings below. Note: If you don’t see the Dev Center, follow the instructions provided by Greenhouse to get access to the Dev Center. Alternatively, you can ask someone with appropriate access to configure this integration. API Credential Management - Watch Video Image 2. Generate new Harvest API Key Once in the API Credential Management page, click the “Create New API Key” button. From the “Type” dropdown select “Harvest”. In the “Partners” box, search for and select “Metaview”. This should automatically name the key “Metaview Harvest API Key”. Click “Manage Permissions”. Create New Credential - Watch Video Image 3. Copy the generated key Copy the new key. You will only be able to see the key at this point, so you must copy it before proceeding. 4. Configure new key The newly generated key should have the required permissions automatically set. Check that the key has the following permissions:
Activity Feed:
  • GET: Retrieve Activity Feed
Applications:
  • GET: Retrieve Application
  • GET: List Applications
Candidates:
  • GET: Retrieve Candidate
  • GET: List Candidates
  • POST: Add Note
Close Reasons:
  • GET: Get close reasons
Departments:
  • GET: Retrieve Department
  • GET: List Departments
Job Openings:
  • GET: List Openings For a Job
Job Posts:
  • GET: List Job Posts
  • GET: Retrieve Job Post for Job
  • GET: List Job Posts for Job
Job Stages:
  • GET: Retrieve Job Stage
  • GET: List Job Stages
  • GET: List Job Stages for Job
Jobs:
  • GET: Retrieve Job
  • GET: List Jobs
  • GET: Get hiring team
Offices:
  • GET: Retrieve Office
  • GET: List Offices
Rejection Reasons:
  • GET: List Rejection Reasons
Scheduled Interviews:
  • GET: List Interviews for Application
  • GET: Retrieve Interview
  • GET: List Interviews
Scorecards:
  • GET: Retrieve Application’s Scorecard
  • GET: List Scorecards for Application
  • GET: Retrieve Scorecard
  • GET: List Scorecards
Sources:
  • GET: List Sources
Tags (Optional):
  • GET: List tags applied to candidate
  • GET: List Candidate Tags
User Roles:
  • GET: List User Roles
Users:
  • GET: Retrieve User
  • GET: List Users
  • GET: List User Job Permissions
Once you’ve selected the permissions above, click “Update” at the bottom of the page. 
5. Share Greenhouse Harvest API Key with Metaview Copy the API key, then navigate to https://my.metaview.app/settings/greenhouse. If you haven’t previously signed in to Metaview you will be prompted to do so. Enter the API key into the corresponding field. Before saving, you’ll also need to sign into Greenhouse and copy the URL from the browser address bar (it will end in “.greenhouse.io”). Enter it into the corresponding field on the Metaview Greenhouse setup page. Image If the test is successful, you must click Save Changes to start the integration process. This can take up to 48 hours to complete, and you will be emailed once the integration is successful.
If the Test API Key step fails, verify your entries and please try again. If you have double-checked the steps and the test has failed 3 times, please contact support@metaview.ai.

​
Posting to Greenhouse

Sometimes Metaview will comment on a candidate’s profile in Greenhouse. Examples of why Metaview will do this include:
  • adding a URL to the conversation to the candidate’s page
  • posting the full AI Notes to the candidate’s profile
All comments in Greenhouse need to be added as a user. Metaview therefore needs to find a Greenhouse user with the required permission to add the comment. Metaview, by default, picks a Greenhouse whole-site admin, and posts as this user. However, a better solution is to post as “Metaview”. To enable “posting as Metaview”, you need to create an account in Greenhouse with the email “metaview@<company-domain>” and make this user a full site admin. Then, Metaview will be able to use this “user” to write to the candidate’s profile in all contexts and the notes will appear as coming from “Metaview”.

​
Features

Integrating your Greenhouse ATS to Metaview unlocks the following features:
  • Automatic scheduling directly from ATS
  • Employees sync
  • Ability to view your ATS scorecards from Metaview
  • Ability to post your notes and TLDR to Greenhouse with one click
  • Automatic enrichment of Call details (e.g. candidate name, job title, stage, location)
  • Automatic addition of links to Metaview notes in Greenhouse
  • Provide Access to calls for users with Recruiter and Hiring Manager roles in ATS
When a call was scheduled through Greenhouse or was matched to data in Greenhouse, you will see the Greenhouse logo in Metaview. Click on the``Greenhouse logo go to the matched entry in your ATS. Image

​
Scorecards

The scorecard will be available whenever Metaview successfully matches your call to a Greenhouse interview that includes a scorecard. Click on``Fill Scorecard to see the relevant Greenhouse scorecard for your interview. Image Metaview automatically fills in parts of your scorecards based on what was said in the interview. However, some fields are intentionally left blank. If a field is too vague or prompts personal evaluation or subjective judgment, Metaview will skip it to avoid making assumptions and ensure accuracy. Metaview does not evaluate candidates or make hiring decisions, and we want to avoid influencing the interviewer’s assessment by prefiling these types of fields.
To improve the relevance of what is auto-filled, make sure your scorecard headings and field descriptions are as clear and specific as possible. For example, instead of “General Thoughts,” try “Candidate’s Communication Style (with examples).”
Please note that currently, you cannot submit your Greenhouse scorecard directly from within Metaview.

​
Scorecard Submission Browser Extension

While you cannot submit your scorecard from within Metaview, we do have a browser extension available for Chrome that once downloaded, will allow you to automatically fill in the objective questions in your scorecards, as outlined below.
1. Add the Extension to Chome Navigate to the Chrome Web Store and navigate to the Metaview Chrome Extension. Click “Add to Chrome” and thenAdd Extension. Integrations Greeenhouse Extension Pn 2. Navigate to a Scorecard in Greenhouse Where Metaview Joined At the top of the page, you’ll see a Metaview banner with the call for this interview. ClickAutofill with Metaview to fill in the relevant sections from the scorecard. Note that Metaview will not overwrite any sections where you previously had entered your own notes GH scorecard 3. Review and Personalize the Outputs, Add in Your Evaluation, and Submit When Metaview finishes processes and posts the relevant updates, review the output, personalize, fill in the relevant scoring fields that have intentionally been left blank, and clickSubmit Scorecard.

​
Troubleshooting

When a call was not scheduled through Greenhouse, Metaview will still attempt to match your calls scheduled by other means to relevant entries in your ATS. This can take up to 30 minutes if your call was not scheduled in advance. If ATS data sync is not successful or if your scorecard does not appear automatically, the most common reasons why are:
  • Call or candidate is missing in the ATS
  • Duplicate calls or candidates in the ATS
  • Data mismatch between Metaview invite and information in ATS (e.g. wrong participants, missing participant, wrong candidate)
  • Insufficient information to match call or candidate (often occurs when using Inviting to an ongoing call or Upload recordings options).
  • The meeting type is NOT set to Job interview or Debrief. Please see Call details for more information.
If you believe that a Metaview call was not matched or was incorrectly matched to your ATS data, please reach out to support@metaview.ai and provide as much data as possible for our team to properly investigate. Please provide specific examples and the relevant IDs (e.g. application ID, candidate ID) from your ATS.