Metaview integrates seamlessly with Gem ATS. This makes it possible for Metaview to automatically capture scheduled interviews in Gem so we can provide AI-generated summaries.
This API integration with Metaview is designed specifically for Gem ATS customers. Teams using only Gem’s CRM will not be able to make full use of the integration even if your API key is valid.

​
Connect Gem to Metaview

1. Your API key can be found within Gem.
  1. Navigate to Team Settings -> Additional Settings.
  2. If you don’t already have Gem API added, scroll to the bottom and press Create API Key.
  3. Copy the API key.
2. Share Gem API key with Metaview Navigate to https://my.metaview.app/settings/gem If you haven’t previously signed in to Metaview, you will be prompted to do so. Enter the API key into the field. Image 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.

​
Features

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

​
Troubleshooting

When a call is not scheduled through Gem’s ATS, Metaview will still attempt to match your calls scheduled by other means to relevant entries in your ATS. The most common reasons why this doesn’t happen automatically are:
  • Your team does not use Gem ATS. Teams that only use Gem’s CRM features will not be able to use scheduling or scorecard features.
  • 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.