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. Request API login details from Bullhorn Contact bullhorn support and ask for your organization’s API account login details. They should provide you with a username and password for a specific API account, which should only be used in the following steps and not used for regular login via the Bullhorn Platform. When getting in contact, you should also supply the following information:- A link to Metaview’s Terms of Service: https://www.metaview.ai/terms-of-service
- The Metaview redirect URL: https://my.metaview.app/settings/bullhorn/oauth/callback
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 the specific API account you acquired details for in step 1.
If you are logged into Bullhorn on your browser already then it will automatically use these login details, which are likely not the correct API account details. To avoid this, it is best to do the setup in an incognito window, or ensure you have logged out of Bullhorn before clicking
Authenticate with BullhornIntegration 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
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)

