Setup Considerations: Workday Integration
You can use this topic to help make decisions when planning and configuring your integration between Workday and Workday Peakon Employee Voice (Peakon). It explains the system interactions, capabilities, security requirements, and design choices to consider before implementation.
Refer to detailed task instructions for full configuration details.
What It Is
The Workday integration provides an automated mechanism to synchronize worker data, organizational structures, and demographic attributes from core Workday into your Peakon directory. The redesigned configuration experience centralizes connection setups, attribute mappings, and eligibility logic within a unified interface.
Business Benefits
- Minimizes manual administrative overhead and removes human errors by replacing flat-file updates with automated incremental syncs.
- Automatically populates reporting segments and supervisory relationships, ensuring accurate context for employee engagement feedback.
- Safeguards feedback confidentiality and secures tenant access by dynamically updating worker statuses and removing leavers based on active Workday states.
Use Cases
- Sync employees automatically by specific criteria, such as supervisory organization, entity, or continuous service dates.
- Provide unified context for conversational AI features and AI agents that support manager self-service workflows.
- Establish automated segmentation for localized pulse surveys or targeted demographics without maintaining separate employee spreadsheets.
Questions to Consider
Question | Consideration |
|---|---|
Which authentication method fits your IT security policy? | You can authenticate the integration using an Integration System User (ISU) name and password or via OAuth. Workday recommends the ISU approach for standard configurations because it is easier to maintain and resilient against external session interruptions. Only use OAuth if you plan to deploy People Experience cards. |
How do you want to define worker sync scopes? | You can sync your entire organization or isolate groups using specific organization IDs. Filtering directly via Organization IDs optimizes synchronization processing speeds compared to complex custom calculated fields. |
Should contingent workers receive surveys? | You can opt to include or ignore contingent worker contracts within the integration settings. Consider your organizational communication strategy and licensing thresholds before enabling this scope. |
How will you handle localized survey delivery? | Enabling the time zone and locale sync settings ensures that workers receive survey alerts at the intended local time and in their preferred language. |
Recommendations
- Perform a full sync manually before launching a new survey round to ensure all indirect structural updates, such as calculated field redefinitions or manager role transfers, are captured.
- Map fields using unique external identification numbers alongside email addresses to prevent duplicate account creation if a worker changes their primary email address.
- Avoid setting employees on long-term leave to inactive manually; instead, sync a dedicated status attribute and exclude that segment from active survey targeting.
Requirements
- Register your company's authorized email domains with our Customer Care before enabling the integration sync.
- Create identical attribute names or precise case-sensitive aliases in Peakon to match your incoming Workday Core Connector data schema.
- Workday AI agents require the use of Workday Flex Credits. For more information, see this Community article.
Limitations
- The integration cannot perform retroactive historical data backdating across your Peakon dashboards; any structural backdating requires manual spreadsheet configuration.
- The incremental hourly sync cycle only tracks direct profile modifications recorded in the Workday transaction log.
- Peakon restricts bulk synchronization updates via external partner platforms to predefined API performance thresholds to maintain system health.
Tenant Setup
The redesigned integration interface lives under . You can modify synchronization behaviors, toggle phone number parameters, and manage attribute overrides directly from this single center.
Security
Domains | Considerations |
|---|---|
Integration Security (Integration functional area) | Required to create the necessary integration system users and secure API programmatic endpoints. |
Security Configuration (System functional area) | Required to activate functional security policies, maintain authentication parameters, and evaluate active security groupings. |
Worker Data: Public Worker Reports (Staffing functional area) | Secures the foundational Get_Workers SOAP web service and requires unconstrained permissions to execute sync calls. |
Person Data: Work Email Address Integration (Contact Information functional area) | Provides essential data access to capture and verify unique worker communication channels. |
Business Processes
The completion of a termination business process in Workday triggers the sync of
Termination Dates
and Termination Reasons
to Peakon. To sync future-dated separations successfully before their effective date, you must construct a dedicated evaluate expression calculated field in your Workday configuration.Reporting
You can audit synchronization events, field mapping rejections, and operational warning criteria using the built-in Peakon integration activity logs. The interface provides a mechanism to export the latest 5,000 diagnostic log lines in CSV format for administrative troubleshooting.
Integrations
Integration Type | Description |
|---|---|
Core Connector: Worker | The fundamental outbound web service architecture that detects changes to employee records and transmits fields to Peakon. |
Field Override Service | An optional connector configuration that enables you to map custom Workday calculated fields to explicit Peakon tracking attributes, using the employee: prefix for reporting relation structures. |
Connections and Touchpoints
You can extend the core integration with People Experience (PEX) cards to project active survey invitations and reminders into workers'
Timely Suggestions
feeds directly on their Workday homepage.