Ellipse Gradient for Header
Workday Recruiting logo

Workday Recruiting Integration Guide

Integrate Workday Recruiting with enterprise applications through tenant-specific REST APIs, SOAP web services, reports, files, and configured outbound integration processes.

Workday Recruiting integration options at a glance

Workday Recruiting integrations can use REST APIs where the required resource and operation are available, or Workday Web Services SOAP APIs for broader or established business-object coverage. Reports, Enterprise Interface Builder-style processes, and file-based outputs support scheduled exports, reconciliation, and bulk movement of data. Workday also supports selected event-driven and outbound integration patterns, although coverage depends on the business process and tenant configuration rather than a universal webhook stream. Martini can consume these interfaces, authenticate with OAuth 2.0 or integration credentials, transform JSON, XML, and files, orchestrate scheduled workflows, expose controlled APIs, and manage checkpoints, retries, and operational exceptions.

Integration pointSupported by Workday Recruiting?Common use casesHow Martini supports it
REST APIsLimitedWorkday provides REST APIs for selected applications and business objects. Recruiting resource and operation coverage varies by API version, tenant configuration, licensed features, and security permissions.Martini can consume supported Workday REST endpoints, send authenticated requests, process JSON responses, apply validation and business rules, and expose a controlled REST API for downstream consumers.
SOAP APIsYesWorkday Web Services provide SOAP operations for many business objects and processes and may be required for Recruiting operations not exposed through REST or for existing WSDL-based integrations.Martini can consume Workday SOAP services, construct XML requests, parse SOAP responses and faults, and transform XML into downstream application formats.
Reports and file-based integrationsYesReports, report-based outputs, Enterprise Interface Builder-style processes, and files support scheduled exports, reconciliation, and bulk synchronization where transactional APIs are not required.Martini can retrieve or process configured outputs, parse structured files, map rows into canonical models, and maintain checkpoints for incremental processing.
Bulk and asynchronous processingLimitedWorkday supports bulk and asynchronous integration processes through reports, integration systems, and file-based processing. Exact Recruiting operations depend on the tenant and selected service.Martini can orchestrate long-running and scheduled workflows, process files or pages incrementally, record checkpoints, and route failed items for retry or review.
Events and outbound callbacksLimitedWorkday supports configured outbound and event-driven patterns for selected business processes and integration scenarios, but not an unrestricted generic webhook stream for every Recruiting change.Martini can receive configured outbound notifications where available. If no suitable event exists, Martini can use scheduled polling or incremental report extraction.
File and attachment APIsLimitedCandidate and application processes may include resumes, cover letters, and other documents. Attachment operations and payload requirements depend on the relevant Workday service or WSDL.Martini can orchestrate document retrieval and transfer, handle binary content and metadata, and apply duplicate, file-size, content-type, and security rules after tenant capabilities are confirmed.
AuthenticationYesSupported patterns include OAuth 2.0 for applicable APIs, integration system users, Basic Authentication where enabled, and WS-Security credentials for SOAP services.Martini can store credentials and tokens in environment configuration or secrets, authenticate requests, and keep authorization separate from workflow logic.
Database and analytics accessNoDirect access to Workday’s underlying application database is not supported. Controlled extraction should use APIs, reports, web services, or configured integration outputs.Martini can consume approved report or API outputs and write normalized data to an authorized downstream database when analytical persistence is required.

How Workday Recruiting exposes data and business events

Workday Recruiting REST APIs

Workday REST APIs provide access to selected applications and business objects. Recruiting coverage is not universal, so the required resource, operation, API version, tenant feature, and security permission must be confirmed before implementation.

Martini implementation pattern

Martini implementation pattern: Martini workflows authenticate to the supported Workday REST endpoint, retrieve or submit JSON, validate response status and business data, map the result to a canonical model, and persist a checkpoint or correlation identifier for subsequent processing.

Implementation sequence

