Real-time
Two-way sync
Changes in Onelogin or Servicemax instantly reflect in both systems. No stale data, no manual imports.
Security and identity ⇄ Business productivity
Onelogin to Servicemax integration — real-time, two-way sync
Keep Onelogin and Servicemax 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 Servicemax
Keep the users, groups, and profile details that Servicemax and Onelogin share consistent in real time, so who can work in Servicemax always matches who your directory in Onelogin says belongs there.
Onelogin is where a company records who its people are: their accounts, the groups and roles they hold, and the attributes attached to each one. Servicemax is where a slice of those same people do their work, as agents, members, or seats, and every one of them needs a matching account with the right access. When a directory and a productivity tool are maintained by hand, someone added, moved, or offboarded in one becomes a stale entry in the other within the hour.
Stacksync syncs Work Orders, Work Details, Installed Products, Service Contracts in Servicemax with Users, Roles, Apps (app instances), Groups in Onelogin bi-directionally and in real time. A user created, renamed, moved between groups, or deactivated in either system updates the matching record in the other within seconds, with field-level mapping and conflict resolution in place of CSV uploads and nightly IT batch jobs.
That matters most at the edges of employment. When both systems agree on who has an account, which groups they belong to, and whether they are still active, granting access on day one and revoking it on the last day stops being a manual checklist that trails the directory.
Common use cases
- 01 Consolidate Service Contracts and entitlement data into a warehouse for renewal forecasting and SLA compliance dashboards.
- 02 Mirror Accounts and Contacts between ServiceMax and the CRM system of record so customer and site data stays consistent.
- 03 Read the OneLogin Events audit log into a warehouse or SIEM for login analytics, access reviews, and SOC 2 audit evidence.
- 04 Keep Role membership aligned with application or database entitlement tables so each role's assigned users match who should hold that access.
Common sync patterns
One record per person
People matched across both systems on email or an external ID stay linked, so every account and action in Servicemax ties back to the right identity in Onelogin.
Provision access when someone joins
A user added to Onelogin, or moved into a group inside it, gets the matching account or membership created in Servicemax, so a new hire can start working without a separate setup ticket.
Close access when someone leaves
When a user is disabled or removed in Onelogin, their account in Servicemax is deactivated in step, so offboarding shuts down access everywhere instead of leaving a live login behind.
What you can sync between Onelogin and Servicemax
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 | Servicemax objects | How this pairing syncs | |
|---|---|---|---|
| Mappings (mapping rules) Attribute-driven rules that assign roles and app access; full CRUD via the Mappings API, then reapplied across matching users. | Accounts Standard Salesforce Account; customer and site company records; synced two-way with CRM and database customer tables. | Mappings (mapping rules) is specific to Onelogin and Accounts to Servicemax — 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. | Contacts Standard Salesforce Contact; people linked to Accounts and service sites; synced with CRM and support person records. | Events is specific to Onelogin and Contacts to Servicemax — 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. | Cases Standard Salesforce Case; support records that often precede a Work Order; synced with help desk tools and reporting databases. | Authentication factors (MFA) is specific to Onelogin and Cases to Servicemax — 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. | Products Standard Salesforce Product2; catalog of serviceable products and spare parts referenced by Installed Products and Work Details. | Custom user fields is specific to Onelogin and Products to Servicemax — each maps to any object or custom field on the other side. | |
| 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. | Work Orders SVMXC__Service_Order__c; the core field-service job record for install, repair, and maintenance; synced two-way with databases and pushed to ERPs at close. | Users is specific to Onelogin and Work Orders to Servicemax — each maps to any object or custom field on the other side. | |
| Roles Roles that bundle app access; created, updated, and deleted via the Roles API, with users, admins, and apps assigned to each role. | Work Details SVMXC__Service_Order_Line__c; line items on a Work Order for labor, parts used, and expenses; read out for billing or written back with usage. | Roles is specific to Onelogin and Work Details to Servicemax — each maps to any object or custom field on the other side. |
How changes propagate between Onelogin and Servicemax
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 Servicemax 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 Servicemax through its API, with automatic retries and rate-limit backoff.
Servicemax Onelogin Sub-second propagation
DetectionChanges in Servicemax are captured at the source via change data capture — no polling loop against its API. Salesforce mechanisms — Apex triggers or polling on SystemModstamp/LastModifiedDate, with Change Data Capture / Platform Events available per object.
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.
- Servicemax: Governed by the Salesforce org-wide daily API request allocation, shared across all integrations and scaled by edition and license count.
What ships with Onelogin ⇄ Servicemax
Connect Onelogin and Servicemax for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Onelogin–Servicemax connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Onelogin or Servicemax 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 Servicemax record.
Observability
Monitoring
Track your Onelogin ⇄ Servicemax 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 Servicemax.
How the Onelogin and Servicemax 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.
Servicemax
- Integration surface
- Salesforce REST, SOAP, and Bulk APIs (ServiceMax is a managed package on the Salesforce platform)
- Authentication
- Salesforce OAuth login via a user with API access; the connecting profile needs object and field permissions on ServiceMax's SVMXC__ objects
- Change detection
- Salesforce mechanisms — Apex triggers or polling on SystemModstamp/LastModifiedDate, with Change Data Capture / Platform Events available per object where enabled
- Capabilities
- read · write · CDC
- Rate limits
- Governed by the Salesforce org-wide daily API request allocation, shared across all integrations and scaled by edition and license count
How it works
How to connect Onelogin to Servicemax — 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 Onelogin and Servicemax with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Onelogin
connected
Servicemax
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Onelogin and Servicemax 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 · Onelogin ⇄ ServicemaxCustomers 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.
Onelogin ServicemaxCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Onelogin and Servicemax integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Onelogin and Servicemax: authenticate both systems, choose the objects to sync (such as Onelogin's Mappings (mapping rules) and Events), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Onelogin: 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. Servicemax: Salesforce REST, SOAP, and Bulk APIs (ServiceMax is a managed package on the Salesforce platform). Authentication: Salesforce OAuth login via a user with API access; the connecting profile needs object and field permissions on ServiceMax's SVMXC__ objects. Stacksync manages authentication, retries, and rate limits on both sides.
-
Servicemax: Polling orders incremental changes by each object's SystemModstamp or LastModifiedDate; objects without a modified timestamp or API write access cannot sync incrementally. Onelogin: Auth is OAuth 2.0 client credentials - a client_id/client_secret pair exchanged at /auth/oauth2/v2/token for a bearer token; the credential's scope (e.g. Manage users vs Read) decides what it can write. Stacksync's field mapping accounts for these differences between Onelogin and Servicemax without custom code.
-
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Onelogin and Servicemax records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Onelogin and Servicemax connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Onelogin–Servicemax integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Onelogin and Servicemax. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
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 509 integrations available for Onelogin and Servicemax.
Popular · 8 of 509
-
Onelogin ⇄ Gainsight -
Onelogin ⇄ Ironclad -
Onelogin ⇄ Adobe Sign -
Onelogin ⇄ Asana -
Servicemax ⇄ Okta -
Servicemax ⇄ Auth0 -
Servicemax ⇄ Jumpcloud -
Servicemax ⇄ Active Directory
No integrations match .
