Skip to main content
Metaview integrates with SAP SuccessFactors. This enables enhanced candidate metadata, automated team management, Application Review, and Sourcing — helping your team work more efficiently and make better hiring decisions. Connecting SuccessFactors means creating a dedicated API user, granting it the permissions Metaview needs through a permission group and role, and registering an OAuth2 client application to generate an API key. Setup usually takes around 30 minutes.
You will need SAP SuccessFactors administrator access to complete this setup — without it, you will not be able to open the configuration pages described below. If you are not an admin, ask your SuccessFactors admin to run the setup instead.The OData v2 API also needs to be available and enabled on your instance. It is enabled by default, so this is usually not something you need to check.

​
Connect SAP SuccessFactors to Metaview

In Metaview, go to Settings → Integrations, find SAP SuccessFactors, and click Connect SAP SuccessFactors. The connection flow opens and walks you through the setup one screen at a time. The first screen lists the categories of data Metaview will request from SuccessFactors — users, jobs, job postings, candidates, applications, application stages, and so on. Review them and click Continue. From there, the flow collects your API domain, your company ID, and the user ID of a dedicated API user; shows you the permissions to configure in SuccessFactors; and finally asks for an API key. The steps below cover what you need to do in SuccessFactors at each point. Keep the connection flow open throughout. You will paste values into it as you go, and you will need to copy a certificate out of it in step 6.
Kombo, our integration provider, publishes a step-by-step SuccessFactors connection guide with screenshots of each SuccessFactors screen. It is a useful companion to the steps below.

​
1. Find your API domain

Your API domain depends on the data center your SuccessFactors instance runs in.
  1. Open SAP’s SuccessFactors API URLs list.
  2. Filter for production environments, unless you are connecting a preview instance.
  3. Find your location and copy the corresponding API Server domain. An instance based in Germany, for example, would use https://api012.successfactors.eu/.
Paste it into the API Domain field in the Metaview connection flow. If you use a custom or proxied domain, enter that instead.
Your API domain usually resembles the domain you log in on — the API for pmsalesdemo8.successfactors.com, for example, is at apisalesdemo8.successfactors.com.
There is no way to look up the API domain directly in the SuccessFactors UI. If you are unsure which data center your instance runs in, SAP recommends contacting your SAP representative.

​
2. Find your Company ID

In SuccessFactors, click your profile picture in the top right and select Show version information. Copy the value next to Company ID and paste it into the Company ID field in the Metaview connection flow.

​
3. Create a new user

Metaview connects as a dedicated API user rather than as one of your team members.
  1. In the admin center search bar, enter Import Employee Data and open the action.
  2. Click Import Data, then Download Template.
  3. Click the field next to Select an entity, choose Basic Import, then click Generate Template.
  4. Open the .csv file you receive — it will usually contain two rows. Add a row for your API user, filling out at least these fields: Every value here is an example — you can use anything you like, and the email does not need to be a real address. We recommend something recognizable like SFAPI_METAVIEW so the user is easy to identify later.
  5. Click Download Template, then Import Data to switch back.
  6. Select Basic Import as the entity again, click Browse, and select your .csv file.
  7. Click Validate Import File Data. Once you see the Validation Successful dialog, click Import.
Always generate the template from your own instance. SuccessFactors instances are configured differently, so a template taken from anywhere else will not import correctly.
Keep the .csv file to hand — you will need the User ID again in step 6. Enter that User ID in the User ID field of the Metaview connection flow.
To confirm the user was created, search for its first and last name or its username under People. New users can take a few minutes to appear in search.

​
4. Create a permission group

  1. In the search bar, enter Manage Permission Groups and open the action.
  2. Click Create New and give the group a name (e.g. Metaview Integration).
  3. Click Pick a category and select Username.
  4. Search for the user you created in step 3 by its username, tick the box next to it, and click Done.
  5. Check that the user now appears in the people pool, then click Done to save the group.

​
5. Create a permission role

  1. In the search bar, enter Manage Permission Roles and open the action.
  2. Click Create, enter a name for the role (e.g. Metaview Integration), and click Next.
  3. Grant the permissions listed under Permissions. For each category heading, find the matching permission category in the SuccessFactors sidebar, then tick the individual permissions within it.
  4. Click Next, then Save, then Yes to confirm.
  5. Give the role assignment a name and click Next.
  6. On the Grant Access To tab, click Select Groups, search for the permission group you created in step 4, select it, and click Select.
  7. Check that your permission group is listed, click Next, then Save.
