Real-time
Two-way sync
Changes in Infor LN or Lever instantly reflect in both systems. No stale data, no manual imports.
ERP ⇄ Human resources
Infor LN to Lever integration — real-time, two-way sync
Keep Infor LN and Lever in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
- SOC 2 and 6 other compliance frameworks
- POC with real engineers in minutes
Adopted by fast-scaling companies moving mission-critical data in real time
Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Infor LN and Lever
Sync the workers, org structure, and cost centers that Infor LN and Lever share in real time, so the people Lever manages stay current in the system that runs finance and operations.
Lever is the system of record for people: who was hired, which department and location they sit in, who they report to, and how they are paid. Infor LN runs finance and operations, and much of what it does depends on that same information, from booking labor cost to approving an expense report to staffing a project. Where the two are bridged by re-keying or an overnight file, each side spends the day out of step, with new hires missing from the systems they need and leavers still active where they should not be.
Stacksync syncs Bills of material, Business partners, Sales orders, Purchase orders in Infor LN with Users, Stages, Feedback, Interviews in Lever field by field, in real time, and in both directions. You decide which system owns which fields, so the people side stays authoritative for worker data while Infor LN keeps its own accounting and operational detail, and every change made in one is reflected in the other within seconds instead of at the next batch run.
Common use cases
- 01 Run a two-way sync of business partners between LN and a CRM so sales and manufacturing share account data.
- 02 Keep inventory positions aligned between LN and distribution or aftermarket service systems.
- 03 Write enriched Sources, Tags, and Contact data back onto Opportunities from an outbound sourcing pipeline.
- 04 Two-way sync Opportunities and their Stages between Lever and a Postgres database so recruiting ops and analysts query the pipeline in SQL while recruiters keep working in Lever.
Common sync patterns
One org structure
Departments, cost centers, and locations that both systems reference stay in agreement, so labor cost, approvals, and reporting in Infor LN roll up to the same structure Lever maintains.
Reporting lines drive approvals
Manager and reporting-hierarchy changes in Lever keep expense and purchase approval chains in Infor LN pointed at the right people.
Where Lever runs payroll: labor cost in the books
Pay and compensation data from Lever posts into Infor LN as labor cost, so finance sees workforce spend without re-entering it by hand.
What you can sync between Infor LN and Lever
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.
| Infor LN objects | Lever objects | How this pairing syncs | |
|---|---|---|---|
| Production orders Shop-floor work orders synced with MES for execution visibility. | 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. | Production orders is specific to Infor LN and Requisitions to Lever — each maps to any object or custom field on the other side. | |
| Warehouse / inventory Stock positions exposed so external channels reflect real availability. | 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. | Warehouse / inventory is specific to Infor LN and Offers to Lever — each maps to any object or custom field on the other side. | |
| Projects Project structures used in engineer-to-order manufacturing scenarios. | Users Lever team members (recruiters, hiring managers) with configurable roles; can be created via POST /users, deactivated, and reactivated through the API. | Projects is specific to Infor LN and Users to Lever — each maps to any object or custom field on the other side. | |
| Service orders Aftermarket service documents synced with field service tools. | Stages Pipeline stage definitions that Opportunities move through; read to model funnel state and stage transitions in a database. | Service orders is specific to Infor LN and Stages to Lever — each maps to any object or custom field on the other side. | |
| Items Manufacturing item masters synced to PLM, MES, and commerce systems. | Feedback Interview feedback and scorecard forms attached to Opportunities; created via POST /opportunities/:id/feedback and consolidated into a warehouse for interviewer analytics. | Items is specific to Infor LN and Feedback to Lever — each maps to any object or custom field on the other side. | |
| Bills of material Product structures shared with engineering and planning tools. | Interviews Scheduled interview panel events with times and interviewers; read for scheduling reporting and time-to-hire metrics, and creatable via the panels endpoint. | Bills of material is specific to Infor LN and Interviews to Lever — each maps to any object or custom field on the other side. |
How changes propagate between Infor LN and Lever
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.
Infor LN Lever Interval-based propagation
DetectionStacksync polls Infor LN for changes on an incremental schedule, reading only records changed since the previous pass. Event-style BOD publications through Infor ION where configured.
DeliveryEach detected change is written to Lever through its API, with automatic retries and rate-limit backoff.
Lever Infor LN Sub-second propagation
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 Infor LN through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Infor LN: Subject to the ION API gateway's tenant rate limits in cloud deployments.
- Lever: 10 requests/second per API key with a token-bucket burst to ~20/s; POSTs that create candidates/applications are throttled to roughly 2/second. Sustained overage returns 429 with Retry-After. List endpoints are cursor-paginated at up to 100 records per page.
What ships with Infor LN ⇄ Lever
Connect Infor LN and Lever for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Infor LN–Lever connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Infor LN or Lever data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
At scale
Event queues
Handle millions of events per minute without losing a single Infor LN or Lever record.
Observability
Monitoring
Track your Infor LN ⇄ Lever sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Infor LN and Lever.
How the Infor LN and Lever connectors work
Infor LN
- Integration surface
- SOAP and REST web services, with standardized BOD exchange through Infor ION in Infor OS deployments
- Authentication
- OAuth 2.0 via the ION API gateway in cloud deployments; application credentials on premises
- Change detection
- Event-style BOD publications through Infor ION where configured; otherwise polling
- Capabilities
- read · write
- Rate limits
- Subject to the ION API gateway's tenant rate limits in cloud deployments.
Lever
- Integration surface
- 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)
- Change detection
- Webhooks for candidate and application lifecycle events (applicationCreated, candidateStageChange, candidateArchiveStateChange, candidateHired, interview created/updated/deleted), plus incremental polling via created_at and updated_at range filters on Opportunities
- Capabilities
- read · write · webhooks
- Rate limits
- 10 requests/second per API key with a token-bucket burst to ~20/s; POSTs that create candidates/applications are throttled to roughly 2/second. Sustained overage returns 429 with Retry-After. List endpoints are cursor-paginated at up to 100 records per page.
How it works
How to connect Infor LN to Lever — three steps, no code
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.
- 01
Connect your apps
Authenticate Infor LN and Lever with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Infor LN
connected
Lever
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Infor LN and Lever 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.
objects · Infor LN ⇄ LeverCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Infor LN LeverCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Infor LN and Lever integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Infor LN and Lever: authenticate both systems, choose the objects to sync (such as Infor LN's Production orders and Warehouse / inventory), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
On the Infor LN side: Bills of material, Business partners, Sales orders, Purchase orders, plus custom fields where Infor LN exposes them. On the Lever side: Users, Stages, Feedback, Interviews. 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 Infor LN and Lever: One org structure; Reporting lines drive approvals; Where Lever runs payroll: labor cost in the books. Departments, cost centers, and locations that both systems reference stay in agreement, so labor cost, approvals, and reporting in Infor LN roll up to the same structure Lever maintains.
-
Infor LN: SOAP and REST web services, with standardized BOD exchange through Infor ION in Infor OS deployments. Authentication: OAuth 2.0 via the ION API gateway in cloud deployments; application credentials on premises. 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). Stacksync manages authentication, retries, and rate limits on both sides.
-
Infor LN: LN's multi-company and multi-site structure partitions core data, so syncs must be scoped to the right company and site context. Lever: The /candidates endpoint is deprecated; the current model is Opportunities, where one person (Contact) can hold multiple Opportunities across postings, so deduplication keys on the Contact. Stacksync's field mapping accounts for these differences between Infor LN and Lever without custom code.
SECURITY
Security teams trust Stacksync
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.
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS
SSO & SCIM
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Alerts
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Secure connection options
Securely connects to your systems with:
Related integrations
Every pair below is a real-time, two-way sync. Search all 505 integrations available for Infor LN and Lever.
Popular · 6 of 505
-
Infor LN ⇄ Paylocity -
Infor LN ⇄ Ukg Ready -
Infor LN ⇄ BambooHR -
Infor LN ⇄ Success Factors -
Lever ⇄ Cin7 - Lever ⇄ DEAR Inventory
No integrations match .
