The Workday ↔ CertnCentric Integration enables organizations to seamlessly initiate and manage background checks directly from Workday as part of the recruiting or onboarding process. This integration eliminates manual data entry, improves compliance oversight, and ensures real-time status synchronization between Workday and CertnCentric.
The solution leverages Workday Core Connector: Background Check Order Outbound for order initiation and CertnCentric’s secure API (Put_Background_Check) for results ingestion and status updates back into Workday.
The integration streamlines background-check operations by automatically sending candidate data from Workday to Certn Centric when a Background Check Business Process (BP) is triggered and then updating Workday with results once screening is complete.
- Outbound: Workday automatically submits Background Check orders to Certn after the “Background Check” business process (BP) initiates.
- Inbound: Certn updates the candidate’s Background Check status/results in Workday via Workday Web Services (WWS).
Prerequisites
| Requirement | Description |
|---|---|
| Workday Tenant Access | Ability to create Integrations, Security Groups, and Background Check BPs. |
| CertnCentric Account | Integration endpoint and API credentials (Client ID, Secret, Refresh Token). |
| Network Access | HTTPS outbound traffic from Workday to Certn endpoint allowed. |
| OAuth 2.0 Connectivity | Verified refresh token exchange between Workday and Certn. |
| Package & Status Alignment | Packages, tests, and statuses in Workday mirror Certn values exactly. |
Integration architecture
| Component | Role |
|---|---|
| Core Connector – Background Check Order Outbound | Generates background check requests. |
| Document Delivery (HTTP/SSL) | Transmits JSON payload to Certn Centric endpoint. |
| OAuth 2.0 Authorization | Uses Client ID, Secret, and Refresh Token to maintain a secure session. |
| Workday Web Service: Put_Background_Check | Enables Certn to post results back into Workday. |
| ISU & ISSG | Dedicated Integration User and Security Group with least-privilege access. |
In this Guide
This onboarding guide provides a complete, step-by-step blueprint for implementing, validating, and maintaining the Workday ↔ CertnCentric integration.It is intended to ensure that client integration teams can deploy confidently, following a secure, standardized, and repeatable process. The intended audience for this document is the organization's Workday Integration Admins or Integration SME. We recommend first setting up test connectivity within the CertnCentric sandbox environment to validate the integration prior to setting it up in production.
Workday → Certn | Outbound Setup Configuration
Certn requires an Integration System and ISU to be created in the Workday tenant to allow Certn’s Workday Connector to read/write data from/to Workday. This user must be granted the appropriate access to the Workday fields which Certn will be reading from and writing to. This is achieved by adding the user to the correct security group, and by granting the security group access to required domains.
Create Integration Security Group and User
Create an Integration System User (ISU)
- Navigate to: Create Integration System User task.
- Give the ISU a unique name (i.e., ISU_Background_Check_Certn).
- Set up a password and check Do Not Allow UI Session → Ok.
Create an Integration System Security Group (ISSG)
- Navigate to: Create Security Group task.
- Under Tenanted Security Group Type, select Integration System Security Group (Unconstrained).
- Assign ISU to Security Group → Ok.
On the next screen, in the Integration System User field, select the ISU created in Step 1. Save the configuration.
Assign Domain Permissions / Security Policies
- Navigate to: View Security Group for User task.
- Select the ISU you created earlier → Ok.
Go to Security → Maintain Domain Permissions for Security Group.
- Grant View and Modify access to the following domains → Domain Security Permissions Matrix below.
Domain Security Policy Permissions
| Operation | Domain Security Policy | Domain Security Policies Inheriting Permission | Functional Areas |
|---|---|---|---|
| Get and Put | Manage Pre-Hire Process: Manage Pre-Hires | Pre-Hire Process | |
| Get and Put | Manage: Evergreen Requisitions | Consolidated Candidate Pool | Recruiting |
| Get and Put | Worker Data: Public Worker Reports | Staffing | |
| Get and Put | Integration Event | Integration | |
| Get and Put | Worker Data: Background Check Status | Personal Data | |
| Get and Put | Candidate Data: Background Check History | Recruiting | |
| Get and Put | Candidate Data: Job Application | Candidate Data: Bundle Resumes | Recruiting |
| Get and Put | Pre-Hire Data: Background Check Status | Pre-Hire Process | |
| Get and Put | Job Requisition Data | Pre-Hire Process | |
| Get and Put | Pre-Hire: Skills and Experience | Worker Profile and Skills | |
| Get and Put | Worker Data: Skills and Experience | Person Data: Achievements | Worker Profile and Skills |
Link ISSG to the Business Process
- Navigate to: bp: Background Check (Default Definition) → Business Process Policy → Edit.
- Add Security Group: Under Action: View All.
- Go to the Security Groups section.
- Add the ISSG created earlier.
- Navigate to Business Process Policy → Edit → View All section → Security Groups → Add your ISSG.
Apply Security Changes
- Go to the task Activate Pending Security Policy Changes.
- Click Ok to activate the new permissions and finalize the security setup.
Configure Business Process Definition
The integration must be embedded within the Background Check Business Process so it executes automatically when triggered.
- Navigate to: bp: Background Check (Default Definition) → Business Process → Edit Definition.
- Within the BP Definition editor, locate the Initiation step → Add Step (+ row) immediately after the initiation step.
- Type: integration Ensure that the Run As User is your ISU that you created as part of the set up.
- Select the integration you created earlier → Configure <step name> button.
- Select the integration → Ok → Define Integration Criteria.
- Core Connector: Background Check Outbound Initial Service.
- Background Check ID → Background Check Event.
- As of Entry Moment → Current Moment (DateTime).
Workday: Create Integration System
- From Workday, launch Create Integration System task.
- Template: Core Connector – Background Check Order Outbound. Enable all services.
- On the Integration System’s landing page, → Configure Integration Attributes tab.
- Configure the Integration Attributes with default values provided below:
- Phone Device Type → Mobile
- Email Type → Home
- Phone Type → Home
- Country Code Type → ISO3166-1-Alpha-3
- Address Type → Home
Define a Sequence Generator naming pattern
- Increment Sequence ID by 1 / Padding 0
- Set desired Sequence ID format (i.e., BGCHK-[seq])
Create a business process definition of the integration
- From the View Integration System → related actions, select:
- Integration System → Business Process → Create.
- Business Process Type: select < none of the above > → Ok.
- Add a step c, specify Type as Service and Specify Document Delivery → Ok.
Certn → Workday | Inbound Setup Configuration
The inbound integration allows CertnCentric to update background check statuses, completion results, and adjudication outcomes directly in Workday, using Workday’s public web service:
- Put_Background_Check
- Create a secure OAuth 2.0 client that Certn will use to authenticate and call Workday APIs.
Register API Client for Inbound Integrations (Workday)
- In Workday, search for Register API Client for Integrations.
- Click Create New Client.
- Populate the fields:
- Client Name: i.e., CertnCentric API Client.
- [ x ] Non-Expiring Refresh Tokens.
- Scope: Pre-Hire Process | Recruiting | Staffing → Ok.
This will generate the Client ID and Client Secret. Make note of this as you will need to use this in the Client Portal ATS Setup.
- Navigate to → API Client → Manage Refresh Tokens for Integrations.
- Select the ISU you created earlier in the Workday Account prompt → Ok.
- Select Generate New Refresh Token → Refresh Token is issued against this Workday ISU User account.
- Navigate to the CertnCentric Client Portal → Settings → ATS Integration → Initiate Workday Setup.
- Define OAuth Token endpoint.
- View API Clients → Copy “Token Endpoint” displayed.
- Define Recruiting WSDL URL.
- Public Web Services → Recruiting (Public) → Related Actions.
- View WSDL → Obtain URL nested under <soapbind:address> XML tag.
Input this URL into the WSDL endpoint field with a query parameter “?wsdl”.
- Input the Client ID + Client Secret you noted down.
Input the Refresh Token (Related Actions API Client → Manage Refresh Tokens).
Configure Document Delivery Service
- Workday → Navigate to View Integration System → Select Integration System previously created.
- Business Process Definitions → Steps → Configure Document Delivery.
Within the Document Delivery setup, select Document(s) - From this integration process.
Configure:
- Transport Type: HTTP/SSL
- HTTP Address: << obtained from CertnCentric Client portal during WD integration setup. Copy the value from REST API Endpoint >>
- Web Service Invocation Type: OAuth 2.0
- Navigate to CertnCentric → ATS Integrations → Workday to obtain the following:
- Access Token
- Refresh Token
- Refresh Token URL
- Client ID
- Client Secret
- Ensure “payload compressed” is not selected
Note: Workday will automatically refresh tokens when they expire, using the stored Client ID, Secret, and Refresh Token.
Configure Background Check Packages
- Enter Maintain Background Check Packages in the search box.
- Add each Package Name and Reference ID exactly as they appear in Certn Client Portal.
- Under Tests, configure: Test Name + Test Reference ID (must match Certn format)
- Then go to Maintain Background Check Statuses.
- Add all statuses Certn uses (i.e., Pending, Completed, Failed, Clear).
Configure Background Check Status Setup
Certn sends the actual Certn Status enum values directly to the Workday Put_Background_Check API. These enum values are used as the Workday Background_Check_Status_ID for the Overall Status, Package Status, and individual Test Statuses.
- Enter Maintain Background Check Statuses in the search box.
- Update the statuses as per the list provided below.
Package-Level Statuses (Overall Status, Package Status)
| Certn Status Enum (Reference ID Value) | Status Label (Background Check Status Label) | Maps To Workday Status Type(s) (Restricted To) |
|---|---|---|
| CASE_ORDERED | Case Ordered | Overall Status, Package Status |
| APPLICANT_INVITED | Applicant Invited | Overall Status, Package Status |
| APPLICANT_OPENED | Applicant Opened | Overall Status, Package Status |
| APPLICANT_STARTED | Applicant Started | Overall Status, Package Status |
| APPLICANT_SUBMITTED | Applicant Submitted | Overall Status, Package Status |
| INVITE_UNDELIVERABLE | Invite Undeliverable | Overall Status, Package Status |
| APPLICANT_DECLINED | Applicant Declined | Overall Status, Package Status |
| APPLICANT_EXPIRED | Applicant Expired | Overall Status, Package Status |
| IN_PROGRESS | In Progress | Overall Status, Package Status, Test Status |
| IN_DISPUTE | In Dispute | Overall Status, Package Status, Test Status |
| APPLICANT_ACTION_REQUIRED | Applicant Action Required | Overall Status, Package Status, Test Status |
| CLIENT_ACTION_REQUIRED | Client Action Required | Overall Status, Package Status, Test Status |
| CANCELLED | Cancelled | Overall Status, Package Status, Test Status |
| AWAITING_APPLICANT_SUBMISSION | Awaiting Applicant Submission | Test Status |
| PENDING_FULFILLMENT | Pending Fulfillment | Test Status |
| SUBMITTED_TO_SOURCE | Submitted to Source | Test Status |
| MANUAL_REVIEW_SOURCE | Manual Review with Source | Test Status |
| PENDING_QUALITY_REVIEW | Pending Quality Review | Test Status |
| IN_QUALITY_REVIEW | In Quality Review | Test Status |
| SUPERSEDED | Superseded | Test Status |
| COMPLETE | Completed | Overall Status, Package Status, Test Status |
| COMPLETE_CLEAR | Completed - Clear | Overall Status, Package Status, Test Status |
| COMPLETE_REVIEW | Completed - Review | Overall Status, Package Status, Test Status |
| COMPLETE_REJECT | Completed - Reject | Overall Status, Package Status, Test Status |
| COMPLETE_NOT_APPLICABLE | Completed - Not Applicable | Overall Status, Package Status, Test Status |
| COMPLETE_RESTRICTED | Completed - Restricted | Overall Status, Package Status, Test Status |
Testing out the integration
Validate the end-to-end functionality of the Workday → CertnCentric → Workday integration by simulating a candidate’s background check initiation and ensuring:
- The outbound order from Workday is correctly triggered.
- The payload is received and processed by CertnCentric.
- The background check status updates correctly return to Workday.
Pre-Test Setup Checklist
- Ensure ‘The Core Connector: Background Check Order Outbound’ is active.
- CertnCentric endpoint and OAuth configuration are validated (via “Test Integration” in Workday).
- The Business Process “Background Check (Default Definition)” includes your outbound integration.
- Integration System User (ISU) has domain access for Background Check Data, Candidate Data, and Integration Event Data.
- Candidate test data exists and has applied to a test job requisition.
Ensure the Candidate has Applied
- Log in to Workday as a Recruiter or Talent Partner.
- Navigate to: Workday → Recruiting → Candidates → [Select Candidate Name].
Confirm that the candidate has an Active Job Applications under the correct requisition.
Initiate Background Check
- Select Active Job Applications.
- Actions → Move Candidate.
- Move Forward → Assessment → Background Check.
This action invokes the Background Check Business Process, where the integration runs.
Proxy as Job Requisition Recruiter
- In Workday, Start Proxy as a Recruiter of the Job Requisition.
- Navigate to My Tasks → Select Background Check Package (Candidate Name).
Choose the CertnCentric package to test (configured under Maintain Background Check Packages) → click Submit to trigger the integration.
Navigate back to the Candidate > Screening > Background Check History Tab.
Overall Status + Package Status Updated with Result URL available to review the final report.
Comments
0 comments
Article is closed for comments.