Authenticate with an approved OAuth 2.0 client or integration credential
Call the confirmed Workday Recruiting REST resource
Process pagination or incremental filters where supported
Validate the response and map JSON fields
Apply business rules and write the target result
Store a checkpoint and route failures for retry or reconciliation

Workday Web Services SOAP APIs

Workday Web Services expose SOAP operations for many Workday business objects and processes. SOAP may be required when a Recruiting operation is unavailable through REST or when an existing integration depends on Workday WSDLs.

Martini implementation pattern

Martini implementation pattern: Martini constructs an XML request with the required Workday references and credentials, sends it to the configured SOAP service, parses the response or SOAP fault, transforms the result, and records business-process outcomes separately from transport errors.

Implementation sequence

Load the configured Workday WSDL and service details
Authenticate with the permitted SOAP integration credentials
Construct the XML request with required references
Send the SOAP request and parse the response
Handle SOAP faults and business validation messages
Map the result and store correlation information

Reports and file-based integrations

Workday reports and file-based integration processes support scheduled exports, reconciliation, and bulk movement of Recruiting data. Their behavior depends on report design, output format, security, and tenant configuration.

Martini implementation pattern

Martini implementation pattern: a scheduled workflow retrieves or receives the configured report or file, parses rows and metadata, maps them to canonical objects, filters already processed items using a checkpoint, and writes valid results while isolating malformed or rejected rows.

Implementation sequence

Start the scheduled extraction workflow
Retrieve the configured report or file output
Parse the supported file or structured response
Validate rows and map them to canonical objects
Process new or changed rows using the checkpoint
Write results and record rejected rows for reconciliation

Outbound events and integration processes

Workday supports selected event-driven and outbound integration patterns through business processes and its integration framework. These should not be treated as unrestricted generic webhooks for every Recruiting event.

Martini implementation pattern

Martini implementation pattern: where the tenant provides a suitable outbound notification, Martini receives the event through an exposed API or configured endpoint, retrieves current Workday state when necessary, applies event-specific rules, and sends the result downstream. If no event is available, the same workflow can be driven by polling or reports.

Implementation sequence

Receive the configured Workday outbound notification
Validate the event and deduplicate its correlation data
Retrieve current object state when the notification is incomplete
Apply business-process and data-minimization rules
Send the mapped result to downstream systems
Acknowledge or record the outcome and retry transient failures

Candidate documents and attachments

Candidate and Job Application processes may include resumes, cover letters, and other documents. Document operations and payload formats vary by Workday service, API version, and tenant configuration.

Martini implementation pattern

Martini implementation pattern: Martini calls the confirmed Workday document operation, handles binary content and metadata, validates content type and size, transfers the document to an approved repository or application, and records a safe correlation reference without logging sensitive content.

Implementation sequence

Confirm the tenant’s supported document operation
Retrieve the document and associated metadata
Validate content type, size, and document identity
Apply malware, retention, and duplicate-handling controls
Transfer the document to the approved target
Record the outcome without exposing document contents in logs

Common Workday Recruiting integration patterns

Pattern 1: Synchronize job requisitions and postings

When to use this pattern

Use this pattern when approved hiring requirements and their internal or external postings must be published to a careers site, job board, external recruiting platform, or analytics store. It is suitable for scheduled synchronization where immediate event delivery is not required.

Integration direction
Workday Recruiting
Martini
Careers site or job board
Example Mapping
Workday Recruiting FieldCanonical FieldTarget Field
Job Requisition IDsourceIdexternalRequisitionId
Job Posting TitletitlejobTitle
Job Posting StatusstatuspostingStatus
Primary Locationlocationlocation
Martini implementation pattern

A scheduler starts a Martini workflow that calls the confirmed Workday REST or SOAP service, or retrieves an incremental report. Martini filters approved requisitions, joins related Job Postings where necessary, maps location and organization values, publishes the result, stores a checkpoint, and retries transient failures while routing validation failures to reconciliation.

