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

​
Connect Bullhorn to Metaview

To set up a Bullhorn integration, you will need to be an Admin of your company’s Bullhorn account. Currently it is only possible to complete your integration using OAuth.

​
Using OAuth

1. Start OAuth authentication Navigate to https://my.metaview.app/settings/bullhorn Image 2. Authorize Metaview’s access Select Authenticate with Bullhorn. You will be taken to Bullhorn, and asked to sign in. To ensure Metaview can join calls scheduled in Bullhorn, as well as push AI Notes back to Bullhorn, it is essential to log in with an account with admin permissions. 3. You will be redirected to Metaview After approving the integration, you will be taken back to Metaview, where the Bullhorn 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.

​
Integration Features

Integrating your Bullhorn ATS to Metaview unlocks the following features:
  • Automatic scheduling directly from ATS
  • Employees sync
  • Ability to post your AI Notes to ATS with one click.
    • You can also post AI Notes with custom actions. Action types are synced from Bullhorn, and the default is “No Action”. If you want to turn on custom actions for your Bullhorn instance, please reach out to support@metaview.ai
  • Ability to post your 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 Bullhorn or was matched to data in Bullhorn, you will see the ATS logo in Metaview. Click on the``Bullhorn logo go to the matched entry in your ATS.

​
Troubleshooting

When a call was not scheduled through Bullhorn, 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)
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.