Skip to content
Data warehouse ⇄ Security and identity

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

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

Land the users, groups, and access events from Onelogin in BigQuery 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; BigQuery 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 BigQuery. Getting them there usually means a brittle export that runs overnight and hands auditors a snapshot that is already out of date.

Stacksync syncs Apps (app instances), Groups, Mappings (mapping rules), Events from Onelogin into tables in BigQuery in real time, and the connection works in both directions: values computed in BigQuery, 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 Maintain a customer master table in BigQuery joined across CRM, billing, and support sources
  • 02 Feed ML feature tables in BigQuery from operational systems on a continuous schedule
  • 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

Access and sign-in analytics

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

Access governance on joined data

Join Onelogin's users and group memberships with HR, product, and usage data already in BigQuery to surface who holds access they no longer need.

Queryable history for audit and compliance

A continuously synced copy in BigQuery gives you a durable, queryable record of identity and access state for access reviews, SOC 2, and audit questions.

What you can sync between BigQuery 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.

BigQuery objects Onelogin objects How this pairing syncs
Tables The syncable unit: only tables can be synced per the Stacksync docs. Events Audit log of every authentication and admin action; read-only, filtered by since/until, and pushed live through the Event Webhook. Tables is specific to BigQuery and Events to Onelogin — each maps to any object or custom field on the other side.
Partitioned tables Synced like regular tables; partition columns map to target fields. Authentication factors (MFA) Per-user registered MFA factors; enrolled, verified, and removed through the MFA API for lifecycle and security workflows. Partitioned tables is specific to BigQuery and Authentication factors (MFA) to Onelogin — each maps to any object or custom field on the other side.
Clustered tables Supported; clustering is transparent to the sync. Custom user fields Account-level custom attributes on the User record; read and written alongside the standard user profile fields. Clustered tables is specific to BigQuery and Custom user fields to Onelogin — each maps to any object or custom field on the other side.
Datasets Organizational container — you pick which dataset’s tables to sync. 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. Datasets is specific to BigQuery and Users to Onelogin — each maps to any object or custom field on the other side.
Projects Connection scope: the service account grants access per project. Roles Roles that bundle app access; created, updated, and deleted via the Roles API, with users, admins, and apps assigned to each role. Projects is specific to BigQuery and Roles to Onelogin — each maps to any object or custom field on the other side.

How changes propagate between BigQuery 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.

BigQuery Onelogin Sub-second propagation

DetectionChanges in BigQuery are captured at the source via change data capture — no polling loop against its API. Real-time notification service deployed into your Google Cloud project: Eventarc ("a notification service that enables real-time updates to happen").

DeliveryEach detected change is written to Onelogin through its API, with automatic retries and rate-limit backoff.

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

Rate-limit considerations

  • BigQuery: Subject to Google Cloud quotas on queries, DML, and streaming; DML is supported but the platform favors append-heavy batch and streaming loads over row-at-a-time writes.
  • 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 BigQuery ⇄ Onelogin

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your BigQuery ⇄ Onelogin sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between BigQuery and Onelogin.

How the BigQuery and Onelogin connectors work

BigQuery

Integration surface
GoogleSQL via the BigQuery REST API, client libraries, JDBC/ODBC drivers, and the Storage Read/Write APIs
Authentication
Google Cloud service account: create a dedicated service account, grant roles (BigQuery Data Editor, BigQuery Job User, Cloud Functions Service Agent, Cloud Run Developer, Eventarc Event Receiver
Change detection
Real-time notification service deployed into your Google Cloud project: Eventarc ("a notification service that enables real-time updates to happen") with a Cloud Run "secure portal for real-time notification service in
Capabilities
read · write · CDC
Rate limits
Subject to Google Cloud quotas on queries, DML, and streaming; DML is supported but the platform favors append-heavy batch and streaming loads over row-at-a-time writes
BigQuery setup guide

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 BigQuery 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.

  1. 01

    Connect your apps

    Authenticate BigQuery 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.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    BigQuery connected
    Onelogin connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the BigQuery 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · BigQuery ⇄ Onelogin
    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
    BigQuery Onelogin
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

BigQuery and Onelogin 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 540 integrations available for BigQuery and Onelogin.

Popular · 8 of 540
All BigQuery integrations All Onelogin 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