The permission categories are long. Use Ctrl+F (Cmd+F on a Mac) and paste in the permission name to find it quickly.

​
6. Register an OAuth2 client application

  1. In the search bar, enter Manage OAuth2 Client Applications and open the action.
  2. Click Register Client Application.
  3. Enter a name (e.g. Metaview) and any valid URL beginning with https:// — the URL is not used, so any value works.
  4. Tick Bind to Users and click OK, then enter the User ID of the user you created in step 3.
  5. Copy the X.509 certificate from the Metaview connection flow, paste it into the certificate field, and click Register.
Do not click Generate X.509 Certificate. The connection has to use the certificate shown in the Metaview connection flow — generating a new certificate in SuccessFactors will cause the connection to fail.

​
7. Copy your API key and finish the connection

Your new client application appears at the top of the Manage OAuth2 Client Applications list. Click View, copy the value next to API Key, and paste it into the API Key (Client ID) field in the Metaview connection flow. With all four values entered — API domain, company ID, user ID, and API key — click Set up integration. You should see Connection set up successfully!, confirming that Metaview can start syncing your SAP SuccessFactors data and that there is nothing left for you to do. Syncing then begins in the background. This can take up to 48 hours to complete, and you will be emailed once the integration is successful.

​
Permissions

Metaview connects to SAP SuccessFactors through Kombo, an integration provider that sits between Metaview and your ATS. Kombo normalises the differences between ATS APIs and data models, and handles much of the authentication, syncing, and ongoing maintenance. These are the permissions you need to grant to the permission role in step 5. Metaview uses them 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 SAP SuccessFactors.
Manage System Properties
  • Picklist Management and Picklists Mappings Set Up
Recruiting Permissions
  • OData API Job Requisition Export
  • OData API Application Create and Update Validation Bypass for Required Fields
  • OData API Application Create
  • OData API Application Update
  • OData API Candidate Create
  • OData API Candidate Update
  • OData API Candidate Export — also used to deduplicate candidates
  • OData API Application Export
  • OData API Create/Update Interview Central
Employee Central API
  • Employee Central Foundation OData API — optional, used to retrieve job locations
Manage Integration Tools
  • OData API Attachment Import
The connection flow in Metaview shows the definitive list for your workspace. If it differs from the list above, follow the connection flow.
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.

​
Features

Integrating your SAP SuccessFactors 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 Notes to the candidate’s job application as a PDF with one click. It is attached with the attachment type OTHER — usually under Resume and Documents → Additional Documents — and named after the call, for example Interview_with_Jane_Doe.pdf
  • A link to your Metaview notes posted to the application’s Comments tab, in the form Metaview link for [interview title]: [URL]
  • Use Application Review to screen candidates
  • 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
  • Reject applications directly from Metaview
The Notes link is written to SuccessFactors’ standard comments field (field ID comments). That field needs to be present and permissioned in your Job Application Template for the link to appear. This is standard SuccessFactors configuration — no custom field is required.

​
What’s not supported

  • Automatic scheduling — Metaview cannot currently schedule interviews directly from SAP SuccessFactors. You will need to schedule them through your calendar or another connected scheduling tool.
  • Scorecards — Scorecard data is not available through this integration.
There is very little to configure once the integration is connected: the features above are deliberately not configurable, and most actions happen automatically without any setup of their own. Integrations run against production Metaview data only. If something does not behave as you expect, contact support.If you would like a more hands-on rollout — guided implementation and enablement from our team — that is available on our Enterprise plans.

​
Troubleshooting

Since SAP SuccessFactors 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
  • Several applications for the same candidate that Metaview cannot tell apart. If only one was active around the time of the interview, Metaview selects that one; otherwise the call is left unmatched, and Notes cannot be posted until it is matched to the right application
  • 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 SAP SuccessFactors integration

You can disable your Metaview integration directly from within your Metaview account under Settings → Integrations then select Disconnect SAP SuccessFactors. 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.