Lever + Workday REST
Connect Lever and Workday to Build a Hire-to-Onboard Pipeline That Actually Works
Push candidate data from Lever straight into Workday the moment an offer is accepted — no manual re-entry, no delays.
Why integrate Lever and Workday REST?
Lever and Workday do different jobs. Lever handles sourcing, nurturing, and moving candidates through your hiring pipeline. Workday takes over once someone signs an offer and manages everything after that. The problem is the gap between them. When these two systems don't talk to each other, HR teams spend hours manually transcribing data that already exists, and new hires feel the friction before they've even started. Connecting Lever to Workday through tray.ai closes that gap — hired candidate data flows instantly and accurately into Workday, and the people who need to act on it get notified without anyone having to chase them down.
Automate & integrate Lever & Workday REST
Use case
Automated New Hire Record Creation in Workday
When a candidate moves to 'Hired' or accepts an offer in Lever, tray.ai automatically creates a new worker record in Workday with their personal details, job title, department, compensation, and start date already filled in. No manual re-entry, no provisioning delays. HR teams can trust that Workday reflects current hiring decisions without anyone touching a keyboard.
Use case
Requisition and Headcount Sync Between Lever and Workday
Job requisitions approved in Workday are automatically pushed to Lever as new postings, so recruiters are always working against authorized headcount. When a role is filled in Lever, that status change flows back to Workday to close the position and update workforce planning reports. Finance, HR, and Talent Acquisition stay aligned without anyone having to manually sync the two systems.
Use case
Candidate Data Enrichment for Offer Management
Before an offer goes out in Lever, tray.ai can pull compensation bands, job grade structures, and cost-center data from Workday to make sure the offer falls within approved pay equity policies. Recruiters and hiring managers get that context without leaving the ATS. Offers move faster, and fewer come back for revision.
Use case
Pre-Boarding Task Initiation Upon Offer Acceptance
The moment a candidate accepts in Lever, tray.ai triggers pre-boarding tasks in Workday — background check initiation, IT equipment requests, benefits enrollment setup, manager notifications. The lag between offer acceptance and productive onboarding prep collapses. Every task gets the correct start date, manager, and department pulled directly from the Lever offer record.
Use case
Internal Mobility and Referral Candidate Tracking
When an internal employee applies through Lever, tray.ai cross-references their existing Workday worker profile to auto-populate application data and flag them as an internal applicant. If they get the role, the integration initiates a job change or transfer transaction in Workday instead of creating a duplicate new hire record. Their employment history stays intact, and the HRIS stays clean.
Use case
Recruiting Metrics and Compliance Reporting
tray.ai can pull pipeline stage data from Lever and workforce and compensation data from Workday, then merge them into a unified talent analytics dataset — time-to-fill by department, offer acceptance rates by job grade, diversity metrics across the full funnel. Neither system can produce these reports alone. Scheduled syncs keep dashboards and compliance reports current without anyone running manual exports.
Use case
Contingent Worker and Agency Hire Management
For contract roles sourced through Lever, tray.ai creates contingent worker records in Workday rather than full employee records, applying the correct worker type, contract end date, and cost center automatically. Staffing coordinators don't need to manually distinguish and route each hire type — the integration handles it. When a contract is extended or converted to full-time, a status change in Lever triggers the right transaction update in Workday.
Get started with Lever & Workday REST integration today
Lever & Workday REST Challenges
What challenges are there when working with Lever & Workday REST and how will using Tray.ai help?
Challenge
Field Mapping Complexity Between ATS and HRIS Schemas
Lever and Workday use fundamentally different data models. Lever organizes data around candidates, opportunities, and postings. Workday structures data around workers, positions, and organizational hierarchies. Mapping fields like compensation, job title, and department between these two schemas manually is error-prone and requires deep knowledge of both APIs. Mismatches in field types, enumerated values, or required fields can cause record creation failures in Workday that are hard to diagnose.
How Tray.ai Can Help:
tray.ai's visual data mapper and built-in transformation functions let you define precise field mappings between Lever and Workday schemas without writing custom code. You can handle enumerated value translation, conditional logic for different worker types, and data type conversions in a single reusable workflow step. When record creation fails in Workday, the platform's error handling surfaces enough detail to fix the problem quickly.
Challenge
Managing Workday's Strict Data Validation Requirements
Workday's REST API enforces strict validation on new worker records, requiring values for fields like supervisory organization, position, pay group, and cost center that may not be fully captured in Lever's offer data. When these fields are missing or incorrectly formatted, the Workday API returns errors that stall the automation and require manual intervention — defeating the point of the integration.
How Tray.ai Can Help:
tray.ai lets you build pre-validation logic into your workflows that checks for required Workday fields before attempting record creation, and can trigger automated lookup steps to fetch missing values — such as supervisory org or pay group — from Workday reference data based on department or location. Conditional branches handle edge cases without breaking the workflow, and notification steps alert the HR team only when human input is genuinely needed.
Challenge
Handling Duplicate Records and Rehire Scenarios
When a candidate who's already in Workday — a rehire, a boomerang employee, or an internal transfer — gets hired through Lever, a naive integration will try to create a duplicate worker record, corrupting historical data and creating compliance problems. Catching these scenarios requires cross-referencing Lever candidate data against existing Workday worker records before any record creation happens.
How Tray.ai Can Help:
tray.ai workflows can include a pre-hire lookup step that searches Workday for an existing worker record matching the candidate's email address or national ID before creating a new one. If a match is found, the workflow routes to a rehire or job change transaction instead of a new hire creation, preserving employment history and preventing duplicates. HR gets an alert for matched records when human review makes sense.
Challenge
Keeping Requisition Status Synchronized in Real Time
Lever and Workday each track their own version of a job requisition's status, and without integration, they fall out of sync fast. A position filled in Lever may stay open in Workday for days, skewing workforce planning reports and causing Finance to hold budget unnecessarily. Manual status updates lag behind actual hiring activity and get applied inconsistently.
How Tray.ai Can Help:
tray.ai uses event-driven triggers from Lever webhooks to catch status changes — a posting being closed or archived — the moment they happen and immediately updates the corresponding Workday requisition via REST API. Bidirectional sync rules ensure changes originating in either system are reflected in the other, and conflict resolution logic prevents race conditions when both systems update at the same time.
Challenge
Secure Handling of Sensitive Candidate and Employee PII
The data moving between Lever and Workday includes some of the most sensitive information an organization holds — Social Security numbers, compensation details, home addresses, background check results. Any integration touching this data has to comply with GDPR, CCPA, and internal data governance policies. PII can't be logged insecurely, cached longer than necessary, or sent anywhere it shouldn't go.
How Tray.ai Can Help:
tray.ai is built for enterprise security requirements: SOC 2 Type II compliance, encryption in transit and at rest, and role-based access controls that limit which team members can view or modify workflows handling PII. Sensitive fields can be masked in workflow logs, and tray.ai's audit trail gives a complete record of data access and transformation events to support compliance reviews and security audits.
Start using our pre-built Lever & Workday REST templates today
Start from scratch or use one of our pre-built Lever & Workday REST templates to quickly solve your most common use cases.
Lever & Workday REST Templates
Find pre-built Lever & Workday REST solutions for common use cases
Template
Lever Hired Candidate → Workday New Worker Record
This template watches Lever for candidates whose stage advances to 'Hired' or whose offer status changes to 'Accepted' and automatically creates a fully populated new worker record in Workday, mapping all relevant fields including name, job title, department, manager, start date, and compensation package.
Steps:
- Trigger: Lever webhook fires when a candidate's offer status changes to Accepted
- Transform: Map Lever candidate and offer fields to Workday new hire worker schema
- Action: Create new worker record in Workday via REST API with all mapped fields
- Notify: Send confirmation to HR coordinator with Workday worker ID and onboarding checklist link
Connectors Used: Lever, Workday REST
Template
Workday Approved Requisition → Lever Job Posting
This template listens for newly approved job requisitions in Workday and automatically creates corresponding job postings in Lever, including job description, department, hiring manager assignment, and compensation band, so recruiters can start sourcing without waiting on a manual handoff.
Steps:
- Trigger: Workday REST API detects a new requisition entering Approved status
- Fetch: Retrieve full requisition details including job description, org, and compensation range from Workday
- Transform: Map Workday requisition fields to Lever job posting schema
- Action: Create new job posting in Lever with all requisition data and notify assigned recruiter
Connectors Used: Workday REST, Lever
Template
Lever Offer Acceptance → Workday Pre-Boarding Task Bundle
When a candidate accepts an offer in Lever, this template triggers a coordinated set of pre-boarding actions in Workday — creating onboarding tasks, assigning them to the correct owners (IT, HR, Facilities), and setting due dates relative to the candidate's start date, so every department is ready before day one.
Steps:
- Trigger: Lever webhook detects offer acceptance event for a specific candidate
- Fetch: Retrieve start date, department, location, and manager from Lever offer record
- Action: Create onboarding task bundle in Workday with owner assignments and calculated due dates
- Action: Send onboarding summary email to hiring manager and new hire via Workday notification
Connectors Used: Lever, Workday REST
Template
Lever Filled Position → Workday Requisition Closure
When a position is marked hired and closed in Lever, this template automatically updates the corresponding open requisition in Workday to Filled status, keeping headcount reports and workforce planning dashboards accurate without requiring manual updates from recruiters.
Steps:
- Trigger: Lever posting status changes to Closed with a reason of Hired
- Lookup: Match Lever job posting to the corresponding Workday requisition by requisition ID or job code
- Action: Update Workday requisition status to Filled via REST API
- Log: Record closure timestamp and hired candidate reference for audit trail
Connectors Used: Lever, Workday REST
Template
Workday Job Change → Lever Internal Applicant Flag
This template cross-references active Lever applications against Workday worker records to identify internal candidates, automatically tagging them in Lever with their current role, tenure, and department so hiring managers have full context when reviewing internal applicants without needing to open Workday separately.
Steps:
- Trigger: New application submitted in Lever containing an email that matches an active Workday worker
- Fetch: Retrieve current job title, department, tenure, and manager from Workday worker record
- Action: Update Lever candidate profile with internal applicant tag and Workday enrichment data
- Notify: Alert recruiter and hiring manager that the applicant is an internal candidate with context summary
Connectors Used: Workday REST, Lever
Template
Lever + Workday Unified Recruiting Analytics Sync
This scheduled template pulls pipeline stage data, time-to-fill metrics, and offer data from Lever alongside compensation, department, and workforce data from Workday, merging them into a unified dataset delivered to a BI tool or data warehouse for cross-platform talent analytics and compliance reporting.
Steps:
- Schedule: Trigger runs nightly or on a configurable cadence
- Fetch: Pull open and closed requisition data, pipeline stages, and offer outcomes from Lever API
- Fetch: Pull workforce, compensation band, and department hierarchy data from Workday REST API
- Transform: Merge and normalize datasets with shared keys such as requisition ID and job code
- Deliver: Push unified dataset to data warehouse or BI platform for reporting and compliance dashboards
Connectors Used: Lever, Workday REST