Real-time
Two-way sync
Changes in Close or Onelogin instantly reflect in both systems. No stale data, no manual imports.
CRM ⇄ Security and identity
Close to Onelogin integration — real-time, two-way sync
Keep Close 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 Close and Onelogin
Keep the people Close and Onelogin both track in agreement in real time: the internal users who own records in Close, and the customer login accounts in Onelogin.
A CRM and an identity system usually describe different populations. Close 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 Close are the same employees Onelogin provisions and disables, and when Onelogin also runs the login accounts for your product, the customers in Close are the same users Onelogin authenticates. Left unconnected, a departure in Onelogin leaves stale ownership sitting in Close, and a signup in Onelogin never reaches the account it belongs to.
Stacksync syncs Custom Fields, Users, Smart Views, Leads in Close with Users, Roles, Apps (app instances), Groups 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 Sync Close leads and opportunities into Postgres or a warehouse for pipeline reporting outside Close's built-in reports.
- 02 Two-way sync between Close and a billing or ERP system so closed-won opportunities create customers and invoices automatically.
- 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
Group and entitlement membership as CRM fields
Membership of a directory group or an entitlement in Onelogin maps to fields in Close, such as product tier, plan, or internal team, so segmentation reflects real access rather than a manual guess.
Where a closed deal should provision access: Close drives Onelogin
A won or activated customer in Close 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 Close 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.
What you can sync between Close 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.
| Close objects | Onelogin objects | How this pairing syncs | |
|---|---|---|---|
| Users Sales reps referenced as owners on leads, opportunities, and activities. | 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. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. Custom fields on either side are included in the mapping. | |
| Opportunities Deal records with value, confidence, and status; commonly synced to reporting and billing 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. | Opportunities is specific to Close and Groups to Onelogin — each maps to any object or custom field on the other side. | |
| Activities Calls, emails, SMS, notes, and meetings logged against a lead; the source for engagement analytics. | Mappings (mapping rules) Attribute-driven rules that assign roles and app access; full CRUD via the Mappings API, then reapplied across matching users. | Activities is specific to Close and Mappings (mapping rules) to Onelogin — each maps to any object or custom field on the other side. | |
| Tasks Follow-up items assigned to users; synced for workload and SLA reporting. | Events Audit log of every authentication and admin action; read-only, filtered by since/until, and pushed live through the Event Webhook. | Tasks is specific to Close and Events to Onelogin — each maps to any object or custom field on the other side. | |
| Custom Activities User-defined activity types with their own custom fields, mapped like standard activities. | Authentication factors (MFA) Per-user registered MFA factors; enrolled, verified, and removed through the MFA API for lifecycle and security workflows. | Custom Activities is specific to Close and Authentication factors (MFA) to Onelogin — each maps to any object or custom field on the other side. | |
| Custom Fields Org-specific fields on leads, contacts, and opportunities; addressed by stable field ids in syncs. | Custom user fields Account-level custom attributes on the User record; read and written alongside the standard user profile fields. | Custom Fields is specific to Close and Custom user fields to Onelogin — each maps to any object or custom field on the other side. |
How changes propagate between Close 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.
Close Onelogin Sub-second propagation
DetectionClose notifies Stacksync of record changes through webhook events. Webhook subscriptions for record events, with polling on date_updated fields for backfills.
DeliveryEach detected change is written to Onelogin through its API, with automatic retries and rate-limit backoff.
Onelogin Close 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 Close through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Close: Subject to per-endpoint rate limits communicated in response headers.
- 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 Close ⇄ Onelogin
Connect Close and Onelogin for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Close–Onelogin connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Close 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 Close or Onelogin record.
Observability
Monitoring
Track your Close ⇄ Onelogin sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Close and Onelogin.
How the Close and Onelogin connectors work
Close
- Integration surface
- REST API
- Authentication
- API key (sent via HTTP Basic auth)
- Change detection
- Webhook subscriptions for record events, with polling on date_updated fields for backfills
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to per-endpoint rate limits communicated in response headers
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 Close 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 Close 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.
Close
connected
Onelogin
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Close 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 · Close ⇄ 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.
Close OneloginCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Close and Onelogin integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Close and Onelogin: authenticate both systems, choose the objects to sync (such as Close's Users and Opportunities), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Close: Close's data model is lead-centric: the Lead is a company-level record, and contacts, opportunities, and activities all hang off it, unlike CRMs that treat accounts and contacts as separate top-level objects. Onelogin: The Event Webhook (Event Broadcaster) delivers batches of events to a registered URL for near-real-time triggers, while the Events API filters by since/until for historical pulls; there is no database-level CDC. Stacksync's field mapping accounts for these differences between Close and Onelogin 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 Close and Onelogin records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Close and Onelogin connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Close–Onelogin integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Close and Onelogin. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Close: Webhook subscriptions for record events, with polling on date_updated fields for backfills. 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.
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 527 integrations available for Close and Onelogin.
Popular · 8 of 527
-
Close ⇄ Azure Active Directory -
Close ⇄ Okta -
Close ⇄ Auth0 -
Close ⇄ Jumpcloud -
Onelogin ⇄ Streak CRM -
Onelogin ⇄ SugarCRM -
Onelogin ⇄ Twenty CRM -
Onelogin ⇄ Veeva CRM
No integrations match .
