Integration in Workday refers to the process of connecting Workday with external
systems, platforms, or data sources to exchange information automatically—either by
importing data into Workday or exporting it out.
Integration in Workday is required to connect it seamlessly with other systems to
automate processes, eliminate duplicate work, improve accuracy, and enable real-time
operations across the organization.
1. Automated Data Flow
● Avoids the need to manually re-enter the same data in multiple systems.
● Reduces human error and speeds up processes.
Example: Sync new hire data from Workday to Active Directory and payroll system
automatically.
2. Real-Time or Scheduled Updates
● Ensures that data is up-to-date across platforms.
● Can be configured to run real-time, on a schedule, or on-demand.
Example: Daily export of time entry data from Workday to a payroll system.
3. Connect with Third-Party Vendors
● Integrates with providers like ADP, SAP, ServiceNow, SuccessFactors, Microsoft
Azure, etc.
● Enables benefits enrollment, tax filing, background checks, and more.
Example: Integration with a benefits provider like MetLife for real-time benefits eligibility
updates.
Integration Architecture Review
All Workday customer data is stored as objects within a persistent, in-memory store.
Originally, a suite of business services called the Object Management System (OMS)
maintained the relationships and integrity of these objects. Over time, the OMS has evolved
to become a set of microservices that scale based on transaction and reporting demand.
The only way to access Workday object data is via web service requests (OMS). This is an
important aspect of how Workday addresses issues such as security and performance.
All communication with the Workday services is via HTTPS requests. Users generally
access Workday through web browsers. The User Interface Server (UI Server) handles
these requests, presenting HTML forms for user interaction, while communicating with the
Workday platform using XML messages. Developers also connect via the UI Server to make
use of the browser-based tools, for example, when configuring Integration Systems or
building integrations using Enterprise Interface Builder (EIB). Workday has application
programming interfaces (APIs) that support both inbound and outbound requests for mobile
applications and data-driven integrations that do not use the Workday UI.
Workday supports several types of integrations to connect with internal systems and third-
party applications. These are broadly categorized based on complexity, customization, and
use cases.
🔹 EIB Overview
The Enterprise Interface Builder (EIB) allows users to perform simple and secure
integrations with Workday. Unlike other Workday integrations, the purpose of the EIB, which
uses no third-party software or hardware, is to allow customers to build their own
integrations according to their unique business scenarios.
What is Enterprise Interface Builder (EIB)?
Enterprise Interface Builder (EIB) is a Workday-delivered, no-code integration tool that
allows customers to import or export data to and from Workday using flat files (CSV, Excel,
XML). It is designed for simplicity, flexibility, and rapid deployment, making it ideal for
business users and analysts—not just developers.
🔁 Types of EIBs
Inbound EIB
An Inbound EIB (Enterprise Interface Builder) is used to import data into Workday
from an external file, such as a spreadsheet or flat file (CSV, Excel, XML). It's
designed for mass updates or data loads without needing to manually enter data
record by record.
Purpose of Inbound EIB
The primary purpose is to automate bulk data entry into Workday, making data
management faster, more consistent, and less error-prone.
Outbound EIB
Purpose: Extract data from Workday
Destination: Email, SFTP server, local download, or Workday drive.
Output can include:
Custom reports
Filtered data sets
Transformed documents (XML, JSON, etc.)
🔹 3. Core Connectors
Best for: Standard integrations with minimal setup.
Purpose: Pre-built templates for common services (e.g., Benefits, Payroll).
Variants:
Core Connector: Worker
Core Connector: Payroll Interface
Example: Send worker information to ADP or a benefits provider.
🔹 4. Cloud Connect
Best for: Third-party systems with pre-packaged solutions.
Purpose: Full integration solutions built by Workday.
Includes: Predefined mappings, transformations, and scheduling.
Example: Cloud Connect for Benefits (like MetLife or Aetna).
🔹🔹 2. Workday Studio
Workday Studio is a tool that fetches data from Workday, including suppliers,
workers, and imports. It is used to load data into Workday and fetch data from
external APIs.
When external web services are used, users can call servers outside Workday.
Workday Studio is the primary component for calling Workday web services. It is
extensively used for inbound integration, which involves loading data into
Workday
Best for: Complex, custom integrations.
Purpose: Design, build, and deploy custom integrations.
Tools: Eclipse-based IDE with drag-and-drop components and coding.
Example: Send employee data to a third-party payroll provider with custom logic
and transformation.
5. Workday Web Services (WWS / APIs)
Best for: Real-time, programmatic integrations.
Purpose: Allow external applications to communicate with Workday via SOAP or
REST APIs.
Use case: Querying or updating Workday data on-demand.
Example: Sync employee directory in Workday with an internal portal.
🔹 6. Workday Extend (formerly Workday Cloud Platform)
Best for: Building custom apps that run inside Workday.
Purpose: Extend Workday functionality with custom user interfaces, logic, and
storage.
Example: Create a custom onboarding app tailored to your business process.