Skip to content
CRM ⇄ Security and identity

Freshworks CRM to Onelogin integration — real-time, two-way sync

Keep Freshworks CRM 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 Freshworks CRM and Onelogin

Keep the people Freshworks CRM and Onelogin both track in agreement in real time: the internal users who own records in Freshworks CRM, and the customer login accounts in Onelogin.

A CRM and an identity system usually describe different populations. Freshworks CRM tracks customers, contacts, and the deals in motion; Onelogin governs who is allowed to sign in and what they can reach. Where the two meet is people. The reps who own records in Freshworks CRM are the same employees Onelogin provisions and disables, and when Onelogin also runs the login accounts for your product, the customers in Freshworks CRM are the same users Onelogin authenticates. Left unconnected, a departure in Onelogin leaves stale ownership sitting in Freshworks CRM, and a signup in Onelogin never reaches the account it belongs to.

Stacksync syncs Deals, Tasks, Appointments, Sales activities in Freshworks CRM with Roles, Apps (app instances), Groups, Mappings (mapping rules) in Onelogin in real time and in both directions, matching on email or an external ID and mapping field by field. You decide which system owns which fields, and new users, role and group changes, deactivations, and account status move within seconds instead of waiting on a quarterly access review or a manual export.

Common use cases

  • 01 Keep list membership aligned with segments computed in the warehouse.
  • 02 Mirror deal and activity data into a Postgres database that internal tools query directly.
  • 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

Deactivation and record hand-off

When someone is disabled in Onelogin, the matching user in Freshworks CRM is deactivated too, and the accounts, contacts, and deals they owned are flagged for reassignment, so nothing goes unattended after they leave.

Where Onelogin runs customer login accounts: identity on the customer record

Signup, account status, multi-factor enrollment, and last-login from Onelogin land on the matching contact or account in Freshworks CRM, so go-to-market teams see who has actually activated and who has gone dormant.

Group and entitlement membership as CRM fields

Membership of a directory group or an entitlement in Onelogin maps to fields in Freshworks CRM, such as product tier, plan, or internal team, so segmentation reflects real access rather than a manual guess.

What you can sync between Freshworks CRM 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.

Freshworks CRM objects Onelogin objects How this pairing syncs
Contacts Unified sales-and-marketing person records; the core entity for bidirectional syncs. Mappings (mapping rules) Attribute-driven rules that assign roles and app access; full CRUD via the Mappings API, then reapplied across matching users. Contacts is specific to Freshworks CRM and Mappings (mapping rules) to Onelogin — each maps to any object or custom field on the other side.
Accounts Company records kept consistent with ERP and billing systems. Events Audit log of every authentication and admin action; read-only, filtered by since/until, and pushed live through the Event Webhook. Accounts is specific to Freshworks CRM and Events to Onelogin — each maps to any object or custom field on the other side.
Deals Pipeline records synced out for forecasting and full-funnel reporting. Authentication factors (MFA) Per-user registered MFA factors; enrolled, verified, and removed through the MFA API for lifecycle and security workflows. Deals is specific to Freshworks CRM and Authentication factors (MFA) to Onelogin — each maps to any object or custom field on the other side.
Tasks Follow-ups created from external signals such as product usage events. Custom user fields Account-level custom attributes on the User record; read and written alongside the standard user profile fields. Tasks is specific to Freshworks CRM and Custom user fields to Onelogin — each maps to any object or custom field on the other side.
Appointments Meeting records readable for activity reporting. 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. Appointments is specific to Freshworks CRM and Users to Onelogin — each maps to any object or custom field on the other side.
Sales activities Logged activity types used in engagement and productivity analysis. Roles Roles that bundle app access; created, updated, and deleted via the Roles API, with users, admins, and apps assigned to each role. Sales activities is specific to Freshworks CRM and Roles to Onelogin — each maps to any object or custom field on the other side.

How changes propagate between Freshworks CRM 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.

Freshworks CRM Onelogin Sub-second propagation

DetectionFreshworks CRM notifies Stacksync of record changes through webhook events. Polling with updated-at filters.

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

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

Rate-limit considerations

  • Freshworks CRM: Subject to per-account API rate limits that vary by plan.
  • 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 Freshworks CRM ⇄ Onelogin

Connect Freshworks CRM and Onelogin for flexible, real-time data sync.

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Freshworks CRM and Onelogin.

How the Freshworks CRM and Onelogin connectors work

Freshworks CRM

Integration surface
REST API
Authentication
API key sent as a Token authorization header
Change detection
Polling with updated-at filters; outbound webhooks can be configured through workflow automations
Capabilities
read · write · webhooks
Rate limits
Subject to per-account API rate limits that vary by plan

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

    Choose tables

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

Freshworks CRM 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 520 integrations available for Freshworks CRM and Onelogin.

Popular · 7 of 520
All Freshworks CRM 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