Real-time
Two-way sync
Changes in Onelogin or Salesforce instantly reflect in both systems. No stale data, no manual imports.
Security and identity ⇄ CRM
Onelogin to Salesforce integration — real-time, two-way sync
Keep Onelogin and Salesforce 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 Salesforce
Keep the people Salesforce and Onelogin both track in agreement in real time: the internal users who own records in Salesforce, and the customer login accounts in Onelogin.
A CRM and an identity system usually describe different populations. Salesforce tracks customers, contacts, and the deals in motion; Onelogin governs who is allowed to sign in and what they can reach. Where the two meet is people. The reps who own records in Salesforce are the same employees Onelogin provisions and disables, and when Onelogin also runs the login accounts for your product, the customers in Salesforce are the same users Onelogin authenticates. Left unconnected, a departure in Onelogin leaves stale ownership sitting in Salesforce, and a signup in Onelogin never reaches the account it belongs to.
Stacksync syncs Custom Objects, Accounts, Contacts, Leads in Salesforce with Authentication factors (MFA), Custom user fields, Users, Roles in Onelogin in real time and in both directions, matching on email or an external ID and mapping field by field. You decide which system owns which fields, and new users, role and group changes, deactivations, and account status move within seconds instead of waiting on a quarterly access review or a manual export.
Common use cases
- 01 Trigger provisioning or billing changes in an operational database when an Opportunity moves to closed-won.
- 02 Consolidate multiple Salesforce orgs into a single database for cross-org reporting after an acquisition.
- 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
Where a closed deal should provision access: Salesforce drives Onelogin
A won or activated customer in Salesforce can create or update the corresponding user or account in Onelogin, so provisioning starts from the CRM record instead of a separate ticket.
Where Onelogin governs your workforce: CRM users kept current
New employees in Onelogin become active users in Salesforce with the right role, and group or department changes update their access and team, so the CRM's user list matches the directory without an admin re-keying it.
Deactivation and record hand-off
When someone is disabled in Onelogin, the matching user in Salesforce is deactivated too, and the accounts, contacts, and deals they owned are flagged for reassignment, so nothing goes unattended after they leave.
What you can sync between Onelogin and Salesforce
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 | Salesforce objects | How this pairing syncs | |
|---|---|---|---|
| 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. | Contacts People linked to Accounts; synced two-way with marketing, support, and warehouse person records. | Groups is specific to Onelogin and Contacts to Salesforce — 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. | Leads Unqualified prospects; often written into Salesforce from enrichment or product-signup pipelines. | Mappings (mapping rules) is specific to Onelogin and Leads to Salesforce — 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. | Opportunities Deal records with stage and amount; synced to databases for pipeline reporting and to ERPs at close. | Events is specific to Onelogin and Opportunities to Salesforce — 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 Support records; synced with help desk tools or internal databases for escalation workflows. | Authentication factors (MFA) is specific to Onelogin and Cases to Salesforce — 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. | Campaigns Marketing membership data; read out for attribution analysis in the warehouse. | Custom user fields is specific to Onelogin and Campaigns to Salesforce — 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. | Tasks and Events Activity records; usually read-only in syncs to feed activity reporting. | Users is specific to Onelogin and Tasks and Events to Salesforce — each maps to any object or custom field on the other side. |
How changes propagate between Onelogin and Salesforce
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 Salesforce 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 Salesforce through its API, with automatic retries and rate-limit backoff.
Salesforce Onelogin Sub-second propagation
DetectionChanges in Salesforce are captured at the source via change data capture — no polling loop against its API. Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting).
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.
- Salesforce: Daily API request allocations vary by edition and license count.
What ships with Onelogin ⇄ Salesforce
Connect Onelogin and Salesforce for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Onelogin–Salesforce connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Onelogin or Salesforce 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 Salesforce record.
Observability
Monitoring
Track your Onelogin ⇄ Salesforce 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 Salesforce.
How the Onelogin and Salesforce 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.
Salesforce
- Integration surface
- REST, SOAP, and Bulk APIs
- Authentication
- OAuth login via a Salesforce user (browser-based authorization flow); requires "API Enabled" permission for polling mode, plus "Author Apex" and "Customize Application" OR "Modify All Data" for trigger mode
- Change detection
- Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting)
- Capabilities
- read · write · CDC
- Rate limits
- Daily API request allocations vary by edition and license count.
How it works
How to connect Onelogin to Salesforce — 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 Salesforce 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
Salesforce
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Onelogin and Salesforce 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 ⇄ SalesforceCustomers 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 SalesforceCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Onelogin and Salesforce integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Onelogin and Salesforce: authenticate both systems, choose the objects to sync (such as Onelogin's Groups and Mappings (mapping rules)), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
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.
-
Common patterns for Onelogin and Salesforce: Where a closed deal should provision access: Salesforce drives Onelogin; Where Onelogin governs your workforce: CRM users kept current; Deactivation and record hand-off. A won or activated customer in Salesforce can create or update the corresponding user or account in Onelogin, so provisioning starts from the CRM record instead of a separate ticket.
-
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. Salesforce: REST, SOAP, and Bulk APIs. Authentication: OAuth login via a Salesforce user (browser-based authorization flow); requires "API Enabled" permission for polling mode, plus "Author Apex" and "Customize Application" OR "Modify All Data" for trigger mode. Stacksync manages authentication, retries, and rate limits on both sides.
-
Salesforce: Records are queried with SOQL, and every standard and custom object carries a SystemModstamp field that sync engines use to order incremental changes. Onelogin: Users, Roles, Apps, and Mapping rules are the writable surface; Groups and the Events audit log are read-only through the OneLogin API. Stacksync's field mapping accounts for these differences between Onelogin and Salesforce 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 Salesforce records are not retained after a sync operation.
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 535 integrations available for Onelogin and Salesforce.
Popular · 7 of 535
-
Onelogin ⇄ Creatio CRM -
Onelogin ⇄ Folk CRM -
Onelogin ⇄ Freshsales -
Salesforce ⇄ Okta -
Salesforce ⇄ Auth0 -
Salesforce ⇄ Jumpcloud -
Salesforce ⇄ Active Directory
No integrations match .
