Skip to main content
Metaview integrates with Workday Recruiting. This enables enhanced candidate and requisition metadata, automated team management, your Notes added to the candidate’s profile as a PDF, Application Review, and Sourcing — helping your team work more efficiently and make better hiring decisions. The integration connects to Workday over SOAP Web Services and uses custom reports for questionnaire and recruiting-step metadata. To connect your Workday tenant to Metaview, you will need to create an Integration System User (ISU), configure a security group with the required permissions, and provide your credentials to Metaview.
You will need Workday administrator access to complete this setup.

​
Connect Workday Recruiting to Metaview

​
1. Create an Integration System User (ISU)

From the Workday search bar, search for Create Integration System User. Create a new ISU that will be used exclusively for the Metaview integration (e.g. ISU_Metaview). Set a password for the ISU and make a note of both the username and password — you will need these later.
We recommend naming the ISU something recognizable like ISU_Metaview so it’s easy to identify in your security configuration.

​
2. Create a security group and assign the ISU

Search for Create Security Group in the Workday search bar. Create a new Integration System Security Group (Unconstrained) and name it appropriately (e.g. ISSG_Metaview). Create Security Group Once the security group is created, add the ISU you created in Step 1 as a member of this group. Edit Security Group — assign ISU

​
3. Maintain domain permissions for the security group

Search for Maintain Permissions for Security Group in the Workday search bar. When prompted, select Maintain (not Copy) as the operation, and choose the security group you created in Step 2. Maintain Permissions for Security Group — select Maintain On the Domain Security Policy Permissions tab, add the permissions listed below. Each permission needs the correct View/Modify Access level (Get Only, Get and Put, or View and Modify) and the corresponding Domain Security Policy. See Permissions for the Workday operations these grants back.
If you are setting up the optional recruiting stage and step report in Step 6, give the same security group view access to:
  • The Business Process Definitions data source and its data-source filter
  • Business Process Reporting (View Only)
  • Business Process Definition, Business Process Type, Business Process Steps, Workflow Step Alternate Name, Step Type, Workday ID, and Reference ID report fields
  • Analytics Data: Report Fields and Values (View and Modify), if separately secured in your tenant
Use Security Analysis for Securable Item and Account to find any missing grants. The View and Modify grant to Custom Report Creation above covers report ownership. You do not need Manage: All Custom Reports.
You can also find the security group from the View Integration System Security Group page and use the actions menu to navigate directly to Maintain Domain Permissions for Security Group.View Security Group — actions menu

​
4. Grant business process permissions

Application Review’s progress and rejection decisions run as Move Candidate actions on your Job Application business process. This requires a business process security policy grant in addition to the domain permissions above — without it, decisions made in Metaview cannot be applied in Workday. In the same Maintain Permissions for Security Group task, open the Business Process Security Policy Permissions tab and add:
If you prefer, you can grant this from the business process side instead: search for Edit Business Process Security Policy, select the Job Application business process type, and add your Metaview security group to the Move Candidate (Job Application) initiating action.

​
5. Activate pending security policy changes

After configuring permissions for the reports you need, activate them once. Search for Activate Pending Security Policy Changes in the Workday search bar and follow the prompts. Activate Pending Security Policy Changes
Permissions will not take effect until you complete this activation step.

​
6. Create the metadata reports

Create the reports you need while signed in as a Workday administrator. Use Create Custom Report, not Create Temporary Custom Report. The questionnaire report supports interview scorecards; the recruiting stage and step report provides optional metadata and is not required for candidate sync. If you create both, do them in the same session, then transfer ownership and check the URLs together at the end of this step.

​
Questionnaire metadata report

Metaview uses this report to read the format of interview questionnaires, including each question’s type and available choices. It does not contain candidate answers. Configure the report: Add the following columns and XML aliases. Workday limits XML aliases to 16 characters; every alias below is within that limit. Aliases marked Required must match exactly. Under Group Column Headings, add both groups. Workday requires a heading for each subgroup before the report will validate. Workday questionnaire report fields and subgroup aliases
The report name, report owner, and required XML aliases form the integration contract. Other display headings, descriptions, comments, column order, and the generated namespace can be changed.
Save and run the report. Confirm that interview questionnaires show question types and that selector questions show their possible answers. Workday questionnaire report results

​
Recruiting stage and step metadata report

This report returns the names and types of steps inside recruiting business processes. It contains no candidate data. The ISU permissions are covered in Step 3. Configure the second report: On the Columns tab, add these fields. The XML aliases must match exactly: Under Group Column Headings, group the Business Process Steps fields under a heading named Steps with XML alias Steps. Use Workflow Step Alternate Name, rather than the step reference’s descriptor. Descriptors can read “Screen from Screen” rather than the configured step name. On the Filter tab, set Business Process Type to in the selection list. Select the recruiting processes available in your tenant: Screen, Interview, Assess Candidate, Job Application, Review Candidate, Offer, Employment Agreement, Background Check, Reference Check, and Ready for Hire. Include tenant-specific recruiting process types if applicable. On Advanced → Web Services Options, confirm Enable as Web Service is checked. Use your tenant’s current API version and keep Workday’s generated namespace. Save and run the report. Check that each business-process definition includes Definition, Definition_WID, and Stage, and that its Steps entries include Step_Name, Step_Type, Step_WID, and Workflow_Step_ID. Check an actionable step such as Screen Candidate or Schedule Interview for both identifiers. Step names can repeat; initiation and conclusion steps may appear, and some conclusion steps have a blank Step_Type.
Workday can use the same Step_Name for multiple steps within one definition. Step_WID and Workflow_Step_ID identify the step; do not use the name alone to distinguish it. A Job Application Step Label Override, such as “Manager Screen” in the Move Forward menu, can still differ from the reported name. The report lists configured steps, not which moves are currently allowed for a particular application.

