Skip to content
ERP ⇄ Human resources

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

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

Sync the workers, org structure, and cost centers that Infor CloudSuite 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 CloudSuite 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 Purchase orders, Invoices, Inventory balances, GL journal entries in Infor CloudSuite 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 CloudSuite 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 Sync items, customers, and orders between CloudSuite and a CRM so sales quotes against live pricing and inventory.
  • 02 Flow ecommerce orders into CloudSuite and return order status and shipment data to the storefront.
  • 03 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.
  • 04 Push Postings and Requisitions into an HRIS or warehouse to reconcile approved headcount against open roles.

Common sync patterns

Reporting lines drive approvals

Manager and reporting-hierarchy changes in Lever keep expense and purchase approval chains in Infor CloudSuite pointed at the right people.

Where Lever runs payroll: labor cost in the books

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

Where Lever is the worker system of record: one employee master

When a worker is hired, moved, or offboarded in Lever, the matching employee record in Infor CloudSuite is created, updated, or deactivated, so the business system reflects the workforce as it actually is.

What you can sync between Infor CloudSuite 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 CloudSuite objects Lever objects How this pairing syncs
GL journal entries Financial postings replicated for consolidated reporting. 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. GL journal entries is specific to Infor CloudSuite and Requisitions to Lever — each maps to any object or custom field on the other side.
Items Product and material masters synced to commerce, CRM, and planning tools. 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 is specific to Infor CloudSuite and Offers to Lever — each maps to any object or custom field on the other side.
Customers Account masters matched against CRM records in two-way syncs. Users Lever team members (recruiters, hiring managers) with configurable roles; can be created via POST /users, deactivated, and reactivated through the API. Customers is specific to Infor CloudSuite and Users to Lever — each maps to any object or custom field on the other side.
Suppliers / vendors Procurement counterparties synced with sourcing and AP tools. Stages Pipeline stage definitions that Opportunities move through; read to model funnel state and stage transitions in a database. Suppliers / vendors is specific to Infor CloudSuite and Stages to Lever — each maps to any object or custom field on the other side.
Sales orders Demand-side documents synced in from commerce channels and out for fulfillment visibility. Feedback Interview feedback and scorecard forms attached to Opportunities; created via POST /opportunities/:id/feedback and consolidated into a warehouse for interviewer analytics. Sales orders is specific to Infor CloudSuite and Feedback to Lever — each maps to any object or custom field on the other side.
Purchase orders Supply-side documents shared with procurement and supplier portals. Interviews Scheduled interview panel events with times and interviewers; read for scheduling reporting and time-to-hire metrics, and creatable via the panels endpoint. Purchase orders is specific to Infor CloudSuite and Interviews to Lever — each maps to any object or custom field on the other side.

How changes propagate between Infor CloudSuite 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 CloudSuite Lever Interval-based propagation

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

Rate-limit considerations

  • Infor CloudSuite: Subject to the ION API gateway's rate limiting policies for the tenant.
  • 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 CloudSuite ⇄ Lever

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

How the Infor CloudSuite and Lever connectors work

Infor CloudSuite

Integration surface
REST APIs exposed through the Infor ION API gateway; integration payloads are standardized as Business Object Documents (BODs)
Authentication
OAuth 2.0 via Infor OS / ION API credentials
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 rate limiting policies for the tenant.

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 CloudSuite 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 CloudSuite 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 CloudSuite connected
    Lever connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Infor CloudSuite 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 CloudSuite ⇄ 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 CloudSuite Lever
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Infor CloudSuite 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 405 integrations available for Infor CloudSuite and Lever.

Popular · 7 of 405
All Infor CloudSuite 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