Two-way sync
Changes in Lever or Monday instantly reflect in both systems. No stale data, no manual imports.
Keep Lever and Monday in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Each tool in Monday keeps its own list of who can use it: users, members, or agents, along with the team they sit on and whether they are still active. Lever is the authoritative record of the same people as employees, with their department, manager, and employment status. When those two are connected only by manual account admin or a periodic export, the work tools drift: new hires wait days for access, team and manager changes never catch up, and people who have left keep standing accounts.
Stacksync syncs Boards, Items, Subitems, Column values in Monday with Requisitions, Offers, Users, Stages in Lever bi-directionally and in real time. A person added, moved, or offboarded in Lever creates or updates the matching user in Monday within seconds, with field-level mapping and conflict resolution in place of spreadsheets and one-off account changes. Where Monday captures details of its own, such as a corrected contact or a login identity, those can flow back to Lever in whichever direction you configure.
Because the sync is field-level, each system keeps its own extras; only the shared facts, who a person is, which team they belong to, and whether their access should be on, are held in agreement.
When someone changes teams or managers in Lever, the queues, ownership, or approvals in Monday update to match, so work reaches whoever holds the role now.
A new hire recorded in Lever creates the matching user in Monday with the right team and manager already set, so people can start working without waiting on a provisioning ticket.
When someone is marked as leaving in Lever, the matching account in Monday is deactivated or flagged, so departures do not leave open access behind.
Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.
| Lever objects | Monday objects | How this pairing syncs | |
|---|---|---|---|
| Users Lever team members (recruiters, hiring managers) with configurable roles; can be created via POST /users, deactivated, and reactivated through the API. | Users Account members referenced by people columns; read to resolve owner and assignee IDs to names and emails. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Opportunities The core pipeline record for a candidate applying to a role; replaced the deprecated Candidates endpoint. Created via POST /opportunities and updated (stage, archive, links, tags, sources, files) through the API, and synced two-way with a database or HRIS. | Updates Comment and activity threads attached to items; read out into a database for reporting or written back as notes. | Opportunities is specific to Lever and Updates to Monday — each maps to any object or custom field on the other side. | |
| Postings Job posting records with categories, apply URLs, workplace type, and requisition codes. Can be created via POST /postings and read into a warehouse for open-role reporting. | Workspaces Top-level containers that hold boards; used to scope which boards a given sync covers. | Postings is specific to Lever and Workspaces to Monday — each maps to any object or custom field on the other side. | |
| Requisitions Headcount/requisition records with custom requisition fields, tied to Postings; read via GET /requisitions and synced to an HRIS to reconcile approved headcount against open roles. | Boards Table-like containers that hold items; each board maps to a synced table, and its columns define the field mapping. | Requisitions is specific to Lever and Boards to Monday — each maps to any object or custom field on the other side. | |
| Offers Offer records attached to an Opportunity with status and offer-form fields; exposed read-only through GET /opportunities/:id/offers, so they sync outbound to an HRIS or onboarding system when a candidate reaches the offer stage. | Items Rows within a board and the primary record; synced two-way and created, updated, archived, or deleted via GraphQL mutations. | Offers is specific to Lever and Items to Monday — each maps to any object or custom field on the other side. | |
| Stages Pipeline stage definitions that Opportunities move through; read to model funnel state and stage transitions in a database. | Subitems Nested rows under items, stored on a separate hidden board; synced as a child table linked to the parent item. | Stages is specific to Lever and Subitems to Monday — each maps to any object or custom field on the other side. |
Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.
DetectionLever notifies Stacksync of record changes through webhook events. Webhooks for candidate and application lifecycle events (applicationCreated, candidateStageChange, candidateArchiveStateChange, candidateHired,.
DeliveryEach detected change is written to Monday through its API, with automatic retries and rate-limit backoff.
DetectionMonday notifies Stacksync of record changes through webhook events. Board-scoped webhooks (create_item, change_column_value, item_deleted, and similar) for real-time events.
DeliveryEach detected change is written to Lever through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Lever–Monday connection.
Changes in Lever or Monday instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Lever or Monday data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Lever or Monday record.
Track your Lever ⇄ Monday sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Lever and Monday.
Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.
Authenticate Lever and Monday with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the Lever and Monday objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Lever and Monday: authenticate both systems, choose the objects to sync (such as Lever's Users and Opportunities), map fields visually, and changes propagate both ways in milliseconds — no code required.
On the Monday side: Boards, Items, Subitems, Column values, plus custom fields where Monday exposes them. On the Lever side: Requisitions, Offers, Users, Stages. Stacksync auto-detects both schemas and converts types between the two systems.
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
Common patterns for Lever and Monday: Where Monday routes or assigns work by person: assignments follow the org; Onboarding: access ready on day one; Offboarding: no standing access after a departure. When someone changes teams or managers in Lever, the queues, ownership, or approvals in Monday update to match, so work reaches whoever holds the role now.
Lever: REST Data API (api.lever.co/v1). Authentication: API key over HTTP Basic auth (key as username, blank password) for internal integrations, or OAuth 2.0 with 1-hour access tokens for partner integrations (auth.lever.co). Monday: GraphQL API (single endpoint, api.monday.com/v2). Authentication: OAuth 2.0 for installed apps, or a per-user personal API token (admin/member scope); a date-based API version is sent via request header. Stacksync manages authentication, retries, and rate limits on both sides.
Monday: Rate limiting is complexity-based, not request-count based: each query has a complexity cost capped at 5M per call and ~10M per minute per user token (1M on trial/free). Lever: List endpoints use cursor-based pagination at up to 100 records per page; incremental syncs rely on created_at and updated_at range filters. Stacksync's field mapping accounts for these differences between Lever and Monday without custom code.
As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 511 integrations available for Lever and Monday.