Real-time
Two-way sync
Changes in Onelogin or Pigment instantly reflect in both systems. No stale data, no manual imports.
Security and identity ⇄ Accounting and finance
Onelogin to Pigment integration — real-time, two-way sync
Keep Onelogin and Pigment 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 Pigment
Keep the people who can act on financial records in Pigment matched to their identities in Onelogin, so access is provisioned, updated, and revoked in real time.
Pigment 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 Scenarios, Data imports, Users and permissions, Applications in Pigment aligned with Mappings (mapping rules), Events, Authentication factors (MFA), Custom user fields 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 Sync headcount and compensation data from an HRIS into workforce planning models.
- 02 Push CRM pipeline data (deals, stages, amounts) into Pigment for revenue and capacity planning.
- 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
People attributes for allocation and approvals
Department, manager, and employee identifiers carried in Onelogin flow to Pigment, 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 Pigment is disabled in the same motion, so departed employees keep no standing access to financial records.
One user roster across both systems
People, their status, and their contact details stay matched between Pigment and Onelogin, so the finance system's login list reflects who actually works here instead of drifting out of date.
What you can sync between Onelogin and Pigment
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 | Pigment 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. | Users and permissions Access controls governing which model areas a sync can touch | Groups is specific to Onelogin and Users and permissions to Pigment — 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. | Applications Planning models organized by domain such as finance, sales, or workforce | Mappings (mapping rules) is specific to Onelogin and Applications to Pigment — 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. | Metrics Multidimensional values holding plans and actuals; the main target for inbound data | Events is specific to Onelogin and Metrics to Pigment — 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. | Dimension lists Master data like accounts, products, or employees that metrics are sliced by | Authentication factors (MFA) is specific to Onelogin and Dimension lists to Pigment — 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 Row-based transactional data loaded into models from source systems | Custom user fields is specific to Onelogin and Tables to Pigment — 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. | Scenarios Versions such as budget, forecast, and actuals that give exported figures their context | Users is specific to Onelogin and Scenarios to Pigment — each maps to any object or custom field on the other side. |
How changes propagate between Onelogin and Pigment
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 Pigment 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 Pigment through its API, with automatic retries and rate-limit backoff.
Pigment Onelogin Interval-based propagation
DetectionStacksync polls Pigment for changes on an incremental schedule, reading only records changed since the previous pass. No change feed.
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.
- Pigment: Subject to the platform's API rate limits.
What ships with Onelogin ⇄ Pigment
Connect Onelogin and Pigment for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Onelogin–Pigment connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Onelogin or Pigment 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 Pigment record.
Observability
Monitoring
Track your Onelogin ⇄ Pigment 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 Pigment.
How the Onelogin and Pigment 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.
Pigment
- Integration surface
- REST-based import and export API
- Authentication
- API keys, issued separately for import and export
- Change detection
- no change feed; syncs run scheduled imports and exports
- Capabilities
- read · write
- Rate limits
- subject to the platform's API rate limits
How it works
How to connect Onelogin to Pigment — 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 Pigment 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
Pigment
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Onelogin and Pigment 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 ⇄ PigmentCustomers 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 PigmentCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Onelogin and Pigment integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Onelogin and Pigment: authenticate both systems, choose the objects to sync (such as Onelogin's Groups and Mappings (mapping rules)), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
On the Pigment side: Scenarios, Data imports, Users and permissions, Applications, plus custom fields where Pigment exposes them. On the Onelogin side: Mappings (mapping rules), Events, Authentication factors (MFA), Custom user fields. 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 Onelogin and Pigment: People attributes for allocation and approvals; Where Onelogin is the identity source: offboarding reaches the books; One user roster across both systems. Department, manager, and employee identifiers carried in Onelogin flow to Pigment, so expense routing, cost-center allocation, and approval chains use the same org data as the directory.
-
Onelogin: 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. Pigment: REST-based import and export API. Authentication: API keys, issued separately for import and export. Stacksync manages authentication, retries, and rate limits on both sides.
-
Pigment: Pigment's model is multidimensional: metrics are sliced by dimension lists, so inbound records must map to those dimensions rather than flat columns. Onelogin: Some write calls are queued to OneLogin's job system and can take up to about five minutes to finish processing rather than completing synchronously. Stacksync's field mapping accounts for these differences between Onelogin and Pigment without custom code.
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 409 integrations available for Onelogin and Pigment.
Popular · 8 of 409
-
Onelogin ⇄ Workday -
Onelogin ⇄ Anaplan -
Onelogin ⇄ Chargebee -
Onelogin ⇄ Hyperline -
Pigment ⇄ Azure Active Directory -
Pigment ⇄ Okta -
Pigment ⇄ Auth0 -
Pigment ⇄ Jumpcloud
No integrations match .
