Greenhouse

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

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

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:

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 in the Metaview Greenhouse setup page.

After saving your changes, the integration process will start. This can take up to 48 hours to complete, and you will be emailed once the integration is successful.

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:

• directly from ATS

• Employees sync

• Ability to view your ATS scorecards from Metaview

• Ability to post your notes and to Greenhouse with one click

• Automatic enrichment of (e.g. candidate name, job title, stage, location)

• Automatic addition of links to Metaview notes in Greenhouse

• Provide 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.

Click on the Scorecard icon (if available) to see the relevant Greenhouse scorecard for your call.

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 or options).

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.