Skip to content
Security and identity ⇄ CRM

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

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

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

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

Stacksync syncs Tasks and Events, Products and Price Books, Custom Objects, Accounts in Salesforce with User Groups, Systems (devices), System Groups, Applications (SSO) in Jumpcloud 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 Trigger provisioning or billing changes in an operational database when an Opportunity moves to closed-won.
  • 02 Consolidate multiple Salesforce orgs into a single database for cross-org reporting after an acquisition.
  • 03 Drive Application and Policy assignments from HR attributes or entitlement tables so SSO access and device policies change the moment a role does.
  • 04 Two-way sync User Groups and their memberships between JumpCloud and a source-of-truth database so app, LDAP, and RADIUS access stays aligned with org data.

Common sync patterns

Where a closed deal should provision access: Salesforce drives Jumpcloud

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

Where Jumpcloud governs your workforce: CRM users kept current

New employees in Jumpcloud 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 Jumpcloud, 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.

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

Jumpcloud objects Salesforce objects How this pairing syncs
Commands Scripts and commands run on managed systems; full CRUD via v1 /commands, then triggered on target systems and groups for automation and remediation. Opportunities Deal records with stage and amount; synced to databases for pipeline reporting and to ERPs at close. Commands is specific to Jumpcloud and Opportunities to Salesforce — each maps to any object or custom field on the other side.
Directory Insights events Audit stream of logins and admin actions across SSO, LDAP, RADIUS, systems, and MDM; read-only, queried by POST and used as the change feed and SIEM source. Cases Support records; synced with help desk tools or internal databases for escalation workflows. Directory Insights events is specific to Jumpcloud and Cases to Salesforce — each maps to any object or custom field on the other side.
System Users (Users) Directory user accounts (email, username, attributes, status, MFA, group and app bindings); full CRUD via the v1 /systemusers API - create, update, activate or suspend, and delete to match an HR or identity source. Campaigns Marketing membership data; read out for attribution analysis in the warehouse. System Users (Users) is specific to Jumpcloud and Campaigns to Salesforce — each maps to any object or custom field on the other side.
User Groups User groups that grant app, LDAP, and RADIUS access; created, updated, and deleted via v2 /usergroups, with membership managed through the graph association endpoints. Tasks and Events Activity records; usually read-only in syncs to feed activity reporting. User Groups is specific to Jumpcloud and Tasks and Events to Salesforce — each maps to any object or custom field on the other side.
Systems (devices) Enrolled macOS, Windows, and Linux machines running the JumpCloud agent; agent-enrolled, so the API reads, updates, and deletes systems for inventory and management rather than creating them. Products and Price Books Catalog and pricing data; commonly mastered in an ERP and written into Salesforce. Systems (devices) is specific to Jumpcloud and Products and Price Books to Salesforce — each maps to any object or custom field on the other side.
System Groups Device groups used to scope policies, commands, and access; full CRUD via v2 /systemgroups, with systems bound and unbound through association endpoints. Custom Objects Org-specific tables with the __c suffix; discoverable via describe metadata so field mappings can be generated. System Groups is specific to Jumpcloud and Custom Objects to Salesforce — each maps to any object or custom field on the other side.

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

Jumpcloud Salesforce Sub-second propagation

DetectionJumpcloud notifies Stacksync of record changes through webhook events. No database-style change log.

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

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

Rate-limit considerations

  • Jumpcloud: JumpCloud rate-limits API requests and returns HTTP 429 (Rate limit exceeded) when a client sends requests too quickly; its guidance is to back off and retry at a lower rate. Specific per-minute ceilings are not published, and the Directory Insights API is metered separately. Webhook deliveries are retried three times with exponential backoff on 5xx, 408, or 429 responses.
  • Salesforce: Daily API request allocations vary by edition and license count.
What ships with Jumpcloud ⇄ Salesforce

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Jumpcloud and Salesforce connectors work

Jumpcloud

Integration surface
JumpCloud REST API - v1 (console.jumpcloud.com/api) for Systems, System Users, and Commands; v2 (/api/v2) for User Groups, System Groups, Applications, Policies, and resource associations; plus the Directory Insights API (api.jumpcloud.com/insights/directory/v1/events) and Webhook Channels for outbound events.
Authentication
Admin API key sent in the x-api-key header (keys are prefixed jca_, generated in the console with a 30-365 day expiry, and disabled for admins by default until enabled); an x-org-id header scopes calls to a single organization for MSP multi-tenant admins. System Context authorization (HMAC-signed) also exists for agent-run calls.
Change detection
No database-style change log. The Directory Insights API is queried by POST for login and admin events across SSO, LDAP, RADIUS, systems, MDM, and directory services - including the association_change event that records user-to-group and policy-to-device membership changes; Webhook Channels tied to Insights Rules POST JSON to a registered endpoint for near-real-time triggers.
Capabilities
read · write · webhooks
Rate limits
JumpCloud rate-limits API requests and returns HTTP 429 (Rate limit exceeded) when a client sends requests too quickly; its guidance is to back off and retry at a lower rate. Specific per-minute ceilings are not published, and the Directory Insights API is metered separately. Webhook deliveries are retried three times with exponential backoff on 5xx, 408, or 429 responses.

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

    Choose tables

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

Jumpcloud 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 Jumpcloud and Salesforce.

Popular · 7 of 535
All Jumpcloud 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