Real-time
Two-way sync
Changes in Onelogin or Supabase instantly reflect in both systems. No stale data, no manual imports.
Security and identity ⇄ Database
Onelogin to Supabase integration — real-time, two-way sync
Keep Onelogin and Supabase 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 Supabase
Close the gap between your application data and your directory: Supabase 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. Supabase 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 Views, Schemas, auth.users, Row Level Security Policies in Supabase with Mappings (mapping rules), Events, Authentication factors (MFA), Custom user fields 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 application tables in Supabase with the CRM two-way so new signups appear as contacts and sales edits flow back to the app
- 02 Mirror billing and subscription records into Supabase tables the application can join directly
- 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
Provision accounts from the source of truth
When a person is added to the employee, member, or customer table in Supabase, Stacksync creates the matching user in Onelogin with the right attributes, so access starts from live data instead of a manual ticket.
Deprovision the moment the record changes
When someone is marked inactive or removed in Supabase, the matching account in Onelogin is disabled within seconds, closing the window between a departure and a login that still works.
Read users and groups as ordinary tables
Users, groups, and their memberships from Onelogin land in Supabase as rows your application and queries can join, so authorization checks and access reporting run against the database instead of the directory API.
What you can sync between Onelogin and Supabase
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 | Supabase objects | How this pairing syncs | |
|---|---|---|---|
| Events Audit log of every authentication and admin action; read-only, filtered by since/until, and pushed live through the Event Webhook. | Database Functions Postgres functions that can transform or validate synced rows. | Events is specific to Onelogin and Database Functions to Supabase — 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. | Storage Object Metadata File metadata rows that can be joined to synced application data. | Authentication factors (MFA) is specific to Onelogin and Storage Object Metadata to Supabase — 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. | Tables Standard Postgres tables; the primary two-way sync target. | Custom user fields is specific to Onelogin and Tables to Supabase — 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. | Views Read-side projections exposed to outbound syncs. | Users is specific to Onelogin and Views to Supabase — 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. | Schemas Namespaces (public and custom) that scope sync access. | Roles is specific to Onelogin and Schemas to Supabase — 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. | auth.users Managed authentication users, often mirrored into CRM or support systems. | Apps (app instances) is specific to Onelogin and auth.users to Supabase — each maps to any object or custom field on the other side. |
How changes propagate between Onelogin and Supabase
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 Supabase 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 Supabase as a row-level write, with types converted between the two schemas.
Supabase Onelogin Sub-second propagation
DetectionSupabase pushes changes as they happen — webhook events backed by change data capture. Log-based CDC via Postgres logical replication, the same WAL feed that powers Supabase Realtime.
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.
- Supabase: SQL access is bounded by connection limits (pooled connections are provided); the REST layer is subject to the platform's limits.
What ships with Onelogin ⇄ Supabase
Connect Onelogin and Supabase for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Onelogin–Supabase connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Onelogin or Supabase 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 Supabase record.
Observability
Monitoring
Track your Onelogin ⇄ Supabase 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 Supabase.
How the Onelogin and Supabase 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.
Supabase
- Integration surface
- Direct PostgreSQL wire protocol connection, plus an auto-generated REST API (PostgREST)
- Authentication
- Database credentials (connection string) for SQL access; API keys (anon / service role) for the REST layer
- Change detection
- Log-based CDC via Postgres logical replication, the same WAL feed that powers Supabase Realtime; database webhooks can also fire on row changes
- Capabilities
- read · write · CDC · webhooks
- Rate limits
- SQL access is bounded by connection limits (pooled connections are provided); the REST layer is subject to the platform's limits
How it works
How to connect Onelogin to Supabase — 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 Supabase 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
Supabase
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Onelogin and Supabase 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 ⇄ SupabaseCustomers 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 SupabaseCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Onelogin and Supabase integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Onelogin and Supabase: authenticate both systems, choose the objects to sync (such as Onelogin's Events and Authentication factors (MFA)), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Supabase: Supabase Realtime is built on the Postgres write-ahead log, streaming row changes over websockets. 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 Supabase 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 Supabase records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Onelogin and Supabase connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Onelogin–Supabase integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Onelogin and Supabase. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection 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. On Supabase: Log-based CDC via Postgres logical replication, the same WAL feed that powers Supabase Realtime; database webhooks can also fire on row changes. 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 538 integrations available for Onelogin and Supabase.
Popular · 8 of 538
-
Onelogin ⇄ Citus -
Onelogin ⇄ Couchbase -
Onelogin ⇄ DuckDB -
Onelogin ⇄ Elasticsearch -
Supabase ⇄ Active Directory - Supabase ⇄ Azure Active Directory
-
Supabase ⇄ Okta -
Supabase ⇄ Auth0
No integrations match .