Martini capabilities used
  • workflows
  • scheduled triggers
  • API consumption
  • file and XML processing
  • data mapping
  • business rules
  • checkpointing
  • error handling

Pattern 2: Synchronize candidates and job applications

When to use this pattern

Use this pattern when Candidate and Job Application data must be shared with Salesforce, an onboarding application, a support platform, or an analytics store. The design must preserve the distinction between one Candidate and multiple Job Applications.

Integration direction
Workday Recruiting
Martini
Salesforce or onboarding application
Example Mapping
Workday Recruiting FieldCanonical FieldTarget Field
Candidate IDcandidateIdcandidateExternalId
Job Application IDapplicationIdapplicationExternalId
Application StatusapplicationStatusstatus
Job Requisition IDrequisitionIdrequisitionReference
Martini implementation pattern

Martini retrieves changed Candidates and Job Applications through a supported API or report, validates privacy and authorization rules, maps each application independently, and performs idempotent upserts using Workday identifiers or approved external keys. The workflow records rejected objects separately and does not retry permanent validation errors.

Martini capabilities used
  • workflows
  • API consumption
  • incremental synchronization
  • data mapping
  • data minimization
  • business rules
  • idempotency
  • error handling

Pattern 3: Route recruiting status and offer events

When to use this pattern

Use this pattern when approved Job Application or Offer milestones should initiate onboarding, access-request, document-signature, notification, or identity processes. It can use a configured outbound Workday event or scheduled state detection.

Integration direction
Workday Recruiting
Martini
ServiceNow, DocuSign, or Okta
Example Mapping
Workday Recruiting FieldCanonical FieldTarget Field
Offer StatusofferStatusworkflowState
Job Application IDapplicationIdsourceCorrelationId
Candidate IDcandidateIdsubjectExternalId
Offer Approval StatusapprovalStateapprovalStatus
Martini implementation pattern

Martini receives a configured outbound notification or polls an incremental report, retrieves current Workday state when needed, verifies that the business-process state is eligible, minimizes sensitive fields, and calls the downstream application. Correlation IDs, duplicate detection, retry policy, and manual-review routing are included in the workflow.

Martini capabilities used
  • event-driven workflows
  • scheduled triggers
  • API consumption
  • data mapping
  • business rules
  • security controls
  • idempotency
  • retry handling

Pattern 4: Transfer candidate documents

When to use this pattern

Use this pattern when supported resumes, cover letters, or other candidate documents must be copied to an approved document repository or downstream recruiting application. It should only be implemented after the relevant Workday attachment operation and tenant limits are confirmed.

Integration direction
Workday Recruiting
Martini
Document repository
Example Mapping
Workday Recruiting FieldCanonical FieldTarget Field
Candidate IDcandidateIdsubjectExternalId
Document TypedocumentTypecontentCategory
Document File NamefileNamename
Document ContentbinaryContentfileContent
Martini implementation pattern

Martini retrieves the supported document payload, validates file identity, content type, and size, applies duplicate and retention rules, and transfers the binary content securely. The workflow stores only necessary metadata and correlation information, retries transient transfer failures, and sends unsupported or malformed documents to review.

Martini capabilities used
  • workflows
  • API consumption
  • binary and file handling
  • data mapping
  • security controls
  • duplicate detection
  • error handling

Applications commonly integrated with Workday Recruiting

Workday Recruiting data can be coordinated with adjacent enterprise applications when recruiting milestones need to trigger operational, collaboration, document, identity, or onboarding processes. The exact scope should be confirmed against the customer’s Workday tenant, licensed features, security configuration, and business-process design.

