Skip to content
Security and identity ⇄ CRM

Okta to Salesforce integration — real-time, two-way sync

Keep Okta and Salesforce 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 Okta and Salesforce

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

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

Stacksync syncs Accounts, Contacts, Leads, Opportunities in Salesforce with Policies, System Log, Devices, Users in Okta 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 Accounts, Contacts, and Opportunities bi-directionally with Postgres so engineering teams read and write CRM data with plain SQL.
  • 02 Write product usage metrics computed in a warehouse onto Account and Contact fields so reps see adoption signals on the record.
  • 03 Read Application assignments and Factors into a database to report on who can reach which app and which users have strong MFA enrolled.
  • 04 Drive Group Rules and policy assignments from HR attributes so access changes the moment a title, department, or location changes.

Common sync patterns

Where Okta governs your workforce: CRM users kept current

New employees in Okta become active users in Salesforce 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 Okta, the matching user in Salesforce is deactivated too, and the accounts, contacts, and deals they owned are flagged for reassignment, so nothing goes unattended after they leave.

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

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

What you can sync between Okta and Salesforce

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.

Okta objects Salesforce objects How this pairing syncs
Group Rules Dynamic rules that add users to groups from profile attributes; read and written to automate access based on department, title, or location. Campaigns Marketing membership data; read out for attribution analysis in the warehouse. Group Rules is specific to Okta and Campaigns to Salesforce — each maps to any object or custom field on the other side.
Factors (Authenticators) MFA enrollments per user (Okta Verify, WebAuthn, SMS, email); read for security-posture reporting and reset when a device is lost or rotated. Tasks and Events Activity records; usually read-only in syncs to feed activity reporting. Factors (Authenticators) is specific to Okta and Tasks and Events to Salesforce — each maps to any object or custom field on the other side.
Policies Sign-on, password, and authenticator-enrollment policies with their rules; read to audit access controls or updated to manage them centrally. Products and Price Books Catalog and pricing data; commonly mastered in an ERP and written into Salesforce. Policies is specific to Okta and Products and Price Books to Salesforce — each maps to any object or custom field on the other side.
System Log Immutable audit event stream of logins, admin changes, and lifecycle events; read-only, polled by timestamp and used as the change feed and SIEM source. Custom Objects Org-specific tables with the __c suffix; discoverable via describe metadata so field mappings can be generated. System Log is specific to Okta and Custom Objects to Salesforce — each maps to any object or custom field on the other side.
Devices Registered and managed device records tied to users; read to correlate access with device posture and to feed inventory or conditional-access reporting. Accounts Company records that anchor most syncs; typically mapped to customer tables in a database or ERP. Devices is specific to Okta and Accounts to Salesforce — each maps to any object or custom field on the other side.
Users Universal Directory user records with profile attributes, credentials, and lifecycle status (staged, active, suspended, deprovisioned); full CRUD, so users are created, updated, activated, and deactivated to match an HR or identity source. Contacts People linked to Accounts; synced two-way with marketing, support, and warehouse person records. Users is specific to Okta and Contacts to Salesforce — each maps to any object or custom field on the other side.

How changes propagate between Okta and Salesforce

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.

Okta Salesforce Sub-second propagation

DetectionOkta notifies Stacksync of record changes through webhook events. Event Hooks send an HTTPS POST to a subscribed endpoint on events such as user.lifecycle.create and group.user_membership.add (after a one-time.

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

Salesforce Okta Sub-second propagation

DetectionChanges in Salesforce are captured at the source via change data capture — no polling loop against its API. Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting).

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

Rate-limit considerations

  • Okta: Rate limits are enforced per org, per endpoint group, per minute and vary by Okta edition; responses carry X-Rate-Limit-Limit, X-Rate-Limit-Remaining, and X-Rate-Limit-Reset headers and exceeding one returns HTTP 429. The System Log is more tightly limited (about 120 requests/minute) and a separate concurrent-request cap (default 75 in-flight transactions) also applies.
  • Salesforce: Daily API request allocations vary by edition and license count.
What ships with Okta ⇄ Salesforce

Connect Okta and Salesforce for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Okta–Salesforce connection.

Real-time

Two-way sync

Changes in Okta or Salesforce instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Okta or Salesforce 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 Okta or Salesforce record.

Observability

Monitoring

Track your Okta ⇄ Salesforce sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Okta and Salesforce.

How the Okta and Salesforce connectors work

Okta

Integration surface
REST API (Okta Management API, /api/v1) with Event Hooks for outbound events and the System Log API as the change feed
Authentication
SSWS API tokens (Authorization: SSWS {token}) scoped to the creating admin's permissions, or OAuth 2.0 for Okta service apps using a private-key-JWT client-credentials grant with granular scopes (DPoP supported)
Change detection
Event Hooks send an HTTPS POST to a subscribed endpoint on events such as user.lifecycle.create and group.user_membership.add (after a one-time verification handshake); the System Log API (/api/v1/logs) is polled by the since parameter and the next Link header for a near-real-time change feed
Capabilities
read · write · webhooks
Rate limits
Rate limits are enforced per org, per endpoint group, per minute and vary by Okta edition; responses carry X-Rate-Limit-Limit, X-Rate-Limit-Remaining, and X-Rate-Limit-Reset headers and exceeding one returns HTTP 429. The System Log is more tightly limited (about 120 requests/minute) and a separate concurrent-request cap (default 75 in-flight transactions) also applies.

Salesforce

Integration surface
REST, SOAP, and Bulk APIs
Authentication
OAuth login via a Salesforce user (browser-based authorization flow); requires "API Enabled" permission for polling mode, plus "Author Apex" and "Customize Application" OR "Modify All Data" for trigger mode
Change detection
Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting)
Capabilities
read · write · CDC
Rate limits
Daily API request allocations vary by edition and license count.
Salesforce setup guide
How it works

How to connect Okta to Salesforce — 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 Okta and Salesforce 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
    Okta connected
    Salesforce connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

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

Okta and Salesforce 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 535 integrations available for Okta and Salesforce.

Popular · 8 of 535
All Okta integrations All Salesforce 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