Skip to main content
Metaview integrates with iCIMS. This enables enhanced candidate metadata, automated team management, Application Review, and Sourcing — helping your team work more efficiently and make better hiring decisions.
The iCIMS integration is currently in beta. If you experience any issues, please reach out to support@metaview.ai.
Paid API access required. To integrate iCIMS, you need to sign a Statement of Work (SOW) with iCIMS for the integration project. iCIMS does not publicly disclose pricing for this. The time from signing the SOW to kicking off the integration project is usually 6–8 weeks.

​
Connect iCIMS to Metaview

In Metaview, go to Settings → Integrations, find iCIMS, and click Connect. Follow the on-screen flow to complete the setup.

​
Permissions

The iCIMS connection is authorized through Kombo as a whole — there are no individual permissions for you to select. Metaview uses that access to match your calls to the right candidate and role, enrich candidate profiles, keep your team in sync, and write Notes and other Metaview information back to iCIMS.
Kombo is a Metaview subprocessor. Our current subprocessor list is published in the Trust Center, and the terms covering this processing are set out in our DPA. See also Privacy and security.
Anything under Optional is only used by an individual feature — without it, the core integration still works.
Required
  • Jobs
  • Candidates
  • Applications
  • Application stages
  • Users
Optional
  • Create candidates and applications
  • Move or reject an application
  • Write to a configured application File field
  • Read application and candidate attachments

​
Features

Integrating your iCIMS ATS to Metaview unlocks the following features:
  • Enhanced candidate metadata (e.g. name, job title, stage, location, CV)
  • Automated team management with employees sync
  • Add your CV as an attachment to the candidate’s application
  • Use Application Review to screen and progress candidates; rejection moves candidates to your configured rejected stage
  • Use Sourcing to search through your ATS for potential candidates
  • Add new candidates to your ATS that have been sourced
  • Move candidates to different stages in your pipeline
Attachments in iCIMS are limited to CV/resume files only. Other attachment types are not supported.

​
What’s not supported

  • Automatic scheduling — iCIMS does not support an interviews model, so Metaview cannot automatically schedule calls from this ATS. You will need to schedule interviews via your calendar or other scheduling tools.
  • Links to Metaview notes — iCIMS does not support adding Metaview note links to the ATS.
  • Scorecards — Scorecard data is not available through this integration.

​
Troubleshooting

Since iCIMS does not support automatic scheduling, Metaview will 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 us 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.

​
Disconnect your iCIMS integration

You can disable your Metaview integration directly from within your Metaview account under Settings → Integrations then select Disconnect iCIMS. This immediately disconnects Metaview from your ATS data. Please note however that any calls that have already been scheduled may still go ahead. Please see Disabling Metaview for details on how to also make sure that the Notetaker bot doesn’t join any future calls.