Connect Workable to Metaview
1. Open theMetaview integration in Workable
As a Super Admin, go to the Integrations section of your Workable account, then under Service Integrations → Other Integrations click the Metaview item. You can go straight to this link, or follow the steps in the GIF below.
Metaview integration item, click Generate token and copy the token. Make sure you generate it here, not from the API Access Tokens section.
Save.
Permissions
Metaview uses this 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 Workable. The Metaview service integration in Workable grants Metaview a fixed set of permissions, so individual items can’t be deselected during setup. This is a direct connection — no third-party integration partner is involved. Anything under Optional is only used by an individual feature — without it, the core integration still works.View list of permissions
View list of permissions
Required
r_candidatesr_jobsw_candidates
- Candidate creation (covered by
w_candidates)
This is why the token has to come from the
Metaview service integration item. Tokens created in API Access Tokens do not carry w_candidates, so nothing can be written back to Workable — see the warning above.Features
Integrating your Workable ATS to Metaview unlocks the following features:- Automatic scheduling directly from ATS
- Employees sync
- Ability to post your Notes to ATS with one click
- Data enrichment of candidate profile (e.g. name, job title, stage, location, CV)
- Automatic addition of links to Metaview notes in ATS
- Use Application Review to screen, progress, and reject candidates
- Use Sourcing to search through your ATS for potential candidates
- Add new candidates to your ATS that have been sourced
Workable logo go to the matched entry in your ATS.
Troubleshooting
When a call was not scheduled through Workable, 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.
Disconnect your Workable integration
You can disable your Metaview integration directly from within your Metaview account underSettings →Integrations then select Disconnect Workable.
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.