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

​
Connect Ezekia to Metaview

1. Navigate to Settings -> Integrations -> API Tokens You can navigate to integrations by bringing up the side menu, clicking Settings and then Integrations on the left menu. Then select the API Tokens tab at the top. 2. Generate new API Token Once on the API Tokens page, select Generate new token. Name the token “Metaview”, select No Expiry for expiration, enter a username which has Admin permissions and then click Save. At this point, you’ll have a chance to copy the token. Ensure you have done so before quitting this dialog as this is the only opportunity to see the token - otherwise you will have to generate a new one! 3. Share Ezekia token with Metaview Navigate to https://my.metaview.app/settings/ezekia. If you haven’t previously signed in to Metaview, you will be prompted to do so. Enter the API key into the corresponding 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 Ezekia ATS to Metaview unlocks the following features:
  • Automatic scheduling directly from ATS
  • Employees sync
  • Automatic enrichment of Call details (e.g. candidate name, job title, location)
  • Ability to send AI-generated notes from Metaview back to Ezekia
When a call was scheduled through Ezekia or was matched to data in Ezekia, you will see the ATS logo in Metaview. Click on the``Ezekia logo go to the matched entry in your ATS.

​
Troubleshooting

When a call was not scheduled through Ezekia, 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:
  • 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.