Skip to content
Security and identity ⇄ ERP

Onelogin to SAP Business One integration — real-time, two-way sync

Keep Onelogin and SAP Business One 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 Onelogin and SAP Business One

Keep the employee, group, and account records that SAP Business One 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. SAP Business One 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 SAP Business One and their account still being active in Onelogin is a real security exposure.

Stacksync syncs Items, Sales Orders, A/R Invoices, Purchase Orders in SAP Business One with Groups, Mappings (mapping rules), Events, Authentication factors (MFA) 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 Two-way sync of business partners between SAP Business One and a CRM so sales edits and finance records converge on one customer master.
  • 02 Create sales orders in Business One from e-commerce platforms and sync delivery and invoice status back to the storefront.
  • 03 Keep Role membership aligned with application or database entitlement tables so each role's assigned users match who should hold that access.
  • 04 Read Users, Apps, and Groups into a database for identity, license, and app-assignment inventory across the OneLogin account.

Common sync patterns

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.

One roster on a shared key

People are matched across both systems on an identifier you choose, such as work email or employee ID, so there is a single accurate list of who is active.

What you can sync between Onelogin and SAP Business One

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.

Onelogin objects SAP Business One objects How this pairing syncs
Apps (app instances) Connected SAML/OIDC application configs on the account; create, update, delete, and assign to users and roles - the writable app catalog. Activities CRM-style tasks and interactions aligned with external sales tools. Apps (app instances) is specific to Onelogin and Activities to SAP Business One — each maps to any object or custom field on the other side.
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. Business Partners Combined customer, vendor, and lead master records; the anchor object for most syncs. Groups is specific to Onelogin and Business Partners to SAP Business One — each maps to any object or custom field on the other side.
Mappings (mapping rules) Attribute-driven rules that assign roles and app access; full CRUD via the Mappings API, then reapplied across matching users. Items Product master data including inventory levels, aligned with e-commerce and warehouse systems. Mappings (mapping rules) is specific to Onelogin and Items to SAP Business One — each maps to any object or custom field on the other side.
Events Audit log of every authentication and admin action; read-only, filtered by since/until, and pushed live through the Event Webhook. Sales Orders Order documents with header and line structure created from external channels. Events is specific to Onelogin and Sales Orders to SAP Business One — each maps to any object or custom field on the other side.
Authentication factors (MFA) Per-user registered MFA factors; enrolled, verified, and removed through the MFA API for lifecycle and security workflows. A/R Invoices Billing documents synced outward for CRM visibility and payment tracking. Authentication factors (MFA) is specific to Onelogin and A/R Invoices to SAP Business One — each maps to any object or custom field on the other side.
Custom user fields Account-level custom attributes on the User record; read and written alongside the standard user profile fields. Purchase Orders Procurement documents exchanged with supplier-facing tools. Custom user fields is specific to Onelogin and Purchase Orders to SAP Business One — each maps to any object or custom field on the other side.

How changes propagate between Onelogin and SAP Business One

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.

Onelogin SAP Business One 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 SAP Business One through its API, with automatic retries and rate-limit backoff.

SAP Business One Onelogin Interval-based propagation

DetectionStacksync polls SAP Business One for changes on an incremental schedule, reading only records changed since the previous pass. Polling on update timestamps.

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

Rate-limit considerations

  • 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 Onelogin ⇄ SAP Business One

Connect Onelogin and SAP Business One for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Onelogin–SAP Business One connection.

Real-time

Two-way sync

Changes in Onelogin or SAP Business One instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Onelogin or SAP Business One 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 Onelogin or SAP Business One record.

Observability

Monitoring

Track your Onelogin ⇄ SAP Business One sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Onelogin and SAP Business One.

How the Onelogin and SAP Business One connectors work

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.

SAP Business One

Integration surface
Service Layer, a REST API based on OData, plus the legacy COM-based DI API
Authentication
Session-based login with company database, username, and password against the Service Layer
Change detection
Polling on update timestamps; no general-purpose webhook mechanism on the standard surface
Capabilities
read · write
How it works

How to connect Onelogin to SAP Business One — 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 Onelogin and SAP Business One 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
    Onelogin connected
    SAP Business One connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Onelogin and SAP Business One 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 · Onelogin ⇄ SAP Business One
    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
    Onelogin SAP Business One
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Onelogin and SAP Business One 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.

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 512 integrations available for Onelogin and SAP Business One.

Popular · 8 of 512
Coworkers laughing in front of a laptop in a casual office setting

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