Real-time
Two-way sync
Changes in Onelogin or Rillet instantly reflect in both systems. No stale data, no manual imports.
Security and identity ⇄ Accounting and finance
Onelogin to Rillet integration — real-time, two-way sync
Keep Onelogin and Rillet 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 Rillet
Keep the people who can act on financial records in Rillet matched to their identities in Onelogin, so access is provisioned, updated, and revoked in real time.
Rillet runs the money — the ledgers, invoices, budgets, and payments — and every one of those actions is taken by a person with a login. Onelogin is where those people and their access actually live: who is employed, what team they belong to, and what they are allowed to do. The two systems rarely share customers or transactions, but they share the one thing that governs both — the user. When that overlap is maintained by hand, a departed employee keeps finance access for weeks and a new hire waits on a ticket to get any.
Stacksync keeps Invoice, Credit Memo, Bill, Journal Entry in Rillet aligned with Custom user fields, Users, Roles, Apps (app instances) in Onelogin, field by field and in real time. A person added, moved, or deactivated on the identity side updates their matching user in the finance system within seconds, with the role or permission set mapped from the group they belong to. Direction is yours to set: lead provisioning from the directory, or let an HR-owned finance record drive the downstream accounts.
For a finance team, that alignment is an audit control rather than a convenience. When the user list in the books matches the identity source of truth, segregation-of-duties and access reviews start from data that is already correct instead of an export that was current last quarter.
Common use cases
- 01 Keep customers and invoices aligned between Rillet and a CRM so finance and sales work from the same account records.
- 02 Mirror journal entries and contract revenue data into a warehouse for board and ARR reporting.
- 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
Access reviews backed by live data
Because the user list in Rillet matches the identity source in Onelogin in real time, access certifications and SOX-style reviews start from current membership rather than a stale spreadsheet.
People attributes for allocation and approvals
Department, manager, and employee identifiers carried in Onelogin flow to Rillet, so expense routing, cost-center allocation, and approval chains use the same org data as the directory.
Where Onelogin is the identity source: offboarding reaches the books
When a person is deactivated in Onelogin, their matching user in Rillet is disabled in the same motion, so departed employees keep no standing access to financial records.
What you can sync between Onelogin and Rillet
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 | Rillet objects | How this pairing syncs | |
|---|---|---|---|
| Roles Roles that bundle app access; created, updated, and deleted via the Roles API, with users, admins, and apps assigned to each role. | Bill Synced with incremental and full sync per the Stacksync docs. | Roles is specific to Onelogin and Bill to Rillet — 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. | Journal Entry Synced with incremental and full sync per the Stacksync docs. | Apps (app instances) is specific to Onelogin and Journal Entry to Rillet — 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. | Invoice Payment Synced with incremental and full sync per the Stacksync docs. | Groups is specific to Onelogin and Invoice Payment to Rillet — 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. | Charge Synced with incremental and full sync per the Stacksync docs. | Mappings (mapping rules) is specific to Onelogin and Charge to Rillet — 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. | Reimbursement Synced with incremental and full sync per the Stacksync docs. | Events is specific to Onelogin and Reimbursement to Rillet — 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. | Custom Field Synced with incremental and full sync per the Stacksync docs. | Authentication factors (MFA) is specific to Onelogin and Custom Field to Rillet — each maps to any object or custom field on the other side. |
How changes propagate between Onelogin and Rillet
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 Rillet 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 Rillet through its API, with automatic retries and rate-limit backoff.
Rillet Onelogin Sub-second propagation
DetectionRillet pushes changes as they happen — webhook events backed by change data capture. Near real-time updates via change tracking.
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.
- Rillet: Subject to the platform's API rate limits.
What ships with Onelogin ⇄ Rillet
Connect Onelogin and Rillet for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Onelogin–Rillet connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Onelogin or Rillet 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 Rillet record.
Observability
Monitoring
Track your Onelogin ⇄ Rillet 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 Rillet.
How the Onelogin and Rillet 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.
Rillet
- Integration surface
- REST API (OpenAPI-specified, with production and sandbox environments)
- Authentication
- API key generated in Rillet (Organization Setting -> API Access); uncheck Read Only for bidirectional sync, check Read Only for one-way sync
- Change detection
- Near real-time updates via change tracking; incremental sync per object, with delete detection (some objects checked every 1h or 4h)
- Capabilities
- read · write · CDC · webhooks
- Rate limits
- Subject to the platform's API rate limits.
How it works
How to connect Onelogin to Rillet — 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 Rillet 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
Rillet
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Onelogin and Rillet 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 ⇄ RilletCustomers 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 RilletCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Onelogin and Rillet integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Onelogin and Rillet: authenticate both systems, choose the objects to sync (such as Onelogin's Roles and Apps (app instances)), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
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 Rillet records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Onelogin and Rillet connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Onelogin–Rillet integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Onelogin and Rillet. 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 Rillet: Near real-time updates via change tracking; incremental sync per object, with delete detection (some objects checked every 1h or 4h). Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Rillet side: Invoice, Credit Memo, Bill, Journal Entry, plus custom fields where Rillet exposes them. On the Onelogin side: Custom user fields, Users, Roles, Apps (app instances). Stacksync auto-detects both schemas and converts types between the two systems.
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 425 integrations available for Onelogin and Rillet.
Popular · 8 of 425
-
Onelogin ⇄ Adyen -
Onelogin ⇄ Logisense -
Onelogin ⇄ Bill -
Onelogin ⇄ Braintree -
Rillet ⇄ Jumpcloud -
Rillet ⇄ Active Directory - Rillet ⇄ Azure Active Directory
-
Rillet ⇄ Okta
No integrations match .
