Skip to main content
These docs are for Greenhouse v3, which connects with OAuth. All new integrations and existing integrations should be set up or updated to v3. If you need docs for the legacy Greenhouse v1 integration (Harvest API key), click here.
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. The Greenhouse v3 integration connects using OAuth, so there is no need to manually create or share a Harvest API key. Metaview’s access tokens are issued and refreshed automatically once you authorize the connection.

Set up integration

Greenhouse Site Admin required. Only a Greenhouse Site Admin can complete this connection. Authorizing without Site Admin permissions will fail to grant the access Metaview needs. If you’re not a Greenhouse Site Admin, ask someone who is to complete the connection.
1. Open your Integration settings in Metaview Navigate to https://my.metaview.app/?settings=integrations. If you haven’t previously signed in to Metaview you will be prompted to do so. Find the Greenhouse tile and click Connect Greenhouse. 2. Enter your Greenhouse subdomain Enter your Greenhouse account subdomain — this is the part before .greenhouse.io in your Greenhouse URL (for example, if your Greenhouse URL is https://acme.greenhouse.io, your subdomain is acme). 3. Authenticate with Greenhouse Click Authenticate with Greenhouse. You will be redirected to Greenhouse to sign in and authorize Metaview’s access. Greenhouse authorize Metaview 4. Authorize Metaview’s access Sign in to Greenhouse (as a Site Admin) and review the list of permissions Metaview requests. These permissions allow the full functionality of the Metaview – Greenhouse integration. Click to authorize the connection. Authorize Metaview to use your Greenhouse account
Metaview requests the following access. Some permissions are only used by optional features (for example, posting notes or adding sourced candidates); without them the related feature won’t be available.Applications:
  • List Applications
  • Create Applications
  • Move Applications
  • Reject Applications
  • List Application Stages
Candidates:
  • List Candidates
  • Create Candidates
  • List & Create Candidate Educations
  • Create Candidate Employments
  • List Candidate Tags & Applied Candidate Tags
Jobs:
  • List Jobs
  • List Job Posts
  • List Job Hiring Managers
  • List Job Interview Stages
  • List Job Owners
  • List Openings
Interviews & Scorecards:
  • List Interviews
  • List Interviewers
  • List Scorecards
Notes & Attachments:
  • List & Create Notes
  • List & Create Attachments
Organization & metadata:
  • List Departments
  • List Offices
  • List Sources
  • List Offers
  • List Close Reasons
  • List Rejection Reasons
  • List Email Templates
  • List Custom Field Options
  • List EEOC data
Users & permissions:
  • List Users
  • List User Roles
  • List User Job Permissions
5. You’ll be redirected back to Metaview After authorizing the connection, you will be taken back to Metaview, where the Greenhouse integration will show as “In progress”. It can take up to 48 hours for the integration to complete, and you will be emailed once the integration is successful.
If the connection fails, the most common cause is authorizing without Greenhouse Site Admin permissions. Verify you are a Site Admin and try again. If you have double-checked this and the connection still fails, please contact our team.

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
  • Data enrichment of candidate profile (e.g. name, job title, stage, location, CV)
  • Automatic addition of links to Metaview notes in Greenhouse
  • Provide Access to calls for users with Recruiter and Hiring Manager roles in ATS
  • Use AI Sourcing to search through your ATS for potential candidates
  • Add new candidates to your ATS that have been sourced
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).”

Scorecard Submission Browser Extension

Metaview offers a Chrome Extension you can use to automatically fill our your scorecard, direct within Greenhouse. You can also download and use this browser extension with the Microsoft Edge browser using the same instructions.
Simply download the Metaview Chrome Extension, open your scorecard in Greenhouse, and Metaview will extract objective sections of your scorecard and automatically fill it with information shared by the candidate in the interview. 1. Add the Extension to Chome Navigate to the Chrome Web Store and navigate to the Metaview Chrome Extension. Click Add to Chrome and then Add 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. Metaview will not overwrite any sections you’ve already filled in.
Save time and keep a consistent note structure by pulling your full Metaview note template into Greenhouse with one click. In Greenhouse, add a scorecard section titled “Metaview Notes” (exact title), and in Metaview ensure a note template is set for that role or call type. Enterprise customers can use custom section names—contact your Customer Success Manager to set this up.
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.

AI Sourcing

It is possible to add candidates you have found with AI sourcing to your Greenhouse instance. The only prerequisites to this are the following:
  • You have the Metaview-Greenhouse integration set up, as detailed above
  • You have added a Metaview source to Greenhouse. This is so that candidates sourced through Metaview can be attributed correctly.
With the Metaview-Greenhouse integration it is possible to use AI sourcing to find candidates already in your Greenhouse data. To enable this feature on your Metaview account, just contact us and ask for the AI Sourcing - Greenhouse integration to be enabled.

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 our team 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.

Disconnect your Greenhouse integration

You can disable your Metaview integration directly from within your Metaview account under SettingsIntegrations then select Disconnect Greenhouse. This immediately disconnects Metaview from your ATS data. Please note however that any calls that have already been scheduled may still go ahead. Please see Disabling Metaview for details on how to also make sure that the Notetaker bot doesn’t join any future calls.