Skip to content
Business productivity ⇄ Security and identity

Full Enrich to Onelogin integration — real-time, two-way sync

Keep Full Enrich 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 Full Enrich and Onelogin

Keep the users, groups, and profile details that Full Enrich and Onelogin share consistent in real time, so who can work in Full Enrich always matches who your directory in Onelogin says belongs there.

Onelogin is where a company records who its people are: their accounts, the groups and roles they hold, and the attributes attached to each one. Full Enrich is where a slice of those same people do their work, as agents, members, or seats, and every one of them needs a matching account with the right access. When a directory and a productivity tool are maintained by hand, someone added, moved, or offboarded in one becomes a stale entry in the other within the hour.

Stacksync syncs Phone numbers, Credits, Enrichment requests, Contacts in Full Enrich with Mappings (mapping rules), Events, Authentication factors (MFA), Custom user fields in Onelogin bi-directionally and in real time. A user created, renamed, moved between groups, or deactivated in either system updates the matching record in the other within seconds, with field-level mapping and conflict resolution in place of CSV uploads and nightly IT batch jobs.

That matters most at the edges of employment. When both systems agree on who has an account, which groups they belong to, and whether they are still active, granting access on day one and revoking it on the last day stops being a manual checklist that trails the directory.

Common use cases

  • 01 Route enrichment completions via webhook into a database that keeps contactability status current.
  • 02 Enrich new CRM contacts with verified emails and mobile numbers as they are created.
  • 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

Keep profile attributes current

A person's name, email, department, manager, or phone number corrected in either system updates the other, so the productivity tool shows the same details the directory holds of record.

Mirror group and role membership

Moving a user between groups or roles in Onelogin updates their team, permission set, or seat in Full Enrich, so what someone can do reflects where they sit in the directory.

One record per person

People matched across both systems on email or an external ID stay linked, so every account and action in Full Enrich ties back to the right identity in Onelogin.

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

Full Enrich objects Onelogin objects How this pairing syncs
Credits Account balance consumed on successful finds; monitored to pace sync jobs. Custom user fields Account-level custom attributes on the User record; read and written alongside the standard user profile fields. Credits is specific to Full Enrich and Custom user fields to Onelogin — each maps to any object or custom field on the other side.
Enrichment requests Submitted batches of contacts to enrich; processed asynchronously by the waterfall. 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. Enrichment requests is specific to Full Enrich and Users to Onelogin — each maps to any object or custom field on the other side.
Contacts The person inputs (name plus company or domain) sent for enrichment. Roles Roles that bundle app access; created, updated, and deleted via the Roles API, with users, admins, and apps assigned to each role. Contacts is specific to Full Enrich and Roles to Onelogin — each maps to any object or custom field on the other side.
Enrichment results Completed records fetched by request ID or delivered via webhook. Apps (app instances) Connected SAML/OIDC application configs on the account; create, update, delete, and assign to users and roles - the writable app catalog. Enrichment results is specific to Full Enrich and Apps (app instances) to Onelogin — each maps to any object or custom field on the other side.
Emails Returned addresses with verification status, written back to the CRM or database. 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. Emails is specific to Full Enrich and Groups to Onelogin — each maps to any object or custom field on the other side.
Phone numbers Returned mobile and direct-dial numbers from the provider waterfall. Mappings (mapping rules) Attribute-driven rules that assign roles and app access; full CRUD via the Mappings API, then reapplied across matching users. Phone numbers is specific to Full Enrich and Mappings (mapping rules) to Onelogin — each maps to any object or custom field on the other side.

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

Full Enrich Onelogin Sub-second propagation

DetectionFull Enrich notifies Stacksync of record changes through webhook events. Webhook callbacks when enrichment batches complete, with polling of result endpoints as a fallback.

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

Onelogin Full Enrich 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 Full Enrich through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Full Enrich: Subject to the platform's API rate limits and per-batch size constraints.
  • 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 Full Enrich ⇄ Onelogin

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Full Enrich and Onelogin connectors work

Full Enrich

Integration surface
REST API with asynchronous bulk enrichment endpoints
Authentication
API key (Bearer token)
Change detection
Webhook callbacks when enrichment batches complete, with polling of result endpoints as a fallback
Capabilities
read · write · webhooks
Rate limits
Subject to the platform's API rate limits and per-batch size constraints

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 Full Enrich 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 Full Enrich 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
    Full Enrich connected
    Onelogin connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Full Enrich 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 · Full Enrich ⇄ 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
    Full Enrich Onelogin
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Full Enrich 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 384 integrations available for Full Enrich and Onelogin.

Popular · 7 of 384
All Full Enrich 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