Real-time
Two-way sync
Changes in Epicor ERP or Onelogin instantly reflect in both systems. No stale data, no manual imports.
ERP ⇄ Security and identity
Epicor ERP to Onelogin integration — real-time, two-way sync
Keep Epicor ERP and Onelogin 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 Epicor ERP and Onelogin
Keep the employee, group, and account records that Epicor ERP and Onelogin share aligned in real time, so a person added, moved, or offboarded in one system shows up correctly in the other within seconds.
An ERP and an identity system describe the same workforce from two angles. Epicor ERP holds the authoritative record of who works at the company, and often their department, title, manager, and cost center. Onelogin controls the accounts, groups, and access those same people use every day. When the two aren't connected, every hire, transfer, and departure has to be keyed twice, and the window between someone leaving in Epicor ERP and their account still being active in Onelogin is a real security exposure.
Stacksync syncs Bills of materials, Customers, Suppliers, Parts in Epicor ERP with Mappings (mapping rules), Events, Authentication factors (MFA), Custom user fields in Onelogin in real time, with field-level mapping and conflict resolution in place of CSV exports and nightly jobs. A new hire, a department change, or a termination propagates within seconds, and where you want changes to flow both ways — the ERP's org data into the directory, account status back into the ERP — the same mapping handles it.
That matters most at offboarding and audit time. When the directory reflects the ERP's current headcount and org structure, disabling access no longer depends on someone remembering to update a second system, and access reviews start from a roster both sides already agree on.
Common use cases
- 01 Sync shipment confirmations out to commerce platforms and customer portals as jobs complete.
- 02 Sync Epicor customers and AR invoices into a CRM so sales sees order history and credit status without ERP logins.
- 03 Two-way sync Users between OneLogin and an HRIS or Postgres so new hires, attribute changes, and terminations provision and deprovision SSO accounts automatically.
- 04 Read the OneLogin Events audit log into a warehouse or SIEM for login analytics, access reviews, and SOC 2 audit evidence.
Common sync patterns
Disable access at offboarding
When a person is marked terminated or inactive in one system, the matching account is disabled in the other within seconds, closing the gap that leaves ex-employees with live access.
Keep profile attributes current
A name, email, title, manager, or department corrected in either system updates the other, so directory entries and employee records don't drift apart.
Align group and department membership
When someone changes team or department, their group or organizational-unit membership updates to match, keeping access tied to their current role.
What you can sync between Epicor ERP and Onelogin
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.
| Epicor ERP objects | Onelogin objects | How this pairing syncs | |
|---|---|---|---|
| Sales orders Created from won CRM opportunities; status and line changes sync back out. | Authentication factors (MFA) Per-user registered MFA factors; enrolled, verified, and removed through the MFA API for lifecycle and security workflows. | Sales orders is specific to Epicor ERP and Authentication factors (MFA) to Onelogin — each maps to any object or custom field on the other side. | |
| Purchase orders Synced with procurement systems and matched against receipts. | Custom user fields Account-level custom attributes on the User record; read and written alongside the standard user profile fields. | Purchase orders is specific to Epicor ERP and Custom user fields to Onelogin — each maps to any object or custom field on the other side. | |
| Jobs Production jobs whose status feeds shop-floor dashboards and delivery-date updates. | Users User accounts (email, username, custom attributes, status, roles); full CRUD via the v2 Users API - create, update, delete, set password, lock/unlock, and add or remove role assignments. | Jobs is specific to Epicor ERP and Users to Onelogin — each maps to any object or custom field on the other side. | |
| Quotes Estimates that pair with CRM opportunities during the sales cycle. | Roles Roles that bundle app access; created, updated, and deleted via the Roles API, with users, admins, and apps assigned to each role. | Quotes is specific to Epicor ERP and Roles to Onelogin — each maps to any object or custom field on the other side. | |
| AR invoices Billing records surfaced in CRM or finance tools for collections visibility. | Apps (app instances) Connected SAML/OIDC application configs on the account; create, update, delete, and assign to users and roles - the writable app catalog. | AR invoices is specific to Epicor ERP and Apps (app instances) to Onelogin — each maps to any object or custom field on the other side. | |
| Shipments Fulfillment confirmations synced to customer portals and commerce systems. | Groups Account groups used for mapping and reporting; listed and read through the API, which has no create or update endpoint, so groups are read-only. | Shipments is specific to Epicor ERP and Groups to Onelogin — each maps to any object or custom field on the other side. |
How changes propagate between Epicor ERP and Onelogin
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.
Epicor ERP Onelogin Interval-based propagation
DetectionStacksync polls Epicor ERP for changes on an incremental schedule, reading only records changed since the previous pass. Polling on change-date fields.
DeliveryEach detected change is written to Onelogin through its API, with automatic retries and rate-limit backoff.
Onelogin Epicor ERP Sub-second propagation
DetectionOnelogin notifies Stacksync of record changes through webhook events. Event Webhook (Event Broadcaster) posts batches of Event objects to a registered endpoint in near real time.
DeliveryEach detected change is written to Epicor ERP through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Epicor ERP: Subject to the platform's API rate limits and per-tenant throttling on Kinetic cloud deployments.
- Onelogin: Account-level limit of 5,000 API calls per hour shared across all access tokens; responses carry X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset, over-limit calls return HTTP 429, and the count resets each hour. Paid plans can request an increase.
What ships with Epicor ERP ⇄ Onelogin
Connect Epicor ERP and Onelogin for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Epicor ERP–Onelogin connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Epicor ERP or Onelogin 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 Epicor ERP or Onelogin record.
Observability
Monitoring
Track your Epicor ERP ⇄ Onelogin sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Epicor ERP and Onelogin.
How the Epicor ERP and Onelogin connectors work
Epicor ERP
- Integration surface
- REST API (OData) over Epicor business objects, plus BAQ (Business Activity Query) endpoints
- Authentication
- API key combined with basic or token authentication, depending on version and deployment
- Change detection
- Polling on change-date fields; outbound calls can be wired through BPM directives, but there is no standard webhook subscription surface
- Capabilities
- read · write
- Rate limits
- Subject to the platform's API rate limits and per-tenant throttling on Kinetic cloud deployments
Onelogin
- Integration surface
- OneLogin API (REST, v1 and v2 resource endpoints on <subdomain>.onelogin.com) plus the Event Webhook (Event Broadcaster) for event delivery
- Authentication
- OAuth 2.0 client credentials - an admin generates an API credential pair (client_id + client_secret) in the OneLogin portal and exchanges it at POST /auth/oauth2/v2/token for a bearer access token sent on every call; each credential carries a scope (Manage all, Manage users, Read users, etc.) that governs read vs write.
- Change detection
- Event Webhook (Event Broadcaster) posts batches of Event objects to a registered endpoint in near real time; the Events API also supports polling with since/until time filters and pagination for historical backfill.
- Capabilities
- read · write · webhooks
- Rate limits
- Account-level limit of 5,000 API calls per hour shared across all access tokens; responses carry X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset, over-limit calls return HTTP 429, and the count resets each hour. Paid plans can request an increase.
How it works
How to connect Epicor ERP to Onelogin — 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 Epicor ERP and Onelogin with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Epicor ERP
connected
Onelogin
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Epicor ERP and Onelogin 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 · Epicor ERP ⇄ OneloginCustomers 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.
Epicor ERP OneloginCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Epicor ERP and Onelogin integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Epicor ERP and Onelogin: authenticate both systems, choose the objects to sync (such as Epicor ERP's Sales orders and Purchase orders), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Epicor ERP and Onelogin connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Epicor ERP–Onelogin integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Epicor ERP and Onelogin. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Epicor ERP: Polling on change-date fields; outbound calls can be wired through BPM directives, but there is no standard webhook subscription surface. On Onelogin: Event Webhook (Event Broadcaster) posts batches of Event objects to a registered endpoint in near real time; the Events API also supports polling with since/until time filters and pagination for historical backfill. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Epicor ERP side: Bills of materials, Customers, Suppliers, Parts, plus custom fields where Epicor ERP exposes them. On the Onelogin side: Mappings (mapping rules), Events, Authentication factors (MFA), Custom user fields. 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.
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 508 integrations available for Epicor ERP and Onelogin.
Popular · 6 of 508
-
Epicor ERP ⇄ Jumpcloud -
Epicor ERP ⇄ Active Directory - Epicor ERP ⇄ Azure Active Directory
-
Epicor ERP ⇄ Okta -
Onelogin ⇄ Extensiv (3PL Central) -
Onelogin ⇄ Fishbowl Manufacturing
No integrations match .
