Connectors / Integration
Lever + Greenhouse Integration: Unify Your Recruiting Operations
Sync candidate data, job postings, and hiring workflows between Lever and Greenhouse to cut manual work and hire faster.
Lever + Greenhouse integration
Lever and Greenhouse are two of the most widely used applicant tracking systems around, and plenty of organizations run both at once — after a merger, because different teams have different preferences, or mid-way through a migration. Without reliable data sync, that setup gets messy fast. Manually reconciling candidate records, interview feedback, and job requisitions across two systems creates data silos, slows down hiring decisions, and introduces errors that are annoying to catch and painful to fix. Connecting Lever and Greenhouse through tray.ai lets talent acquisition teams keep a single source of truth while still using whichever platform works best for each part of the business.
When recruiting teams use both Lever and Greenhouse at the same time, disconnected systems become a real problem quickly. Duplicate candidate profiles, inconsistent pipeline stages, missed follow-ups — and that's before you get to reporting. Integrating Lever and Greenhouse with tray.ai lets talent ops leaders automate candidate record syncing, mirror job requisition statuses, propagate offer approvals, and keep interview scorecards consistent across both platforms in real time. Hiring managers always see current information regardless of which ATS they're in, recruiters stop re-entering the same data twice, and pipeline reporting actually reflects reality. The result is a faster candidate experience and a recruiting operation that can grow without piling on administrative work.
Automate & integrate Lever + Greenhouse
Automating Lever and Greenhouse business processes or integrating data is made easy with Tray.ai.
Use case
Bi-Directional Candidate Profile Sync
When a new candidate is created or updated in Lever, their profile — contact details, resume, source, and stage — is automatically mirrored in Greenhouse, and vice versa. Recruiting teams working in either ATS see the same candidate information without manual re-entry. Deduplication logic prevents duplicate records from building up in either system.
- Eliminates duplicate candidate records across both ATS platforms
- Gives recruiters in either system real-time access to current candidate data
- Reduces manual data entry errors that can slow or derail hiring decisions
Use case
Job Requisition and Opening Sync
New job requisitions created in Greenhouse are automatically published as corresponding job postings in Lever, keeping both systems aligned on open roles. Updates like headcount changes, location edits, or requisition closures propagate instantly between platforms. Talent ops teams no longer need to duplicate job configurations across both ATS environments by hand.
- Prevents open roles from being missed or double-listed across ATS platforms
- Keeps pipeline stages consistent and visible to hiring managers across Lever and Greenhouse
- Saves hours of administrative work when managing large volumes of open requisitions
Use case
Interview Scorecard and Feedback Propagation
Structured interview feedback submitted in Greenhouse is automatically transferred to the corresponding candidate record in Lever, and feedback from Lever is synced back to Greenhouse. Hiring managers get a consolidated view of all interviewer evaluations regardless of which platform collected them. Scorecards, ratings, and written comments are all preserved in the receiving system.
- Gives hiring managers complete feedback visibility without switching between platforms
- Preserves structured scorecard data including ratings and written evaluations
- Speeds up hiring decisions by surfacing all relevant interview feedback in one place
Use case
Offer Approval Status Mirroring
When an offer is approved or rejected in one ATS, the status change is immediately reflected in the other, keeping compensation teams and hiring managers aligned. This prevents situations where an offer is accepted in Lever but the Greenhouse record still shows the candidate as active in pipeline, which creates reporting discrepancies. Automated notifications alert relevant stakeholders when offer statuses change in either direction.
- Eliminates reporting discrepancies caused by out-of-sync offer statuses
- Notifies compensation and HR teams in real time when offers move forward or are declined
- Reduces compliance risk by ensuring both systems reflect accurate candidate disposition
Use case
Candidate Stage Progression Sync
As candidates move through hiring stages in Lever or Greenhouse, their pipeline progression is mirrored in the counterpart system using a configurable stage-mapping schema. Talent ops teams can define how Lever stages map to Greenhouse stages and vice versa, keeping pipeline reporting consistent across both platforms. Automated stage updates can also trigger downstream actions like interview scheduling emails or recruiter task creation.
- Maintains consistent pipeline stage data across both ATS platforms for unified reporting
- Supports custom stage mapping to accommodate differing workflow configurations
- Triggers downstream automation like scheduling or notifications based on stage changes
Use case
Candidate Source Attribution Sync
Source data — job boards, referrals, agencies, campaigns — is synchronized between Lever and Greenhouse so recruiting analytics stay accurate across both systems. When a candidate's source is recorded or updated in either platform, the change is reflected in the other, keeping source-of-hire reports consistent. Teams tracking recruiting ROI and channel effectiveness across a unified candidate database need this to be right.
- Preserves source attribution integrity for accurate recruiting ROI measurement
- Prevents source data loss during candidate migration or dual-ATS operations
- Enables consolidated source-of-hire reporting across both platforms
Challenges Tray.ai solves
Common obstacles when integrating Lever and Greenhouse — and how Tray.ai handles them.
Challenge
Inconsistent Field Schemas Between ATS Platforms
Lever and Greenhouse use different data models, field names, and enumeration values for common concepts like hiring stages, rejection reasons, and candidate sources. Mapping between these schemas by hand is error-prone and breaks whenever either platform updates its data structure.
How Tray.ai helps
tray.ai's visual data mapper lets teams build and maintain field translation logic between Lever and Greenhouse without writing code. Custom mapping tables handle enumeration mismatches like stage name differences, and schema updates can be adjusted in the workflow without rebuilding the entire integration.
Challenge
Avoiding Infinite Update Loops in Bi-Directional Sync
When syncing data in both directions between Lever and Greenhouse, an update in System A triggers a write to System B, which can fire a webhook back to System A — creating an infinite loop that floods both systems with redundant API calls and corrupts data.
How Tray.ai helps
tray.ai lets teams implement loop-prevention logic using conditional checks — comparing last-modified timestamps or checking for a sync-origin flag — before writing to either system. These guardrails are built directly into the workflow logic without requiring custom middleware.
Challenge
Matching Candidates Across Systems Without a Shared Identifier
Lever and Greenhouse each assign their own internal candidate IDs, so there's no native shared key to reliably match a candidate record in one system to its counterpart in the other. Relying on email address matching alone can fail when candidates have multiple email addresses or when data entry inconsistencies exist.
How Tray.ai helps
tray.ai workflows can implement multi-field matching logic — combining email, name, and phone number — to reliably identify candidate matches across both systems. Once a match is confirmed, the workflow stores cross-system ID mappings in a connected data store for faster future lookups.
Templates
Pre-built workflows for Lever and Greenhouse you can deploy in minutes.
New Lever Candidate to Greenhouse Profile Creator
Lever 
Greenhouse Automatically creates a matching candidate profile in Greenhouse whenever a new candidate is added to Lever, mapping all standard and custom fields including name, contact details, source, and resume attachment.
Greenhouse Candidate Stage Update to Lever Stage Sync
Lever Greenhouse When a candidate advances or moves backward through a hiring stage in Greenhouse, their corresponding Lever record is automatically updated to reflect the equivalent stage based on a configurable mapping table.
Lever Interview Feedback to Greenhouse Scorecard Sync
Lever Greenhouse Captures structured interview feedback submitted against a candidate in Lever and creates a corresponding scorecard entry in Greenhouse, preserving interviewer ratings, written comments, and overall recommendation.
Greenhouse Job Opening to Lever Requisition Creator
Lever Greenhouse When a new job is opened and approved in Greenhouse, a corresponding job posting is automatically created in Lever with matching title, department, location, and hiring team assignments, keeping both ATS systems synchronized on active requisitions.
Bi-Directional Candidate Offer Status Sync
Lever Greenhouse Monitors offer status changes in both Lever and Greenhouse and propagates the updated status to the counterpart system, so compensation teams and hiring managers always see consistent offer data regardless of which ATS they're in.
Lever Rejection to Greenhouse Candidate Disposition Sync
Lever Greenhouse When a candidate is rejected in Lever with a disposition reason, the workflow automatically locates the matching Greenhouse record and updates it with the rejection status and reason code, then optionally triggers a candidate notification email.
How Tray.ai makes this work
Lever + Greenhouse runs on the full Tray.ai platform
Intelligent iPaaS
Integrate and automate across 700+ connectors with visual workflows, error handling, and observability.
Learn more →Agent Builder
Build AI agents that read, write, and take action in Lever and Greenhouse — with guardrails, audit, and human-in-the-loop.
Learn more →Agent Gateway for MCP
Expose Lever + Greenhouse actions as governed MCP tools — observable, rate-limited, authenticated.
Learn more →Ship your Lever + Greenhouse integration.
We'll walk through the exact integration you're imagining in a tailored demo.