Application Scenario Direction Martini Pattern
Salesforce Synchronize selected Candidate, Prospect, or Job Application information with talent relationship and business development processes. Workday Recruiting → Martini → Salesforce Martini retrieves approved or changed recruiting data through Workday REST, SOAP, or report-based interfaces, preserves Workday identifiers, maps the data to Salesforce objects, and applies filtering, deduplication, retry, and reconciliation rules.
ServiceNow Create or update onboarding, access-request, or HR service tasks when recruiting or offer milestones reach an approved state. Workday Recruiting → Martini → ServiceNow A scheduled or configured outbound Workday process starts a Martini workflow. Martini validates the recruiting state, minimizes personal data, maps the event to ServiceNow task fields, submits the request, and records correlation and error information.
Okta Support identity lifecycle or pre-hire processes after a candidate reaches an approved hiring or onboarding state. Workday Recruiting → Martini → Okta Martini consumes an approved Workday status change or incremental extract, applies eligibility and security rules, transforms the required identity attributes, and calls the configured Okta API while avoiding unnecessary candidate data.
DocuSign Coordinate electronic signature processes for offer-related or employment documents where the tenant has configured the relevant process. Workday Recruiting → Martini → DocuSign Martini retrieves eligible Offer data and supported document metadata, submits the required envelope or document payload to DocuSign, receives status updates through the configured interface, and writes controlled status information back to the appropriate workflow.
Microsoft Teams Coordinate recruiting or interview-related collaboration and notifications for recruiting teams. Workday Recruiting → Martini → Microsoft Teams Martini detects a configured recruiting event or scheduled status change, applies notification rules, transforms the message content, and sends a controlled notification to Microsoft Teams with correlation data for operational traceability.
Slack Send controlled recruiting notifications, approval alerts, or operational messages to authorized teams. Workday Recruiting → Martini → Slack A Martini workflow retrieves or receives the relevant Workday event, removes sensitive information, applies routing rules, and publishes a formatted message to Slack with retry and failure handling.
Jira Track recruiting technology, hiring operations, or onboarding tasks associated with recruiting events. Workday Recruiting → Martini → Jira Martini maps selected Job Requisition, Job Application, or Offer milestones to Jira issue fields, maintains an external correlation key, and updates or creates issues idempotently through the configured Jira API.
NetSuite Share approved worker or organizational information after recruiting and hiring processes complete, typically as part of a broader Workday HCM flow. Workday Recruiting → Martini → NetSuite Martini filters recruiting outputs to approved downstream data, enriches them with required organizational values, maps the payload to NetSuite, and separates recruiting-stage exceptions from post-hire synchronization failures.

How to build a Workday Recruiting integration in Martini

Objective

Establish access to the customer’s Workday tenant using the authentication method required by the selected interface and the permissions assigned to the integration system user or OAuth client.

Instructions in Martini

  • Confirm the Workday release, API version, tenant features, and required Recruiting operations
  • Choose OAuth 2.0, Basic Authentication where enabled, or SOAP WS-Security as appropriate
  • Store credentials and tokens in Martini environment configuration or secrets
  • Verify Workday security domains and least-privilege permissions

Objective

Select a trigger that matches the required delivery latency and the event coverage available in the Workday tenant.

Instructions in Martini

  • Use a configured outbound business-process integration when a suitable event is available
  • Use a Scheduler Trigger for predictable incremental synchronization
  • Define modified-date, effective-date, status, report, or other supported checkpoints
  • Avoid assuming a universal Workday Recruiting webhook stream

Objective

Call the confirmed Workday interface and obtain the current business object or report data required by the workflow.

Instructions in Martini

  • Consume the supported REST resource or SOAP operation
  • Retrieve report or file outputs for bulk and reconciliation use cases
  • Process pagination, batching, and asynchronous results as supported
  • Preserve Workday identifiers and relevant response correlation data

Objective

Coordinate retrieval, validation, enrichment, target calls, and operational outcomes in a maintainable Martini workflow.

Instructions in Martini

  • Separate Candidate data from Job Application data
  • Retrieve current object state when an event is incomplete
  • Use reusable workflow logic for common authentication, validation, and error handling
  • Apply explicit business-process and authorization rules before state-changing operations

Objective

