Skip to content
Business productivity ⇄ Security and identity

Customer.io to Onelogin integration — real-time, two-way sync

Keep Customer.io 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 Customer.io and Onelogin

Keep the users, groups, and profile details that Customer.io and Onelogin share consistent in real time, so who can work in Customer.io 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. Customer.io 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 Campaigns, Broadcasts, Deliveries / Messages, Newsletters in Customer.io with Users, Roles, Apps (app instances), Groups 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 Sync account-level objects and their person relationships for B2B messaging keyed to company attributes.
  • 02 Sync product usage and billing attributes from Postgres onto Customer.io people so lifecycle campaigns trigger on real product behavior.
  • 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

One record per person

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

Provision access when someone joins

A user added to Onelogin, or moved into a group inside it, gets the matching account or membership created in Customer.io, so a new hire can start working without a separate setup ticket.

Close access when someone leaves

When a user is disabled or removed in Onelogin, their account in Customer.io is deactivated in step, so offboarding shuts down access everywhere instead of leaving a live login behind.

What you can sync between Customer.io 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.

Customer.io objects Onelogin objects How this pairing syncs
Events Behavioral events sent via the Track API that trigger campaigns. Events Audit log of every authentication and admin action; read-only, filtered by since/until, and pushed live through the Event Webhook. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Broadcasts One-off sends to segments or audiences, triggerable via API. Apps (app instances) Connected SAML/OIDC application configs on the account; create, update, delete, and assign to users and roles - the writable app catalog. Broadcasts is specific to Customer.io and Apps (app instances) to Onelogin — each maps to any object or custom field on the other side.
Deliveries / Messages Per-recipient message records whose lifecycle events flow out through reporting webhooks. 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. Deliveries / Messages is specific to Customer.io and Groups to Onelogin — each maps to any object or custom field on the other side.
Newsletters Recurring email sends with performance metrics available for reporting syncs. Mappings (mapping rules) Attribute-driven rules that assign roles and app access; full CRUD via the Mappings API, then reapplied across matching users. Newsletters is specific to Customer.io and Mappings (mapping rules) to Onelogin — each maps to any object or custom field on the other side.
People Profiles with attributes, matched on identifiers like id or email; the main write target of data syncs. Authentication factors (MFA) Per-user registered MFA factors; enrolled, verified, and removed through the MFA API for lifecycle and security workflows. People is specific to Customer.io and Authentication factors (MFA) to Onelogin — each maps to any object or custom field on the other side.
Objects Non-person entities such as accounts or companies, related to people for account-level messaging. Custom user fields Account-level custom attributes on the User record; read and written alongside the standard user profile fields. Objects is specific to Customer.io and Custom user fields to Onelogin — each maps to any object or custom field on the other side.

How changes propagate between Customer.io 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.

Customer.io Onelogin Sub-second propagation

DetectionCustomer.io notifies Stacksync of record changes through webhook events. Reporting webhooks push message and delivery events.

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

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

Rate-limit considerations

  • Customer.io: Subject to per-API rate limits documented by Customer.io.
  • 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 Customer.io ⇄ Onelogin

Connect Customer.io and Onelogin for flexible, real-time data sync.

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Customer.io and Onelogin.

How the Customer.io and Onelogin connectors work

Customer.io

Integration surface
REST APIs split by purpose: Track API for data ingestion, App API for campaigns, people lookups, and messages
Authentication
Basic auth with site ID and API key for the Track API; bearer token for the App API
Change detection
Reporting webhooks push message and delivery events; person attribute changes are not streamed and require source-side detection
Capabilities
read · write · webhooks
Rate limits
Subject to per-API rate limits documented by Customer.io

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

    Choose tables

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

Customer.io 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 415 integrations available for Customer.io and Onelogin.

Popular · 8 of 415
All Customer.io 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