.png)
Workday Learning Integration Guide
Integrate Workday Learning with enterprise applications through tenant-configured REST and SOAP APIs, reports, approved event mechanisms, and scheduled workflows.
Workday Learning integration options at a glance
Workday Learning integrations can use Workday REST APIs for selected resources, Workday Public Web Services for SOAP operations, and approved reports, integration processes, or bulk and asynchronous mechanisms for larger data sets. Selected Workday services may provide event or callback-style delivery, but universal Workday Learning webhook coverage should be verified for each tenant and event. Workday also supports file-oriented integration patterns in selected areas. Martini can consume these endpoints, process JSON or XML, orchestrate pagination and batching, apply mappings and business rules, expose controlled APIs, and run scheduled incremental synchronization workflows. OAuth 2.0, API clients, Integration System Users, tenant security domains, and environment-managed secrets support secure execution.
| Integration point | Supported by Workday Learning? | Common use cases | How Martini supports it |
|---|---|---|---|
| REST APIs | Yes | Workday REST APIs provide access to selected Workday resources. Workday Learning coverage depends on API version, enabled services, tenant configuration, and permissions. | Martini can consume Workday REST endpoints, manage configured authentication, process JSON responses, handle pagination, and map results into downstream APIs, databases, or files. |
| SOAP APIs | Yes | Workday Public Web Services expose SOAP operations and WSDLs for many business objects and integration services. SOAP may be required where a Learning operation is not available through REST. | Martini can consume Workday SOAP services, construct XML requests, parse XML responses, and transform SOAP data into JSON, database, file, or API formats. |
| Webhooks / outbound callbacks | Limited | Selected Workday services may support outbound integrations, event-driven patterns, or callback-style delivery. Universal webhook coverage for Workday Learning is not confirmed. | Martini can receive supported webhook-style requests or callbacks through an API or workflow trigger; where delivery is unavailable, Martini can run scheduled incremental polling instead. |
| Bulk / async / batch processing | Limited | Workday supports reports, integration processes, bulk data exchange, and asynchronous processing for larger data sets, with the exact mechanism depending on the object and tenant. | Martini can orchestrate pages and batches, apply bounded concurrency, track checkpoints, process asynchronous results where exposed, and retry transient failures. |
| File / attachment APIs | Limited | Workday provides report, document, and file-oriented integration capabilities in selected areas. Direct Learning attachment operations must be verified for the target API version. | Martini can process approved Workday CSV, XML, JSON, and other file payloads and route them through workflows for validation, transformation, and delivery. |
| Authentication | Yes | Workday integrations may use OAuth 2.0 API clients and refresh tokens, or Integration System Users and credentials for applicable SOAP services. Security domains and permissions are also required. | Martini can store tenant endpoints and credentials in environment configuration and secrets, invoke authenticated APIs, and expose controlled APIs without passing Workday credentials to consumers. |
| Database access | No | Direct customer access to the Workday production application database is not a documented integration approach. Reports, APIs, integration services, and approved exports should be used instead. | Martini can consume Workday APIs, reports, or files and can write normalized data to an approved downstream database without connecting to Workday's production database. |
How Workday Learning exposes data and business events
Workday Learning REST APIs
Workday provides REST APIs for selected Workday resources, but the available Learning resources and operations depend on the tenant, API version, enabled services, and security permissions.
Martini implementation pattern
Martini implementation pattern: a workflow calls the tenant-specific REST endpoint with configured OAuth or other approved credentials, follows pagination or incremental filters, validates the JSON response, maps Workday Learning objects, and writes the result to the target system.
Implementation sequence
Workday Public Web Services
Workday Public Web Services expose SOAP operations and WSDLs for many business objects and integration services. SOAP is useful when the required Learning operation is not available through REST or an existing integration depends on WSDL-based services.
Martini implementation pattern
Martini implementation pattern: a workflow invokes the selected Workday SOAP operation using the tenant's configured authentication, parses XML responses, handles service faults, and transforms the result into the downstream JSON, database, file, or API model.
Implementation sequence
Workday outbound events and callbacks
Selected Workday services may support outbound integrations, business-process-driven events, or callback-style delivery. Workday Learning webhook coverage is not universal and must be verified for the exact event and tenant.
Martini implementation pattern
Martini implementation pattern: where an approved Workday event or callback exists, Martini exposes a controlled receiving API or workflow trigger, validates the notification, retrieves the current Workday resource when necessary, and processes the event idempotently. If callback delivery is unavailable, the same workflow can be initiated by a scheduler for incremental polling.
Implementation sequence
Workday reports and bulk processing
Workday supports reports, integration processes, bulk data exchange, and asynchronous processing for larger data sets. The exact report, integration, or asynchronous operation depends on the Learning object and tenant configuration.
Martini implementation pattern
Martini implementation pattern: a scheduled workflow retrieves an approved report or bulk result, parses the response or file, processes records in bounded batches, applies checkpointing, and separates successful, rejected, and retryable records.
Implementation sequence
Workday file-oriented integrations
Workday provides file-oriented integration capabilities through reports, integration services, and selected document or file operations. Direct Learning attachment support must be confirmed for the target API version.
Martini implementation pattern
Martini implementation pattern: Martini receives or retrieves an approved Workday file, validates its structure and encoding, transforms rows or document metadata, and routes the resulting records or files to downstream systems through an orchestrated workflow.
Implementation sequence
Common Workday Learning integration patterns
Pattern 1: Synchronize worker learning assignments
When to use this pattern
Use this pattern when HR, compliance, or workforce systems need current Learning Courses, Learning Items, Learners, or Learning Enrollments. A scheduled workflow is appropriate when event coverage for the required Learning object is unavailable or uncertain.
Integration direction
Example Mapping
| Workday Learning Field | Canonical Field | Target Field |
|---|---|---|
| Learning Enrollment ID | learningEnrollmentId | ServiceNow external enrollment ID |
| Learner ID | learnerId | ServiceNow employee reference |
| Learning Item status | learningStatus | ServiceNow training status |
| Completion date | completedAt | ServiceNow completion date |
Martini implementation pattern
A scheduler starts a Martini workflow that retrieves changed pages through Workday REST or SOAP, preserves stable Workday identifiers and effective dates, applies worker-status and eligibility rules, and performs idempotent ServiceNow upserts. Pagination checkpoints are committed only after downstream writes succeed; transient failures are retried and validation failures are routed for correction.
Martini capabilities used
- workflows
- scheduled triggers
- API consumption
- SOAP and XML processing
- data mapping
- business rules
- checkpointing
- error handling
Pattern 2: Publish the learning catalog
When to use this pattern
Use this pattern when an employee portal, intranet, search index, or external learning catalog needs active Workday Learning Courses, Learning Content, or Learning Items.
Integration direction
Example Mapping
| Workday Learning Field | Canonical Field | Target Field |
|---|---|---|
| Learning Item ID | catalogItemId | Microsoft Teams notification reference |
| Learning Item title | title | message title |
| Learning Item type | contentType | notification category |
| Effective date | effectiveFrom | message availability date |
Martini implementation pattern
Martini retrieves catalog data through a scheduled REST, SOAP, report, or approved file workflow, filters active offerings by country, organization, or worker population, normalizes classifications, and sends only eligible changes to the target application. The workflow records source identifiers and avoids duplicate publication across retries.
Martini capabilities used
- workflows
- scheduler triggers
- API consumption
- file processing
- data mapping
- conditional routing
- business rules
- retry handling
Pattern 3: Expose completion status through an API façade
When to use this pattern
Use this pattern when an external learning, compliance, talent, or service application needs completion information without receiving direct Workday credentials or tenant access.
Integration direction
Example Mapping
| Workday Learning Field | Canonical Field | Target Field |
|---|---|---|
| Learner ID | learnerId | Workday learner query parameter |
| Learning Item ID | learningItemId | Workday Learning Item filter |
| Completion status | completionStatus | API response status |
| Completion date | completedAt | API response completion date |
Martini implementation pattern
Martini exposes a controlled REST API that authenticates the consumer, validates learner and item parameters, invokes the relevant Workday REST or SOAP operation, and returns a normalized response. Caching or checkpointed retrieval can reduce repeated Workday calls, while authorization rules restrict the data returned to each consumer.
Martini capabilities used
- API exposure
- workflow orchestration
- REST and SOAP consumption
- authentication and authorization
- data mapping
- validation
- business rules
- error handling
Pattern 4: Process learning events or bulk files
When to use this pattern
Use this pattern when the Workday tenant provides an approved outbound event, report, bulk result, or file-based integration for Learning data, especially for higher-volume changes or compliance extracts.
Integration direction
Example Mapping
| Workday Learning Field | Canonical Field | Target Field |
|---|---|---|
| Learning Course ID | courseId | Jira custom course field |
| Learning Content status | contentStatus | Jira issue status |
| Learning Campaign | campaignId | Jira program reference |
| Validation error | processingError | Jira remediation description |
Martini implementation pattern
Martini receives the approved notification or retrieves the report and file on a schedule, validates the payload, processes records in bounded batches, and creates or updates Jira remediation work items for qualifying exceptions. Duplicate events are controlled with source identifiers, and failed batches remain available for replay without advancing the checkpoint.
Martini capabilities used
- workflow triggers
- scheduled workflows
- file processing
- batch orchestration
- data mapping
- business rules
- idempotency
- error handling
Applications commonly integrated with Workday Learning
Workday Learning data can be orchestrated with adjacent enterprise applications for compliance, workforce communications, service operations, partner enablement, and operational reconciliation. The exact object coverage and direction should be confirmed for each Workday and target-system tenant.
| Application | Scenario | Direction | Martini Pattern |
|---|---|---|---|
| ServiceNow | Synchronize mandatory training, compliance status, worker information, and exceptions with employee-service and compliance processes. | Workday Learning → Martini → ServiceNow | A scheduled Martini workflow retrieves changed Learning Enrollments, Learners, and completion-related data through Workday REST or SOAP services, maps stable Workday identifiers into ServiceNow records, applies status and effective-date rules, and performs idempotent updates with retry and reconciliation handling. |
| Salesforce | Share learning completion, certification, or partner-enablement information with account, customer, and partner teams. | Workday Learning → Martini → Salesforce | Martini retrieves approved Workday Learning data, filters eligible learners or offerings, transforms completion and certification fields into Salesforce objects, and invokes Salesforce APIs while recording checkpoints and isolating validation failures. |
| Microsoft Teams | Publish learning assignments, reminders, campaign notifications, or completion messages to workforce collaboration channels. | Workday Learning → Martini → Microsoft Teams | A Martini workflow polls Workday for new assignments or campaign changes, applies audience and timing rules, formats a message payload, and calls Microsoft Teams endpoints with controlled retries for transient delivery failures. |
| Slack | Deliver learning reminders, campaign notifications, or completion acknowledgements to workforce channels. | Workday Learning → Martini → Slack | Martini consumes Workday Learning changes through an incremental workflow, maps the relevant learner and course context into Slack messages, routes notifications by organization or channel, and prevents duplicate messages using Workday identifiers and checkpoints. |
| Jira | Create or update work items for learning-content remediation, compliance exceptions, or training-program actions. | Workday Learning → Martini → Jira | Martini extracts qualifying Learning Courses, Learning Content, or compliance exceptions, applies business rules for priority and ownership, creates or updates Jira issues through its API, and routes rejected payloads for operational correction. |
| NetSuite | Reconcile learning-related worker, contractor, or compliance information with finance and operational records. | Workday Learning → Martini → NetSuite | A scheduled Martini workflow retrieves relevant Workday Learning and Learner data, maps organization and worker identifiers to NetSuite fields, performs controlled upserts, and uses bounded concurrency, retry handling, and reconciliation reports for incomplete batches. |
How to build a Workday Learning integration in Martini
Objective
Establish tenant-specific Workday endpoints and credentials while keeping security configuration separate from workflow logic.
Instructions in Martini
- Confirm the required Workday Learning REST resource or SOAP operation, API version, tenant hostname, and permissions.
- Configure OAuth 2.0 API client details or the approved Integration System User credentials.
- Store endpoints, client secrets, refresh tokens, and page-size settings in Martini environment configuration and secrets.
- Verify Workday security domains, scopes, and business-process permissions with the production security principal.
Objective
Select an event-driven, API-led, or scheduled initiation based on the Workday capability confirmed for the target object.
Instructions in Martini
- Use a supported Workday event or callback only when the exact Learning event is confirmed.
- Use a scheduler for incremental polling, reports, bulk extraction, or file processing where callback delivery is unavailable.
- Define the last-updated, effective-date, or checkpoint strategy before retrieving data.
- Set a bounded schedule and concurrency level appropriate for tenant capacity.
Objective
Call the appropriate Workday interface and obtain complete, validated Learning data.
Instructions in Martini
- Invoke the Workday REST endpoint or SOAP operation through the Martini workflow.
- Retrieve approved reports, bulk results, or files when they are more suitable for high-volume processing.
- Handle pagination, continuation data, asynchronous results, and response parsing.
- Validate required identifiers, statuses, dates, and object relationships before downstream processing.
Objective
Coordinate retrieval, transformation, business rules, target writes, and checkpoint management as one maintainable integration flow.
Instructions in Martini
- Separate extraction, transformation, target delivery, and checkpoint stages where operational clarity requires it.
- Route transient service failures to bounded retries and route validation or permission failures for correction.
- Use stable Workday identifiers and a correlation value throughout the workflow.
- Preserve successful and rejected batch outcomes for reconciliation and replay.
Objective
Convert Workday Learning objects and XML or JSON payloads into a canonical model suitable for each target application.
Instructions in Martini
- Map Learning Courses, Learning Content, Learning Items, Learning Enrollments, Learners, and Learning Campaigns to target fields.
- Normalize enumerations, classifications, effective dates, worker statuses, and completion values.
- Apply country, organization, audience, and active-offering filters.
- Retain source identifiers and relevant timestamps for traceability.
Objective
Ensure that only eligible and meaningful learning changes are delivered to downstream systems.
Instructions in Martini
- Filter records by active status, effective date, worker population, organization, or country where required.
- Determine whether a change is a create, update, completion, cancellation, or remediation event.
- Validate required target fields before making an upsert.
- Use idempotency keys to prevent duplicate enrollments, notifications, or work items.
Common Workday Learning data objects used in integrations
| Object | Typical Use | Common target systems | Martini handling |
|---|---|---|---|
| Learning Course | Represents a structured learning offering that can be assigned to or selected by learners. | ServiceNow, Salesforce, Microsoft Teams, Slack, employee portals | Martini retrieves the course through the applicable REST, SOAP, report, or export mechanism, filters active or effective offerings, maps identifiers and classifications, and upserts the target representation. |
| Learning Content | Represents digital or external material associated with a learning offering, including online material, video, documents, or external resources. | Employee portals, search indexes, Jira, external learning catalogs | Martini transforms content metadata and links, applies availability and classification rules, and routes file or document payloads only where the customer's Workday capability supports them. |
| Learning Item | Represents a catalog item such as a course, content package, blended offering, or other learning activity. | ServiceNow, Salesforce, intranets, learning catalogs | Martini preserves the Workday identifier, effective dates, item type, and status while mapping the item into the target catalog or compliance model. |
| Learning Enrollment | Represents a learner's registration, assignment, or participation relationship with a learning item or course. | ServiceNow, Salesforce, compliance applications, workforce communications | Martini processes enrollments incrementally, uses stable identifiers for idempotent upserts, applies worker and effective-date rules, and records checkpoints for replay. |
| Learner | Represents a Workday worker or other person who can be assigned learning and receive completion or certification information. | ServiceNow, Salesforce, NetSuite, collaboration applications | Martini maps Workday worker or learner identifiers, organization context, status, and eligibility attributes while minimizing the data sent to each target. |
| Learning Campaign | Represents a coordinated assignment or promotion of learning to a defined population. | Microsoft Teams, Slack, ServiceNow, employee portals | Martini extracts campaign details where exposed, resolves audience and timing rules, generates notifications or downstream assignments, and prevents duplicate processing. |
Authentication and security considerations
Tenant-specific authentication
Workday integrations commonly use OAuth 2.0 API clients and tenant-authorized scopes for REST APIs. Applicable SOAP services may use Integration System Users and WS-Security credentials. Authentication does not replace Workday security-domain and business-process permissions.
Secrets and endpoints
Tenant URLs, region-specific hostnames, client identifiers, client secrets, refresh tokens, and service credentials should be stored in Martini environment configuration and secrets rather than hard-coded in workflows.
Least privilege
- Grant only the Workday domains, operations, scopes, and report access required by the integration.
- Test each operation with the same security principal intended for production.
- Expose controlled Martini APIs so downstream consumers do not need direct Workday credentials.
Operational considerations for Workday Learning integrations
Pagination and checkpoints
Learning Courses, Learning Items, and Learning Enrollments may be large collections. Use pagination, incremental filters, reports, or approved bulk mechanisms, and advance checkpoints only after downstream writes succeed.
Rate limits and retries
Tenant capacity, API policies, and scheduling constraints can limit request volume. Use bounded concurrency, page-size tuning, exponential backoff, and limited retries for transient failures. Do not repeatedly retry validation or authorization errors.
Idempotency and reconciliation
Use stable Workday identifiers as external keys and design target writes as idempotent upserts. Periodic reconciliation helps identify missed events, failed report runs, or downstream delivery gaps.
Effective dating and schema changes
Preserve effective dates and worker-status context where relevant. Workday releases, API versions, WSDLs, reports, enumerations, and security requirements can change, so mappings should be versioned and tested against the target tenant.
Why use Martini instead of scripts or point-to-point integrations?
Orchestrate more than an API call
Martini coordinates Workday REST and SOAP calls, reports, files, target-system APIs, schedules, controlled API façades, business rules, and checkpoint management in maintainable workflows.
Separate transformation from transport
Mappings can normalize Workday XML or JSON into canonical models and target-specific payloads while preserving identifiers, effective dates, and operational metadata.
Operate integrations reliably
- Apply bounded retries, validation, idempotency, pagination, and reconciliation patterns.
- Keep tenant configuration and credentials outside workflow logic.
- Centralize error handling and monitoring instead of duplicating behavior across point-to-point scripts.
Frequently asked questions
Workday Learning can be integrated through Workday REST APIs, Workday Public Web Services using SOAP, approved reports and integration processes, bulk or asynchronous mechanisms, selected event or callback patterns, and file-oriented integrations where enabled. The available resources and operations depend on the Workday tenant, API version, subscription, and security configuration.
Yes. Martini can integrate with Workday Learning by consuming confirmed Workday REST or SOAP endpoints, processing approved reports or files, receiving supported event or callback requests, exposing controlled APIs, and orchestrating scheduled synchronization workflows. No native Martini Workday Learning connector is documented in the supplied sources.
No. A dedicated Workday Learning connector is not required. Martini can use Workday's confirmed native integration mechanisms, including REST APIs, SOAP services, approved reports, files, authentication methods, and supported event or callback endpoints.
Lonti does not charge an additional per-connector or per-vendor fee to integrate Workday Learning. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from Workday, cloud infrastructure, or other third-party systems depending on subscriptions, usage, and deployment model.
Use REST when the required Learning resource and operation are available and a JSON-based interface is preferred. Use SOAP when the required operation is exposed through Workday Public Web Services, an existing integration depends on WSDLs, or REST coverage is incomplete. The tenant's enabled services and security configuration should determine the final choice.
Only where the customer's Workday configuration and the specific Workday service provide a supported event or callback mechanism. Universal Workday Learning webhook coverage should not be assumed. When callback delivery is unavailable, Martini can use scheduled incremental polling or approved reports and integration processes.
Use a scheduled or event-triggered Martini workflow that retrieves pages or batches, preserves Workday identifiers and effective dates, maps the data into the target model, applies business rules, and performs idempotent upserts. Checkpoints should advance only after successful processing, with reconciliation available for independently failed deliveries.
Use pagination, incremental filters, reports, or approved bulk and asynchronous integration mechanisms. Martini can process pages or batches with bounded concurrency, apply throttling, retry transient failures, and retain rejected records without reprocessing successful records.
Related Martini documentation
Workday APIs
Workflow Design
Data Handling
Integrate Workday Learning with Martini
Use Martini to connect Workday Learning with enterprise applications through secure APIs, scheduled workflows, approved events, reports, and file-based integration patterns.