Convert Workday JSON, XML, report, or file structures into the canonical and target models required by downstream applications.

Instructions in Martini

  • Map stable Workday IDs rather than display names alone
  • Transform JSON and XML payloads into the target format
  • Normalize status, location, organization, and date values
  • Minimize personal and sensitive data before forwarding it

Objective

Ensure that only eligible recruiting data and approved business-process states reach downstream systems.

Instructions in Martini

  • Validate requisition, posting, application, and offer status values
  • Check approval and business-process state before triggering downstream actions
  • Apply consent, visibility, retention, and data-minimization rules
  • Reject permanent validation failures without repeated retries

Common Workday Recruiting data objects used in integrations

ObjectTypical UseCommon target systemsMartini handling
Job RequisitionRepresents an approved hiring requirement, including recruiting restrictions, organization, staffing information, and hiring details.Careers sites, job boards, Salesforce, analytics stores, JiraMartini retrieves the object through supported REST, SOAP, or report interfaces, maps stable Workday identifiers and status values, applies approval and visibility rules, and synchronizes changes idempotently.
Job PostingRepresents an internal or external posting associated with a Job Requisition.Careers sites, job boards, recruiting platforms, analytics storesMartini maps posting content, location, organization, and status, separates posting data from requisition data, and uses checkpoints or modified-date criteria for incremental synchronization.
CandidateRepresents an individual participating in the recruiting process or being considered for a role.Salesforce, analytics stores, onboarding applications, document repositoriesMartini minimizes personal data, preserves the Workday Candidate identifier, applies privacy and authorization rules, and avoids using names or email addresses as the sole correlation key.
Job ApplicationRepresents a Candidate’s application for a specific Job Requisition.Salesforce, ServiceNow, onboarding platforms, analytics storesMartini treats Job Application separately from Candidate so one person can have multiple applications, maps application status and requisition references, and checks current state before retries or transitions.
ProspectRepresents a potential candidate identified or sourced before submitting an application.Salesforce, recruiting relationship platforms, analytics storesMartini synchronizes Prospect data selectively, preserves source and correlation identifiers, applies consent and data-minimization rules, and routes duplicates for reconciliation.
OfferRepresents an employment offer and associated details and approval status.DocuSign, ServiceNow, onboarding applications, identity platformsMartini filters sensitive fields, validates approval state, maps offer status to downstream actions, and distinguishes retryable transport failures from business-process validation errors.

Authentication and security considerations

Tenant-aware authentication

Workday integrations commonly use OAuth 2.0 for supported APIs, or integration system users with Basic Authentication and WS-Security credentials for applicable services. Authentication does not itself grant access; Workday security domains, scopes, tenant configuration, and business-process permissions must also allow the requested operation.

Protect credentials and candidate data

  • Store OAuth credentials, tokens, passwords, and integration configuration in Martini environment configuration or secrets.
  • Use a dedicated Workday integration system user with least-privilege security groups and domain permissions.
  • Minimize Candidate, Job Application, Offer, resume, and contact data passed to downstream systems.
  • Avoid logging tokens, resumes, and unnecessary personally identifiable information.
  • Apply secure transport, access controls, retention rules, and document-handling protections.

Operational considerations for Workday Recruiting integrations

Rate limits and pagination

Workday tenants may enforce service protection, concurrency, or request-volume controls. Use incremental filters, scheduled batching, pagination, and backoff rather than repeated full reads.

State and idempotency

Persist Workday identifiers, external correlation keys, checkpoints, and synchronization outcomes. Deduplicate repeated events or report rows and verify current business-process state before repeating a transition.

Retries and reconciliation

Retry transient transport failures, throttling, and temporary service errors with controlled backoff. Route authentication failures, missing references, malformed payloads, and business-process validation errors to operational review instead of retrying indefinitely.

Release and schema changes

Workday releases, API versions, WSDL structures, fields, enumerations, and business-process behavior can change. Use explicit mappings, validation, tenant-specific testing, and controlled deployment practices.

