Skip to content
Security and identity ⇄ Data warehouse

Onelogin to Snowflake integration — real-time, two-way sync

Keep Onelogin and Snowflake 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 Snowflake

Land the users, groups, and access events from Onelogin in Snowflake continuously for security analytics, and write computed results back — without building or maintaining a pipeline.

Onelogin is the record of who exists and what they can reach; Snowflake is where the business measures everything else. The two overlap on people and their access — the same users, groups, roles, and events that Onelogin governs are what security, compliance, and analytics teams want to query in Snowflake. Getting them there usually means a brittle export that runs overnight and hands auditors a snapshot that is already out of date.

Stacksync syncs Authentication factors (MFA), Custom user fields, Users, Roles from Onelogin into tables in Snowflake in real time, and the connection works in both directions: values computed in Snowflake, such as risk scores or access-review decisions, can be written back to attributes in Onelogin where the identity team acts on them. Schema changes are handled, API limits are managed, and the sync is something you configure rather than a pipeline you keep alive.

Common use cases

  • 01 Land CRM and ERP records in Snowflake continuously so BI reflects business systems without nightly batch ETL
  • 02 Activate modeled Snowflake tables by syncing scores and attributes back into CRM fields sales can act on
  • 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

Risk and review results back on the account

Risk scores, anomaly flags, or access-review outcomes computed in Snowflake write back to attributes on the matching user in Onelogin, where the identity team can act on them.

Directory data in the warehouse, minus the pipeline

Users, groups, and roles from Onelogin arrive in Snowflake as queryable tables, current within seconds instead of a nightly directory export.

Access and sign-in analytics

Sign-in and access events from Onelogin land in Snowflake, so security and compliance teams can query who reached what, and when, alongside the rest of the business's data.

What you can sync between Onelogin and Snowflake

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 Snowflake 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. Virtual Warehouses The compute a sync's queries run on, sized independently of storage. Groups is specific to Onelogin and Virtual Warehouses to Snowflake — 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. Databases Top-level containers that scope which data a sync can touch. Mappings (mapping rules) is specific to Onelogin and Databases to Snowflake — 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. Schemas Namespaces within a database used to organize synced tables. Events is specific to Onelogin and Schemas to Snowflake — 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. Tables The main landing and activation target for synced records. Authentication factors (MFA) is specific to Onelogin and Tables to Snowflake — 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. Views Modeled projections used as the source side of outbound syncs. Custom user fields is specific to Onelogin and Views to Snowflake — 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. Materialized Views Precomputed results synced outward for low-latency reads. Users is specific to Onelogin and Materialized Views to Snowflake — each maps to any object or custom field on the other side.

How changes propagate between Onelogin and Snowflake

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 Snowflake 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 applied to Snowflake as a row-level write, with types converted between the two schemas.

Snowflake Onelogin Sub-second propagation

DetectionChanges in Snowflake are captured at the source via change data capture — no polling loop against its API. The setup script grants "create stream" on synced schemas (Snowflake streams), but the docs do not name the change-capture mechanism.

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.
  • Snowflake: No conventional API rate limits; cost and throughput are governed by virtual warehouse size and running time.
What ships with Onelogin ⇄ Snowflake

Connect Onelogin and Snowflake for flexible, real-time data sync.

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Onelogin ⇄ Snowflake 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 Snowflake.

How the Onelogin and Snowflake 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.

Snowflake

Integration surface
SQL via JDBC/ODBC and native drivers, plus the Snowflake SQL REST API
Authentication
Dedicated Snowflake service user + role with RSA key-pair authentication (Stacksync-provided public key), created via a setup script requiring SECURITY_ADMIN and ACCOUNTADMIN roles
Change detection
Not explicitly stated; the setup script grants "create stream" on synced schemas (Snowflake streams), but the docs do not name the change-capture mechanism
Capabilities
read · write · CDC
Rate limits
No conventional API rate limits; cost and throughput are governed by virtual warehouse size and running time
Snowflake setup guide
How it works

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

    Choose tables

    Pick the Onelogin and Snowflake 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 ⇄ Snowflake
    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 Snowflake
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Onelogin and Snowflake 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.

Learn more about security
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:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 545 integrations available for Onelogin and Snowflake.

Popular · 8 of 545
All Onelogin integrations All Snowflake integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

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

Book a demo Tour the platform on your own