Real-time
Two-way sync
Changes in DuckDB or Onelogin instantly reflect in both systems. No stale data, no manual imports.
Database ⇄ Security and identity
DuckDB to Onelogin integration — real-time, two-way sync
Keep DuckDB 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 DuckDB and Onelogin
Close the gap between your application data and your directory: DuckDB and Onelogin share users, groups, and access in real time, in both directions.
Onelogin is the system of record for who people are and what they can reach: users, the groups they belong to, and the applications assigned to them. DuckDB holds the operational data those same people show up in, whether an employee or member table that decides who should have an account at all, a customers list, or the rows an application checks before it authorizes an action. The two describe overlapping users and groups, and when a nightly export or a hand-run script is all that connects them, accounts lag joiners and leavers and the application authorizes against a stale picture of who has access.
Stacksync syncs Tables, Views, External files (Parquet/CSV/JSON), Attached databases in DuckDB with Groups, Mappings (mapping rules), Events, Authentication factors (MFA) in Onelogin field by field, in real time, and in both directions. You decide which system owns which fields, with the directory holding credentials and group membership and the database holding the source list of people who should exist at all, and Stacksync keeps every copy consistent, resolving conflicts by rules you set. A person added to a table becomes an account within seconds, a departure disables one just as fast, and the directory's users and groups are always present in your tables as ordinary rows.
Common use cases
- 01 Sync SaaS data to Parquet on object storage and query it with DuckDB without standing up a warehouse.
- 02 Push aggregates computed in DuckDB out to a CRM or business tools so analysis results reach operational systems.
- 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
Read users and groups as ordinary tables
Users, groups, and their memberships from Onelogin land in DuckDB as rows your application and queries can join, so authorization checks and access reporting run against the database instead of the directory API.
Keep group and role membership aligned
A group or role change made in either system updates the other, so the entitlements an application enforces match what the directory grants.
One profile, kept current
A name, department, email, or manager corrected in either system updates the other, so the profile the directory shows and the data the application reads stop drifting apart.
What you can sync between DuckDB 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.
| DuckDB objects | Onelogin objects | How this pairing syncs | |
|---|---|---|---|
| Database files Single-file .duckdb databases that jobs read and write directly on disk or object storage. | Custom user fields Account-level custom attributes on the User record; read and written alongside the standard user profile fields. | Database files is specific to DuckDB and Custom user fields to Onelogin — each maps to any object or custom field on the other side. | |
| Schemas Namespaces within a database used to organize tables in sync outputs. | 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. | Schemas is specific to DuckDB and Users to Onelogin — each maps to any object or custom field on the other side. | |
| Tables Columnar tables created via SQL; the destination for materialized sync data. | Roles Roles that bundle app access; created, updated, and deleted via the Roles API, with users, admins, and apps assigned to each role. | Tables is specific to DuckDB and Roles to Onelogin — each maps to any object or custom field on the other side. | |
| Views SQL views used to shape or filter data for downstream consumers. | Apps (app instances) Connected SAML/OIDC application configs on the account; create, update, delete, and assign to users and roles - the writable app catalog. | Views is specific to DuckDB and Apps (app instances) to Onelogin — each maps to any object or custom field on the other side. | |
| External files (Parquet/CSV/JSON) Files DuckDB queries in place without loading, common as a sync interchange format. | 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. | External files (Parquet/CSV/JSON) is specific to DuckDB and Groups to Onelogin — each maps to any object or custom field on the other side. | |
| Attached databases Additional database files or external systems attached into one session for cross-source queries. | Mappings (mapping rules) Attribute-driven rules that assign roles and app access; full CRUD via the Mappings API, then reapplied across matching users. | Attached databases is specific to DuckDB and Mappings (mapping rules) to Onelogin — each maps to any object or custom field on the other side. |
How changes propagate between DuckDB 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.
DuckDB Onelogin Interval-based propagation
DetectionStacksync polls DuckDB for changes on an incremental schedule, reading only records changed since the previous pass. Polling or full re-reads.
DeliveryEach detected change is written to Onelogin through its API, with automatic retries and rate-limit backoff.
Onelogin DuckDB 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 DuckDB as a row-level write, with types converted between the two schemas.
Rate-limit considerations
- DuckDB: No API rate limits; throughput is bounded by local compute and I/O.
- 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 DuckDB ⇄ Onelogin
Connect DuckDB and Onelogin for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every DuckDB–Onelogin connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever DuckDB 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 DuckDB or Onelogin record.
Observability
Monitoring
Track your DuckDB ⇄ Onelogin sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between DuckDB and Onelogin.
How the DuckDB and Onelogin connectors work
DuckDB
- Integration surface
- In-process SQL engine via client libraries (Python, Node.js, JDBC, CLI); no server or network API by default
- Authentication
- None built in; access control is file-system level (MotherDuck adds token auth for its hosted service)
- Change detection
- Polling or full re-reads; no change feed or transaction log API
- Capabilities
- read · write
- Rate limits
- No API rate limits; throughput is bounded by local compute and I/O
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 DuckDB 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 DuckDB 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.
DuckDB
connected
Onelogin
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the DuckDB 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 · DuckDB ⇄ 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.
DuckDB OneloginCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
DuckDB and Onelogin integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between DuckDB and Onelogin: authenticate both systems, choose the objects to sync (such as DuckDB's Database files and Schemas), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Yes — Stacksync ships production-grade connectors for both DuckDB and Onelogin. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on DuckDB: Polling or full re-reads; no change feed or transaction log API. 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.
-
On the DuckDB side: Tables, Views, External files (Parquet/CSV/JSON), Attached databases, plus custom fields where DuckDB exposes them. On the Onelogin side: Groups, Mappings (mapping rules), Events, Authentication factors (MFA). Stacksync auto-detects both schemas and converts types between the two systems.
-
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 DuckDB and Onelogin: Read users and groups as ordinary tables; Keep group and role membership aligned; One profile, kept current. Users, groups, and their memberships from Onelogin land in DuckDB as rows your application and queries can join, so authorization checks and access reporting run against the database instead of the directory API.
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 446 integrations available for DuckDB and Onelogin.
Popular · 8 of 446
-
DuckDB ⇄ Okta -
DuckDB ⇄ Auth0 -
DuckDB ⇄ Jumpcloud -
DuckDB ⇄ Active Directory -
Onelogin ⇄ Amazon DynamoDB -
Onelogin ⇄ Reltio -
Onelogin ⇄ SAP Hana -
Onelogin ⇄ Jdbc
No integrations match .