​
Finish the reports you created

  1. Confirm each report is not Temporary. If that setting is checked and cannot be cleared, ask a Workday Report Administrator to make the report permanent.
  2. Search for Transfer Ownership of Custom Reports. Select the reports you created and set New Owner to the ISU from Step 1. Check the Share tab on each report to confirm the ISU now owns it. The ISU username cannot contain a backslash (\) because Workday cannot run a RaaS report owned by that username.
  3. If you created the questionnaire report, share it with the Integration System Security Group from Step 2. The recruiting-step report does not need a separate share grant because the ISU owns it.
  4. Open Related Actions → Web Service → View URLs for each report you created. Confirm it has a JSON URL with the ISU from Step 1 as the report-owner segment. Metaview finds the ISU-owned reports automatically using the connected Workday host, tenant, username, and report names. You do not need to enter or send the URLs. Test them with the ISU in a secure client. Keep passwords and tokens out of URLs and shared documents.
Workday questionnaire report web-service URLs Workday questionnaire report web-service and temporary-report settings If the ISU is unavailable for ownership transfer or cannot run a report, use Security Analysis for Securable Item and Account to check the data source, filter, and fields from Step 3. For the questionnaire report, use View Security for Securable Item if its security group is not available in the Share picker. Grant the missing access and activate any new policy changes once before retrying.
Missing questionnaire-report access prevents Workday scorecards from loading. It does not block the rest of the Workday integration. Metaview supports Text, Number, Date, Multiple Choice - Single Select, and Multiple Choice - Multi Select questions. A questionnaire with a required attachment or unknown required question type cannot be completed in Metaview.

​
7. Find your Workday host and tenant

Search for View API Clients in the Workday search bar. From the REST API endpoint information displayed, identify:
  • Workday Host — the datacenter hostname in your Workday URL (e.g. wd5-impl-services1.workday.com or impl-services1.wd12.myworkday.com)
  • Workday Tenant — your tenant name, found in your service URLs after /ccx/service/ (e.g. acme_corp)
View API Clients

​
8. Connect your Workday tenant to Metaview

Navigate to https://my.metaview.app/?settings=workday. If you haven’t previously signed in to Metaview, you will be prompted to do so. Enter the following credentials: Click Connect to start the integration. Metaview will validate your credentials and permissions. If the connection is successful, the integration process will begin syncing your data. This can take up to 48 hours to complete, and you will be emailed once the integration is successful.

​
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 Workday. Metaview connects to Workday over SOAP Web Services and calls the operations below. These are backed by the domain security policies granted in step 3, plus the business process permission in step 4 for Move_Candidate. This is a direct connection — no third-party integration partner is involved.
Required
  • Get_Candidates
  • Get_Job_Requisitions
  • Get_Evergreen_Requisitions
  • Get_Interviews
  • Get_Interview_Feedbacks
  • Get_Web_Conference_Interview_Data
  • Get_Questionnaires
  • Get_Competencies
  • Get_Proficiency_Rating_Scales
  • Get_Workers
  • Move_Candidate
  • Put_Candidate
  • Put_Candidate_Photo
  • Put_Candidate_Attachment
  • Put_Interview_Feedback
Along with read access to candidate attachments and to your recruiting reference data.

​
Features

Integrating Workday Recruiting with Metaview unlocks the following features:
  • Worker and recruiting team member sync
  • Add your Notes as a PDF attachment to the Workday candidate profile with one click
  • Automatic enrichment of interview details (e.g. candidate name, job requisition title, recruiting step, location)
  • 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
  • View, complete, and submit assigned Workday interview scorecards from Metaview
  • Recruiting stage and step metadata from your configured business processes

​
Scorecards

When a Metaview interview matches a Workday interview event, Metaview reads the questionnaires and competencies assigned to each interviewer and creates the corresponding scorecard. Question IDs, requiredness, order, and selector-answer IDs continue to come from Workday Web Services; the custom report supplies the question type and body. Competency names and available proficiency ratings come from the Workday Talent service. Competency ratings are always selected by the interviewer. Metaview can draft an evidence comment for each rating from the interview conversation, which the interviewer can review and edit. After completing the scorecard in Metaview, select Submit Feedback. Metaview sends questionnaire answers, competency ratings and comments, and the overall comment together in one Workday feedback submission. Workday only accepts feedback while the interview event is in progress, and each interviewer can submit feedback once. If an assigned questionnaire is not available in Metaview, verify that the metadata report is permanent, owned by the ISU, shared with the ISU security group, and still uses the required XML aliases from Step 6. If a scorecard with assigned competencies is not available, verify that the ISU security group has Get Only access to Setup: Skills and Experience and Setup: Talent, then activate pending security policy changes. When your interview in Metaview matches to data in your Workday Recruiting instance, you will see the Workday logo in Metaview. Click on the Workday logo to navigate directly to the matched candidate’s application in Workday Recruiting.

​
Troubleshooting

Although Metaview does not automatically schedule interviews from Workday Recruiting, Metaview will still attempt to match your interviews scheduled by other means to the relevant applications and job requisitions in Workday. The most common reasons why this doesn’t happen automatically are:
  • Interview or candidate is missing in Workday Recruiting
  • Duplicate interviews or candidate applications in Workday
  • Data mismatch between Metaview invite and information in Workday (e.g. wrong participants, missing participant, wrong candidate name)
  • Insufficient information to match interview 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 interview was not matched or was incorrectly matched to your Workday data, please reach out to our team and provide as much data as possible for our team to properly investigate. Please provide specific examples and the relevant identifiers (e.g. Application ID, Job Requisition ID, Candidate ID) from your Workday Recruiting instance.

​
Disconnect your Workday integration

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