Salesforce logo ↔ Okta logo

How to Integrate Salesforce with Okta

Native vs. Make vs. n8n vs. Zapier: setup time, cost, and field mapping

Guide last updated: November 12, 2026

Integration Status

Salesforce (CRM) has a native integration with Okta (Development). This built-in connection handles standard sync scenarios without additional automation tools.

Native integrationVerified Nov 2026

Salesforce and Okta: native integration

Mechanism
Okta Salesforce provisioning integration
Data direction
Both directions (Salesforce ↔ Okta)
What syncs
  • New Okta users pushed to Salesforce
  • Okta profile updates pushed to Salesforce
  • Okta deactivation deactivates the Salesforce user
  • Salesforce users imported into Okta
  • Salesforce profile updates imported into Okta
  • Salesforce user accounts reactivated
Limits
The supported features page states no edition or license requirements. Create, update, and deactivate options must be turned on in the app's provisioning settings, otherwise provisioning fails.
Sources
Checked

Data Flow Architecture

Salesforce Salesforce
→ One-Way
Standard API Latency
Okta Okta
API Tier
REST API v3
Auth Method
OAuth 2.0
Rate Limits
Standard SaaS Limits

Import a ready-made workflow template

Copy this Salesforce → Okta blueprint, open Make.com, paste it into the canvas, and your workflow is ready to configure.

Make.com
salesforce-okta-blueprint.json
{
  "name": "Salesforce → Okta Sync",
  "flow": [
    {
      "id": 1,
      "module": "salesforce:WatchRecords",
      "version": 1,
      "parameters": {},
      "mapper": {},
      "metadata": {
        "designer": {
          "x": 0,
          "y": 0
        },
        "restore": {},
        "expect": [
          {
            "name": "body",
            "type": "text",
            "label": "Body"
          }
        ]
      }
    },
    {
      "id": 2,
      "module": "http:ActionSendData",
      "version": 1,
      "parameters": {
        "url": "https://api.okta.com/v1/records"
      },
      "mapper": {},
      "metadata": {
        "designer": {
          "x": 300,
          "y": 0
        }
      }
    }
  ],
  "metadata": {
    "instant": false,
    "version": 1,
    "scenario": {
      "roundtrips": 1,
      "maxErrors": 3,
      "autoCommit": true,
      "sequential": false
    }
  }
}

Frequently Asked Questions

Is the connection between Salesforce and Okta secure? ▼

Yes. This integration typically uses OAuth 2.0, meaning you grant permission via a secure login window. You do not need to share your raw password, and you can revoke access at any time from your Salesforce security settings.

Is the sync one-way or two-way? ▼

This is typically a one-way sync: Salesforce → Okta. Changes in Okta do not sync back to Salesforce.

Will existing data in Salesforce sync to Okta? ▼

Usually, no. Most native integrations are "forward-looking," meaning they only sync data created or updated *after* you activate the connection. To move historical data, you will likely need to perform a one-time CSV export/import manually.

Can I sync custom fields? ▼

Native integration is limited to standard fields. For custom field mapping, use an automation tool.

Can I add approval steps before syncing? ▼

Native integrations can't do this. For workflows that need human review (e.g., "Manager must approve before creating invoice"), use Make or n8n to pause the workflow on a webhook or Slack approval before it continues.

Using Salesforce and Okta with other tools?

Build your full stack map, see all connections and gaps at once.

See your full stack →