Real-time
Two-way sync
Changes in Onelogin or Outreach instantly reflect in both systems. No stale data, no manual imports.
Security and identity ⇄ CRM
Onelogin to Outreach integration — real-time, two-way sync
Keep Onelogin and Outreach 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 Outreach
Keep the people Outreach and Onelogin both track in agreement in real time: the internal users who own records in Outreach, and the customer login accounts in Onelogin.
A CRM and an identity system usually describe different populations. Outreach 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 Outreach are the same employees Onelogin provisions and disables, and when Onelogin also runs the login accounts for your product, the customers in Outreach are the same users Onelogin authenticates. Left unconnected, a departure in Onelogin leaves stale ownership sitting in Outreach, and a signup in Onelogin never reaches the account it belongs to.
Stacksync syncs Sequences, Sequence states, Mailings, Calls in Outreach with Roles, Apps (app instances), Groups, Mappings (mapping rules) 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 Enroll leads in sequences automatically by writing sequence-state records when a lead crosses a scoring threshold in the warehouse.
- 02 Pull mailing, call, and task activity into a database for engagement analytics beyond native reports.
- 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
Where a closed deal should provision access: Outreach drives Onelogin
A won or activated customer in Outreach 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 Outreach 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 Outreach 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 Outreach
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 | Outreach objects | How this pairing syncs | |
|---|---|---|---|
| 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. | Users Seat holders used to resolve ownership on synced records | 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. | |
| Custom user fields Account-level custom attributes on the User record; read and written alongside the standard user profile fields. | Tasks Rep action items mirrored between Outreach and the CRM | Custom user fields is specific to Onelogin and Tasks to Outreach — 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. | Opportunities Deal records used to tie engagement to pipeline outcomes | Roles is specific to Onelogin and Opportunities to Outreach — each maps to any object or custom field on the other side. | |
| Apps (app instances) Connected SAML/OIDC application configs on the account; create, update, delete, and assign to users and roles - the writable app catalog. | Mailboxes Connected sending accounts referenced when attributing outbound activity | Apps (app instances) is specific to Onelogin and Mailboxes to Outreach — 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. | Prospects The people being engaged; the main record kept in sync with the CRM | Groups is specific to Onelogin and Prospects to Outreach — 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. | Accounts Companies grouping prospects, aligned with CRM account ownership | Mappings (mapping rules) is specific to Onelogin and Accounts to Outreach — each maps to any object or custom field on the other side. |
How changes propagate between Onelogin and Outreach
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 Outreach 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 Outreach through its API, with automatic retries and rate-limit backoff.
Outreach Onelogin Sub-second propagation
DetectionOutreach notifies Stacksync of record changes through webhook events. Webhook subscriptions on resource create, update, and destroy events, plus polling.
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.
- Outreach: Subject to per-user hourly rate limits.
What ships with Onelogin ⇄ Outreach
Connect Onelogin and Outreach for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Onelogin–Outreach connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Onelogin or Outreach 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 Outreach record.
Observability
Monitoring
Track your Onelogin ⇄ Outreach 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 Outreach.
How the Onelogin and Outreach 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.
Outreach
- Integration surface
- REST API conforming to the JSON:API specification
- Authentication
- OAuth 2.0
- Change detection
- webhook subscriptions on resource create, update, and destroy events, plus polling
- Capabilities
- read · write · webhooks
- Rate limits
- subject to per-user hourly rate limits
How it works
How to connect Onelogin to Outreach — 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 Outreach 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
Outreach
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Onelogin and Outreach 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 ⇄ OutreachCustomers 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 OutreachCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Onelogin and Outreach integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Onelogin and Outreach: authenticate both systems, choose the objects to sync (such as Onelogin's Users and Custom user fields), 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 Outreach: Where a closed deal should provision access: Outreach drives Onelogin; Where Onelogin governs your workforce: CRM users kept current; Deactivation and record hand-off. A won or activated customer in Outreach 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. Outreach: REST API conforming to the JSON:API specification. Authentication: OAuth 2.0. Stacksync manages authentication, retries, and rate limits on both sides.
-
Outreach: Sequence enrollment is modeled as its own resource (sequence states), so adding a prospect to a cadence is a normal record write rather than a special action. Onelogin: OneLogin enforces an account-level rate limit of 5,000 API calls per hour shared across all access tokens; exceeding it returns HTTP 429, and the count resets each hour. Stacksync's field mapping accounts for these differences between Onelogin and Outreach 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 Outreach 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 497 integrations available for Onelogin and Outreach.
Popular · 7 of 497
-
Onelogin ⇄ Vitally -
Onelogin ⇄ DealCloud -
Onelogin ⇄ Chorusai -
Outreach ⇄ Auth0 -
Outreach ⇄ Jumpcloud -
Outreach ⇄ Active Directory - Outreach ⇄ Azure Active Directory
No integrations match .