Attachments and sensitive content

Resume and document flows require confirmation of payload format, file size, MIME type, duplicate handling, virus scanning, retention, and downstream access controls.

Why use Martini instead of scripts or point-to-point integrations?

Centralized integration logic

Martini provides a maintainable workflow layer between Workday Recruiting and downstream applications. Instead of duplicating API calls and business rules across scripts or point-to-point interfaces, teams can centralize authentication, orchestration, mappings, validation, and error handling.

Flexible interface choices

Workday Recruiting coverage varies by tenant. Martini can consume the appropriate REST or SOAP interface, process reports and files, receive configured outbound events, and switch to scheduled polling when event coverage is unavailable.

Operational reliability

Workflows can use checkpoints, incremental extraction, idempotency, retries, reconciliation paths, and controlled logging. This supports long-running and scheduled synchronization without treating every failure as a retryable error.

Reusable enterprise APIs

Martini can expose a controlled API façade that shields downstream systems from Workday-specific versions, XML structures, tenant permissions, and business-process details while preserving the flexibility to use custom logic when required.

Frequently asked questions

How can Workday Recruiting be integrated with enterprise systems?

Workday Recruiting can be integrated through supported REST APIs, Workday Web Services SOAP APIs, reports, file-based integration outputs, and selected outbound or event-driven business-process mechanisms. The available operations depend on the Workday release, tenant configuration, licensed features, API version, and security permissions.

Can Martini integrate with Workday Recruiting?

Yes. Martini can integrate with Workday Recruiting by consuming supported Workday REST APIs and SOAP web services, processing reports and files, receiving configured outbound integration notifications, and orchestrating scheduled synchronization workflows. No native Martini Workday connector is documented in the supplied product context.

Do I need a connector to integrate Workday Recruiting with Martini?

No. A dedicated Workday Recruiting connector is not required. Martini can use Workday’s confirmed native integration mechanisms, including REST APIs, SOAP services, reports, file-based outputs, authentication methods, and configured outbound integration processes.

Is there any extra Lonti cost to integrate Workday Recruiting with Martini?

Lonti does not charge an additional per-connector or per-vendor fee to integrate Workday Recruiting with Martini. Integrations are subject to the provisioned capacity of the Martini environment. Separate costs may apply from Workday, infrastructure providers, document repositories, or other third-party systems based on subscriptions, usage, and deployment model.

Should a Workday Recruiting integration use REST or SOAP?

Use REST when the required Recruiting resource and operation are available and supported in the tenant. Use Workday SOAP Web Services when the operation is available only through SOAP, an existing integration depends on WSDLs, or SOAP provides the required business-object or business-process coverage.

Does Workday Recruiting provide webhooks or event notifications?

Workday supports selected outbound and event-driven integration patterns through its integration framework and business processes, but it should not be treated as providing a universal webhook stream for every Recruiting change. Where no suitable event is available, Martini can use scheduled polling or incremental report extraction.

How does synchronization handle candidates and applications?

Candidate and Job Application should be synchronized as separate Workday objects because one Candidate can have multiple applications. Martini can preserve Workday identifiers, use approved external correlation keys, process incremental changes, and apply idempotent updates and reconciliation rules.

Can Martini expose an API façade for Workday Recruiting?

Yes. Martini can expose a controlled REST API that standardizes selected Workday Recruiting operations for downstream applications. The façade can centralize authentication, validation, field mapping, business rules, tenant-specific API calls, error handling, and data minimization without exposing Workday directly.

Related Martini documentation

API Integration

Workflows

Security

Operations

Data Formats

Connect Workday Recruiting with Martini

Use Martini to orchestrate Workday Recruiting APIs, SOAP services, reports, files, and configured outbound processes with secure authentication, reusable workflows, controlled data mapping, and operational safeguards.

EXPLORE MARTINI
BOOK A DEMO