Skip to content
CRM ⇄ Security and identity

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

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

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

A CRM and an identity system usually describe different populations. Folk 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 Folk CRM are the same employees Onelogin provisions and disables, and when Onelogin also runs the login accounts for your product, the customers in Folk CRM are the same users Onelogin authenticates. Left unconnected, a departure in Onelogin leaves stale ownership sitting in Folk CRM, and a signup in Onelogin never reaches the account it belongs to.

Stacksync syncs Groups, Custom fields, Notes, Reminders in Folk 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 Sync folk people and companies with a marketing or outbound tool so outreach lists stay current.
  • 02 Push enriched contact data from a data warehouse into folk custom fields.
  • 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

Where a closed deal should provision access: Folk CRM drives Onelogin

A won or activated customer in Folk CRM can create or update the corresponding user or account in Onelogin, so provisioning starts from the CRM record instead of a separate ticket.

Where Onelogin governs your workforce: CRM users kept current

New employees in Onelogin become active users in Folk CRM with the right role, and group or department changes update their access and team, so the CRM's user list matches the directory without an admin re-keying it.

Deactivation and record hand-off

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

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

Folk CRM objects Onelogin objects How this pairing syncs
Groups Shared workspaces that organize contacts; group membership is often the field integrations act on. 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. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Custom fields Group-scoped attributes that receive enriched or computed values from external systems. Apps (app instances) Connected SAML/OIDC application configs on the account; create, update, delete, and assign to users and roles - the writable app catalog. Custom fields is specific to Folk CRM and Apps (app instances) to Onelogin — each maps to any object or custom field on the other side.
Notes Free-text context attached to people and companies, readable for reporting. Mappings (mapping rules) Attribute-driven rules that assign roles and app access; full CRUD via the Mappings API, then reapplied across matching users. Notes is specific to Folk CRM and Mappings (mapping rules) to Onelogin — each maps to any object or custom field on the other side.
Reminders Follow-up items that can be created from external triggers. Events Audit log of every authentication and admin action; read-only, filtered by since/until, and pushed live through the Event Webhook. Reminders is specific to Folk CRM and Events to Onelogin — each maps to any object or custom field on the other side.
People Contact records; the primary entity synced with outreach and enrichment tools. 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 Folk CRM and Authentication factors (MFA) to Onelogin — each maps to any object or custom field on the other side.
Companies Organization records linked to people and kept aligned with billing or CS systems. Custom user fields Account-level custom attributes on the User record; read and written alongside the standard user profile fields. Companies is specific to Folk CRM and Custom user fields to Onelogin — each maps to any object or custom field on the other side.

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

Folk CRM Onelogin Sub-second propagation

DetectionFolk CRM notifies Stacksync of record changes through webhook events. Webhook subscriptions for record events, with polling of list endpoints as a fallback.

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

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

Rate-limit considerations

  • Folk CRM: Subject to the platform's API rate limits.
  • 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 Folk CRM ⇄ Onelogin

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Folk 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 Folk CRM and Onelogin.

How the Folk CRM and Onelogin connectors work

Folk CRM

Integration surface
REST API
Authentication
API key (Bearer token)
Change detection
Webhook subscriptions for record events, with polling of list endpoints as a fallback
Capabilities
read · write · webhooks
Rate limits
Subject to the platform's API rate limits

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

    Choose tables

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

Folk 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 414 integrations available for Folk CRM and Onelogin.

Popular · 7 of 414
All Folk 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