Skip to content
ERP ⇄ Human resources

Infor WMS to Lever integration — real-time, two-way sync

Keep Infor WMS 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 WMS and Lever

Sync the workers, org structure, and cost centers that Infor WMS 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 WMS 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 Locations, Shipments, Appointments, Items in Infor WMS with Stages, Feedback, Interviews, Notes and Contacts 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 WMS 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 Send shipment confirmations and tracking numbers back to the order system when the WMS ships
  • 02 Mirror ASN and receipt data into procurement so buyers see received quantities without logging into the WMS
  • 03 Consolidate Feedback, Interviews, and Notes into a warehouse for interviewer scorecard and time-to-fill reporting.
  • 04 Write enriched Sources, Tags, and Contact data back onto Opportunities from an outbound sourcing pipeline.

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 WMS 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 WMS pointed at the right people.

Where Lever runs payroll: labor cost in the books

Pay and compensation data from Lever posts into Infor WMS as labor cost, so finance sees workforce spend without re-entering it by hand.

What you can sync between Infor WMS 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 WMS objects Lever objects How this pairing syncs
Shipment Orders Outbound orders arrive from the ERP or OMS for allocation and picking. Feedback Interview feedback and scorecard forms attached to Opportunities; created via POST /opportunities/:id/feedback and consolidated into a warehouse for interviewer analytics. Shipment Orders is specific to Infor WMS and Feedback to Lever — each maps to any object or custom field on the other side.
Waves Wave assignments group orders for fulfillment and can be reported outward. Interviews Scheduled interview panel events with times and interviewers; read for scheduling reporting and time-to-hire metrics, and creatable via the panels endpoint. Waves is specific to Infor WMS and Interviews to Lever — each maps to any object or custom field on the other side.
Tasks Warehouse task data supports labor and productivity reporting in BI tools. Notes and Contacts Free-text Notes on Opportunities plus the underlying Contact (person) that dedupes multiple Opportunities; notes are posted via POST /opportunities/:id/notes and contact-level tags, sources, and links can be added back for attribution. Tasks is specific to Infor WMS and Notes and Contacts to Lever — each maps to any object or custom field on the other side.
Locations Bin and zone definitions scope inventory records during mapping. 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. Locations is specific to Infor WMS and Opportunities to Lever — each maps to any object or custom field on the other side.
Shipments Ship confirmations and tracking references flow back to the order source system. 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. Shipments is specific to Infor WMS and Postings to Lever — each maps to any object or custom field on the other side.
Appointments Dock appointment data coordinates carriers and yard operations with external schedules. 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. Appointments is specific to Infor WMS and Requisitions to Lever — each maps to any object or custom field on the other side.

How changes propagate between Infor WMS 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 WMS Lever Sub-second propagation

DetectionInfor WMS notifies Stacksync of record changes through webhook events. ION event publishing or scheduled polling of API endpoints.

DeliveryEach detected change is written to Lever through its API, with automatic retries and rate-limit backoff.

Lever Infor WMS 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 WMS through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Infor WMS: Subject to Infor ION API gateway throttling policies.
  • 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 WMS ⇄ Lever

Connect Infor WMS and Lever for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Infor WMS–Lever connection.

Real-time

Two-way sync

Changes in Infor WMS or Lever instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Infor WMS 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 WMS or Lever record.

Observability

Monitoring

Track your Infor WMS ⇄ 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 WMS and Lever.

How the Infor WMS and Lever connectors work

Infor WMS

Integration surface
REST API via the Infor OS / ION API gateway (cloud deployments run inside Infor CloudSuite)
Authentication
OAuth 2.0 via Infor OS
Change detection
ION event publishing or scheduled polling of API endpoints
Capabilities
read · write · webhooks
Rate limits
Subject to Infor ION API gateway throttling policies

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.
Lever setup guide
How it works

How to connect Infor WMS 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.

  1. 01

    Connect your apps

    Authenticate Infor WMS 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.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Infor WMS connected
    Lever connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Infor WMS 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Infor WMS ⇄ Lever
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Infor WMS Lever
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Infor WMS and Lever integration FAQ

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.

Learn more about security
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:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 392 integrations available for Infor WMS and Lever.

Popular · 7 of 392
All Infor WMS integrations All Lever integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own