# Connect Lever to Greenhouse > Sync candidate data, job postings, and hiring workflows between Lever and Greenhouse to cut manual work and hire faster. **Canonical page:** https://tray.ai/connectors/lever-greenhouse-integrations/ **Lever connector:** https://tray.ai/connectors/lever-integrations/ **Lever documentation:** https://tray.ai/documentation/connectors/service/lever **Greenhouse connector:** https://tray.ai/connectors/greenhouse-integrations/ **Greenhouse documentation:** https://tray.ai/documentation/connectors/service/greenhouse ## Overview 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. ## Use cases ### 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 ### 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 ### 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 ### 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 ### 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 ### 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 ### Rejected Candidate and Disposition Sync When a candidate is rejected in Lever, the corresponding Greenhouse record is automatically updated with the rejection reason and disposition status, and vice versa. This prevents rejected candidates from staying active in one system while being closed in the other — a situation that causes compliance issues and skews pipeline metrics. Automated rejection notifications can also be triggered to candidates based on disposition events in either ATS. - Keeps candidate disposition statuses consistent to support compliance and reporting accuracy - Prevents accidental re-engagement of candidates who have already been rejected - Automates candidate rejection notifications to improve candidate experience ## Templates ### New Lever Candidate to Greenhouse Profile Creator 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. Connectors used: Lever, Greenhouse ### Greenhouse Candidate Stage Update to Lever Stage Sync 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. Connectors used: Lever, Greenhouse ### Lever Interview Feedback to Greenhouse Scorecard Sync 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. Connectors used: Lever, Greenhouse ### Greenhouse Job Opening to Lever Requisition Creator 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. Connectors used: Lever, Greenhouse ### Bi-Directional Candidate Offer Status Sync 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. Connectors used: Lever, Greenhouse ### Lever Rejection to Greenhouse Candidate Disposition Sync 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. Connectors used: Lever, Greenhouse ## Challenges Tray.ai solves ### 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. ### 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. ### 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. ### Handling API Rate Limits During High-Volume Recruiting Periods During peak hiring seasons, the volume of candidate creates, updates, and stage changes can exceed the API rate limits of both Lever and Greenhouse, causing integration failures and data gaps that are hard to detect and painful to fix manually. **How Tray.ai helps:** tray.ai includes built-in rate limit handling, automatic retry logic with exponential backoff, and queue-based processing that smooths out high-volume bursts across both APIs. Failed calls are logged and retried automatically, so no candidate updates are silently dropped during peak recruiting cycles. ### Maintaining Data Lineage and Audit Trails Across Both Systems Compliance and legal teams often need a full audit trail of when candidate data was created, modified, or deleted, and which system did it. When data flows between two ATS platforms automatically, reconstructing the history of a record for GDPR, CCPA, or internal compliance purposes gets complicated. **How Tray.ai helps:** tray.ai logs every workflow execution — input data, transformation steps, API responses, and timestamps — giving compliance teams a complete audit trail of every data movement between Lever and Greenhouse. Those logs can be exported or forwarded to a data warehouse or SIEM system for long-term retention. ## Learn more - Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/ - Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/ - Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/ - Book a demo: https://tray.ai/contact/