.png)
Workday Human Capital Management Integration Guide
Integrate Workday HCM workforce data and business processes with enterprise applications through REST APIs, SOAP web services, reports, files, and governed workflows.
Workday Human Capital Management integration options at a glance
Workday HCM supports tenant-specific REST APIs for selected resources, broad SOAP web services, Reports-as-a-Service (RaaS), Enterprise Interface Builder (EIB), Workday Studio, and file-based integration patterns. REST is suitable for supported resource operations, while SOAP remains important for established staffing, worker, organization, payroll, and recruiting services. RaaS provides governed report extracts in formats such as XML, JSON, and CSV. Event-driven activity is selective and usually tied to business processes or outbound integrations rather than a universal webhook model. Martini can consume these interfaces, schedule and orchestrate workflows, map effective-dated workforce data, and route validated results to enterprise applications.
| Integration point | Supported by Workday Human Capital Management? | Common use cases | How Martini supports it |
|---|---|---|---|
| REST APIs | Yes | Retrieve and update supported Workday HCM resources, read reference data, and implement application-oriented workforce flows. Resource availability, operations, versions, and fields vary by tenant. | Martini can consume tenant-specific Workday REST endpoints, manage OAuth-based configuration, paginate responses, map JSON, and orchestrate writes to target systems. |
| SOAP APIs | Yes | Use WSDL-based Workday web services for staffing, worker, organization, payroll, recruiting, and other operations not available or already implemented through REST. | Martini can consume Workday SOAP services, handle XML and namespaces, apply configured authentication, transform responses, and separate business-process errors from transport failures. |
| Reports-as-a-Service | Yes | Retrieve governed report output in XML, JSON, CSV, or other configured formats for read-oriented extracts, filtered reports, and change-oriented synchronization. | Martini can invoke report endpoints, parse the selected format, validate report columns and prompts, maintain synchronization watermarks, and route the resulting data. |
| Bulk, async, and batch integrations | Yes | Use EIB, Workday Studio, reports, web services, and scheduled extracts for large workforce populations, inbound loads, and multi-endpoint processing. This is not one universal bulk REST API. | Martini can schedule batch workflows, process pages or files, control concurrency, transform records, and retain checkpoints and replay information. |
| Webhooks and outbound callbacks | Limited | Workday supports selected business-process-driven events and outbound integration activity, but not a universal webhook subscription for every HCM object or event. | Martini can receive supported callbacks or event-oriented requests through APIs and workflows; where no suitable event exists, it can poll REST resources or consume change-oriented reports. |
| File and attachment integrations | Limited | EIB, reports, SFTP-based patterns, and document-related services support selected file and attachment scenarios. Operations vary by object, service, and tenant configuration. | Martini can process supported files, transform structured content, validate attachments or documents where the source interface permits it, and route files through controlled workflows. |
| Authentication | Yes | Supported patterns include OAuth 2.0 for selected REST integrations, Basic Authentication or integration-system-user patterns for some SOAP services, and WS-Security depending on tenant configuration. | Martini can store tenant URLs, OAuth credentials, integration-system-user credentials, tokens, and certificates in protected environment configuration and secrets. |
| Database and analytics access | Limited | Workday does not provide ordinary customer database access. Reports and analytics outputs can be consumed through supported reporting and integration mechanisms. | Martini can consume approved report outputs and write integration state to supported target stores, but should not connect directly to a Workday database. |
How Workday Human Capital Management exposes data and business events
Workday REST APIs
Workday provides tenant-specific REST APIs for selected HCM resources, including supported workforce, organization, position, and reference-data operations. Availability and fields depend on the tenant, API version, enabled features, and security configuration.
Martini implementation pattern
Martini implementation pattern: a workflow authenticates to the configured Workday REST endpoint, retrieves or submits the required resource, follows pagination, maps the JSON payload, applies effective-date and business rules, and writes the result to a target system or exposes it through a Martini API.
Implementation sequence
Workday SOAP APIs
Workday exposes broad domain-specific SOAP web services through tenant- and version-specific WSDLs. SOAP remains important for staffing, worker, organization, payroll, recruiting, and operations that are not available through REST.
Martini implementation pattern
Martini implementation pattern: Martini consumes the selected WSDL operation, sends XML with the configured Basic Authentication, integration-system-user, or WS-Security pattern, handles namespaces and repeated elements, and routes Workday business-process responses through orchestration and error handling.
Implementation sequence
Reports-as-a-Service
Reports-as-a-Service exposes governed Workday report results through report URLs or web services. Reports can return XML, JSON, CSV, or other configured formats and can be designed for filtered or change-oriented extraction.
Martini implementation pattern
Martini implementation pattern: a scheduled workflow invokes the report with approved prompts, parses the configured output, validates report columns and calculated fields, applies a watermark or effective-date strategy, and sends the normalized records to downstream systems.
Implementation sequence
Workday EIB and file integrations
Enterprise Interface Builder supports configurable inbound and outbound integrations involving files, reports, web services, and transformation steps. File and document capabilities are object- and configuration-specific rather than one universal attachment API.
Martini implementation pattern
Martini implementation pattern: Martini receives or retrieves an EIB-generated file through the agreed exchange, validates the file structure and business content, transforms it into the target format, and records delivery or processing acknowledgements.
Implementation sequence
Workday events and outbound integrations
Workday can produce selected integration events or outbound activity associated with business processes, but it does not provide a universal webhook model for every HCM object. Availability depends on tenant configuration and implementation technology.
Martini implementation pattern
Martini implementation pattern: where the required event or callback is available, Martini receives the notification and retrieves authoritative Workday data before processing it. Otherwise, Martini uses scheduled REST or RaaS polling with a durable watermark to provide predictable synchronization.
Implementation sequence
Common Workday Human Capital Management integration patterns
Pattern 1: Synchronize workers to identity platforms
When to use this pattern
Use this pattern when Workday is the workforce system of record for provisioning, updating, or deactivating identities in Microsoft Entra ID or Okta. It supports event-oriented processing where available and scheduled incremental synchronization where it is not.
Integration direction
Example Mapping
| Workday Human Capital Management Field | Canonical Field | Target Field |
|---|---|---|
| Worker ID | worker.externalId | employeeId |
| Worker Status | employment.status | account.lifecycleStatus |
| Manager | manager.externalId | managerId |
| Supervisory Organization | organization.id | departmentId |
Martini implementation pattern
Martini receives a supported outbound event or retrieves changed Workers through REST, SOAP, or RaaS. It resolves effective-dated employment values, validates identity prerequisites, applies joiner-mover-leaver rules, writes idempotent updates, and routes permission, validation, and transient failures separately for reconciliation or retry.
Martini capabilities used
- workflows
- API consumption
- scheduling
- data mapping
- business rules
- error handling
Pattern 2: Synchronize workforce data to ServiceNow
When to use this pattern
Use this pattern when ServiceNow needs dependable employee, manager, department, or location data for onboarding, service requests, access workflows, and organizational reporting.
Integration direction
Example Mapping
| Workday Human Capital Management Field | Canonical Field | Target Field |
|---|---|---|
| Worker ID | worker.externalId | user.employee_number |
| Worker Name | person.displayName | user.name |
| Supervisory Organization | organization.name | user.department |
| Location | workLocation.code | user.location |
Martini implementation pattern
A scheduled Martini workflow retrieves paginated Workers and Organizations using the selected Workday interface, normalizes current and future-dated values according to policy, validates references, and calls ServiceNow APIs. Stable identifiers and reconciliation keys prevent duplicate users, while rejected records remain available for controlled replay.
Martini capabilities used
- workflows
- API consumption
- pagination orchestration
- data mapping
- validation
- retry and reconciliation
Pattern 3: Deliver worker and organization data to NetSuite
When to use this pattern
Use this pattern when finance, expense, procurement, or project processes in NetSuite require aligned employee and organizational reference data from Workday HCM.
Integration direction
Example Mapping
| Workday Human Capital Management Field | Canonical Field | Target Field |
|---|---|---|
| Worker ID | worker.externalId | employee.externalId |
| Legal Name | person.legalName | employee.entityId |
| Supervisory Organization | organization.id | employee.department |
| Worker Status | employment.status | employee.isInactive |
Martini implementation pattern
Martini consumes Workday REST, SOAP, RaaS, EIB, or file output, converts effective-dated workforce values into the NetSuite model, applies country and employment-status rules, and sends idempotent updates through NetSuite APIs. The workflow records source and target identifiers and retries only safe transport failures.
Martini capabilities used
- API consumption
- file processing
- data mapping
- business rules
- idempotency
- error handling
Pattern 4: Process business-process-driven workforce changes
When to use this pattern
Use this pattern for hires, terminations, job changes, organization changes, or compensation changes that require Workday business-process semantics rather than a simple field update.
Integration direction
Example Mapping
| Workday Human Capital Management Field | Canonical Field | Target Field |
|---|---|---|
| Business Process Type | change.type | event.type |
| Worker Reference | worker.externalId | subject.employeeId |
| Effective Date | change.effectiveDate | target.effectiveDate |
| Process Status | change.status | event.processingStatus |
Martini implementation pattern
Martini receives a supported outbound notification or polls a change-oriented report, then retrieves authoritative Workday details before routing the change. Business rules determine whether to update identity, service management, payroll, or another target. Correlation identifiers, approval status, and business-process errors are retained so incomplete transactions are not mistaken for successful synchronization.
Martini capabilities used
- event-driven workflows
- scheduled workflows
- API consumption
- orchestration
- business rules
- correlation and error handling
Applications commonly integrated with Workday Human Capital Management
Workday HCM commonly acts as a workforce system of record, so its data is often exchanged with identity, service management, finance, recruiting, payroll, and customer-platform applications. The exact direction, objects, and ownership depend on the customer's operating model and tenant configuration. Martini can implement these relationships through Workday REST APIs, SOAP services, reports, EIB or file exchanges, and the target application's supported APIs.
| Application | Scenario | Direction | Martini Pattern |
|---|---|---|---|
| Microsoft Entra ID | Provision and deactivate workforce identities while synchronizing manager, department, location, and employment-status attributes. | Workday Human Capital Management → Martini → Microsoft Entra ID | Martini retrieves Workers through REST, SOAP, RaaS, or a configured outbound extract, applies lifecycle rules, and calls the identity platform interface with idempotent create, update, and deactivate operations. |
| Okta | Automate workforce identity lifecycle management and user deprovisioning based on Workday employment changes. | Workday Human Capital Management → Martini → Okta | A scheduled or event-oriented Martini workflow retrieves changed Workers, maps worker status and organizational attributes, validates required identity fields, and sends retryable updates to Okta. |
| ServiceNow | Populate employee, department, manager, and location information for onboarding, service requests, and access workflows. | Workday Human Capital Management → Martini → ServiceNow | Martini consumes Workday Workers and Organizations, normalizes effective-dated values, and writes ServiceNow user and organizational data through ServiceNow APIs with reconciliation and error handling. |
| Salesforce | Synchronize employee, manager, territory, and organizational reference data for sales operations and user lifecycle processes. | Workday Human Capital Management → Martini → Salesforce | A Martini workflow reads approved Workday workforce data, applies business rules for eligible users and territories, maps it to Salesforce user or custom-object fields, and records rejected changes for replay. |
| SAP SuccessFactors | Exchange workforce, organizational, talent, or compensation-related information where both platforms operate in the enterprise. | Workday Human Capital Management → Martini → SAP SuccessFactors | Martini coordinates the selected system of record, retrieves or receives Workday data, transforms effective dates and identifiers, and routes acknowledgements or exceptions without assuming ownership of every object. |
| ADP Workforce Now | Exchange worker, payroll, tax, or employment information where Workday and ADP coexist across defined countries or payroll scopes. | Workday Human Capital Management → Martini → ADP Workforce Now | Martini validates country-specific fields, transforms Workday REST, SOAP, RaaS, EIB, or file output into the receiving model, and preserves acknowledgements and failed records for controlled reconciliation. |
| NetSuite | Synchronize employee and organizational data for finance, expense, procurement, or project processes. | Workday Human Capital Management → Martini → NetSuite | Martini retrieves Workers and Organizations, maps stable Workday identifiers and organizational dimensions, invokes NetSuite APIs, and uses duplicate detection and retry controls for outbound writes. |
| Greenhouse | Coordinate recruiting and worker onboarding data between an applicant-tracking platform and Workday HCM. | Greenhouse → Martini → Workday Human Capital Management | Martini receives or retrieves recruiting and hire information, validates the required Workday business-process inputs, transforms the payload for a Workday REST or SOAP operation, and tracks business-process errors separately from transport failures. |
How to build a Workday Human Capital Management integration in Martini
Objective
Establish the tenant-specific Workday endpoints and authentication model before designing the data flow.
Instructions in Martini
- Configure tenant URLs, API versions, and environment-specific values.
- Choose OAuth 2.0 for supported REST operations or the approved SOAP and integration-system-user pattern.
- Store client secrets, tokens, passwords, and certificates in protected Martini secrets or environment configuration.
- Confirm Workday domain permissions and business-process security for the required objects.
Objective
Select an event-oriented, scheduled, API-led, or file-based trigger that matches the Workday tenant and synchronization requirements.
Instructions in Martini
- Use a supported outbound event or callback when the required business-process event is available.
- Use a scheduler for REST, SOAP, or RaaS polling when event coverage is incomplete.
- Use a file-oriented workflow when EIB or an approved report export is the source.
- Define the synchronization watermark, effective-date policy, and replay boundary.
Objective
Obtain authoritative Workday data while respecting pagination, report configuration, and effective-dated semantics.
Instructions in Martini
- Retrieve Workers, Persons, Positions, Organizations, or other approved objects through the selected interface.
- Follow REST or report pagination until the required result set is complete.
- Retrieve full resource details after receiving a lightweight event notification when necessary.
- Validate report columns, API versions, namespaces, and required identifiers.
Objective
Coordinate the Workday call, enrichment, target calls, acknowledgements, and failure paths in a maintainable Martini workflow.
Instructions in Martini
- Separate transport, transformation, business validation, and target-write stages.
- Use reusable services or workflow components for common authentication and normalization logic.
- Route records by lifecycle state, country, organization, or target ownership where required.
- Capture correlation identifiers and source-to-target references throughout the flow.
Objective
Convert Workday REST, SOAP, report, or file structures into a canonical model and the target application's schema.
Instructions in Martini
- Map stable Worker, Person, Position, and Organization identifiers.
- Handle XML namespaces, repeated elements, optional values, and empty fields.
- Normalize effective dates, status values, organizational hierarchies, and location codes.
- Minimize sensitive fields and apply target-specific formatting rules.
Objective
Validate business prerequisites and perform safe, idempotent writes to downstream systems or Workday interfaces.
Instructions in Martini
- Validate required identifiers, lifecycle states, permissions, and target references before writing.
- Distinguish current, future-dated, and historical values according to the integration contract.
- Use stable identifiers or reconciliation keys to avoid duplicate users, positions, or transactions.
- Record acknowledgements and business-process results separately from transport responses.
Common Workday Human Capital Management data objects used in integrations
| Object | Typical Use | Common target systems | Martini handling |
|---|---|---|---|
| Workers | Synchronize worker identity, employment, job, organization, contact, staffing, and lifecycle information. | Microsoft Entra ID, Okta, ServiceNow, Salesforce, NetSuite, payroll platforms | Martini retrieves Workers through REST, SOAP, RaaS, or outbound extracts, handles pagination and effective dates, validates required fields, and maps stable identifiers to target models. |
| Persons | Exchange person-level identity and demographic information associated with workers and other people. | Identity platforms, ServiceNow, payroll applications, workforce systems | Martini applies data-minimization rules, maps person identifiers and sensitive attributes, and preserves tenant-specific permissions and field availability. |
| Positions | Synchronize position restrictions, staffing status, and position-related organizational data. | ServiceNow, Salesforce, recruiting platforms, workforce planning applications | Martini resolves effective-dated position values, applies organizational business rules, and reconciles updates using stable Workday identifiers. |
| Organizations | Share supervisory organization and other organization structures used to manage the workforce. | ServiceNow, Salesforce, NetSuite, identity platforms, reporting stores | Martini retrieves hierarchical data, normalizes parent-child relationships, validates references, and processes changes incrementally where supported. |
| Job Profiles | Exchange job definitions, qualifications, responsibilities, and job-related attributes. | Recruiting platforms, talent applications, workforce planning systems | Martini maps profile codes and attributes, validates required target values, and handles schema differences between Workday reports, REST resources, and receiving applications. |
| Business Processes | Coordinate hiring, job changes, terminations, compensation changes, approvals, and other configurable Workday transactions. | Workday integrations, identity platforms, payroll applications, operational stores | Martini invokes supported operations or consumes completion results, applies business-process rules, tracks correlation identifiers, and distinguishes validation or approval failures from transient errors. |
Authentication and security considerations
Tenant-aware authentication
Workday authentication depends on the selected interface and tenant configuration. Supported patterns include OAuth 2.0 for selected REST APIs, integration-system-user credentials for common server-to-server flows, Basic Authentication for some SOAP services, and WS-Security where required.
Permissions remain essential
Successful authentication does not grant access to HCM data. Workday security groups, domain permissions, OAuth scopes, and business-process security must be configured for the required Workers, Organizations, Compensation, or transaction operations.
Protect integration secrets
- Store tenant URLs, client secrets, tokens, passwords, and certificates in protected Martini environment configuration or secrets.
- Minimize personal, compensation, government-identifier, and other sensitive data in payloads and logs.
- Use least-privilege integration users and restrict access to workflow definitions, runtime data, and operational logs.
Operational considerations for Workday Human Capital Management integrations
Design for Workday behavior
- Confirm tenant-specific API versions, endpoint paths, fields, operations, and security permissions.
- Handle pagination and avoid repeated full-population extracts when incremental criteria or change-oriented reports are available.
- Define whether integrations use current, future-dated, historical, or effective-on-date values.
- Respect tenant capacity with controlled concurrency, batching, backoff, and retry limits.
- Expect XML namespaces, optional elements, repeated elements, and schema differences across REST, SOAP, and reports.
Reconcile safely
Use stable Worker, Person, Position, and Organization identifiers, durable watermarks, correlation identifiers, and idempotent target operations. Separate retryable transport failures from authorization, validation, and business-process errors.
Test for change
Test representative hires, terminations, job changes, effective-dated updates, empty values, report modifications, API-version changes, and permission failures. Monitor workflow logs and retain enough information to replay rejected data without duplicating successful writes.
Why use Martini instead of scripts or point-to-point integrations?
Orchestrate more than an API call
Workday integrations often combine REST, SOAP, reports, files, business-process semantics, effective-dated data, and downstream application APIs. Martini provides a workflow layer for coordinating these steps without embedding the whole integration in a brittle script.
Make mappings reusable
Martini separates API consumption, transformation, validation, business rules, target writes, and error paths. This makes it easier to reuse workforce normalization logic across identity, service management, finance, payroll, and other applications.
Operate with control
- Use scheduled, event-oriented, batch, or API-led workflows as the tenant requires.
- Centralize secrets and environment-specific Workday configuration.
- Apply pagination, checkpoints, idempotency, retries, reconciliation, and monitoring consistently.
- Expose a controlled Martini API when other applications need a stable interface rather than direct Workday access.
Frequently asked questions
Workday HCM can integrate through tenant-specific REST APIs, SOAP web services, Reports-as-a-Service, Enterprise Interface Builder, Workday Studio, selected business-process-driven outbound integrations, and file exchanges. The appropriate mechanism depends on the Workday resource, transaction semantics, tenant configuration, and whether the flow is real time, scheduled, or batch.
Yes. Martini can integrate with Workday HCM by consuming Workday REST APIs and SOAP services, processing RaaS or EIB-generated files and reports, receiving supported outbound events, and orchestrating mappings, validation, synchronization, and error handling in workflows. A native Martini Workday connector is not documented in the supplied sources.
No. A dedicated Workday connector is not required. Martini can use Workday's confirmed native integration mechanisms, including REST APIs, SOAP web services, reports, EIB or file exchanges, selected outbound events, and tenant-approved authentication methods.
Lonti does not charge an additional per-connector or per-vendor fee to integrate Workday HCM with Martini. Integrations are subject to the provisioned capacity of the Martini environment. Separate costs may apply from Workday, infrastructure providers, payroll or identity platforms, or other third parties based on subscription, usage, and deployment model.
Use REST when the required HCM resource and operation are supported and JSON-based access is appropriate. Use SOAP for established WSDL-based services or operations unavailable through REST. Use RaaS for governed read-oriented extracts, and EIB, Workday Studio, or file exchanges for configured batch and multi-endpoint scenarios.
Workday supports selected business-process-driven events and outbound integration activity, but it does not provide a universal webhook subscription model for every HCM object. Martini can receive a supported notification when configured, or use scheduled REST and RaaS polling with a durable watermark when event coverage is insufficient.
Martini can retrieve paginated Workers through REST, SOAP, RaaS, or configured extracts, then apply incremental criteria, watermarks, effective-date rules, and reconciliation. It maps worker, organization, manager, location, and status values into target models while using stable identifiers to manage updates and terminations.
Martini can separate authentication, permission, validation, business-process, throttling, and transient service failures. Retry policies should be limited to safe transient failures, while stable Workday identifiers and reconciliation keys support idempotency. Correlation details and rejected payloads can be retained for controlled replay.
Related Martini documentation
API access
Workflows
Data handling
Integrate Workday HCM with confidence
Use Martini to connect Workday HCM APIs, web services, reports, files, and selected outbound events with the enterprise systems that depend on workforce data.