Skip to content
Security and identity

Connect Jumpcloud to any app with two-way sync.

Two-way sync Jumpcloud across all your CRMs, databases, data warehouses, EDI systems, and AI tools, with custom workflows tailored to your data.

  • 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
Object catalog

What Stacksync syncs in Jumpcloud.

These objects sync between Jumpcloud and any connected system, with field-level mapping and conflict resolution. Custom fields are picked up from the live schema where Jumpcloud exposes them.

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.
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.
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.
System Groups
device groups used to scope policies, commands, and access; full CRUD via v2 /systemgroups, with systems bound and unbound through association endpoints.
Applications (SSO)
SAML and OIDC SSO app configs; read via v2 /applications and their user/group assignments created and removed to control who can reach each connected app.
Policies
device configuration and MDM policies; read, created from templates, and updated via v2 /policies, then bound to systems and system groups to enforce settings across the fleet.
Commands
scripts and commands run on managed systems; full CRUD via v1 /commands, then triggered on target systems and groups for automation and remediation.
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.
API surface

How Stacksync connects to Jumpcloud.

The connector runs on Jumpcloud's native API. Stacksync manages authentication, rate limits, retries, and schema changes so your team does not maintain integration code.

Connection
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.
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.

Sync directions

  • Read Supported
  • Write Supported
  • Change data capture Not available
  • Webhooks Supported
What ships with Jumpcloud

Connect Jumpcloud for flexible, real-time data sync.

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

Real-time

Two-way sync

Changes in Jumpcloud instantly reflect across connected systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions.

Use cases

What teams run on the Jumpcloud connector.

JumpCloud is the cloud directory platform mid-market and MSP-managed organizations use as the system of record for users, the devices they log into, and the SSO apps, LDAP, and RADIUS resources they reach. Owned by IT and identity teams and watched by security and compliance, it holds the System Users, User Groups, Systems, Applications, and Policies that gate access across a fleet, plus a Directory Insights audit log of every login and admin action - the records provisioning, deprovisioning, and device-governance workflows read from and write back to.

  • IT and IAM administrators
  • Identity and device management engineers
  • Security and compliance (GRC) teams
  • IT operations
  • Managed service providers (MSPs)

  1. Provision, update, and deprovision System Users in JumpCloud from Workday or another HRIS so directory identities follow onboarding, role changes, and offboarding automatically.

  2. 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.

  3. Read Directory Insights events into Postgres or a warehouse for access reviews, login analytics, and SOC 2 audit evidence beyond JumpCloud's retention window.

  4. Read Systems and System Group memberships into a database for device inventory, patch reporting, and conditional-access analysis.

  5. Drive Application and Policy assignments from HR attributes or entitlement tables so SSO access and device policies change the moment a role does.

  6. Provision and deprovision System Users and User Group memberships from Workday or another HRIS so a new hire lands in the right JumpCloud groups, apps, and devices on day one and loses all access at offboarding the moment HR updates the record.

All Jumpcloud integrations

Pick the system you need to keep in sync with Jumpcloud. Each page covers the sync setup, field mapping, and common workflows for that pair.

CRM · 41

ERP · 37

Database · 50

Data warehouse · 28

Business productivity · 37

Accounting and finance · 17

How it works

Set up Jumpcloud in minutes, without APIs.

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 with its 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
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Jumpcloud objects to sync — Stacksync auto-detects the schema, 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
    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 database
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo

FAQ

Jumpcloud connector FAQ

What can I sync with the Jumpcloud connector?

Jumpcloud's core objects — System Users (Users), User Groups, Systems (devices), System Groups and custom fields — can sync with any of 302 other systems. Every integration is real-time and bidirectional, with field-level mapping and conflict resolution.

How does Stacksync connect to Jumpcloud?

Via 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., authenticated with 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.. Changes are detected as follows — 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.. Stacksync manages rate limits, retries, and schema changes automatically.

Is the Jumpcloud connector two-way?

Yes. Changes made in Jumpcloud propagate to the connected system and vice versa, in milliseconds. One-way flows are also supported when a direction should stay read-only.

How long does a Jumpcloud integration take to set up?

Most Jumpcloud integrations go live in minutes: authenticate Jumpcloud and the other system, pick objects and fields, and enable the sync. No code and no infrastructure to manage.

Is Jumpcloud data secure in transit?

Stacksync is SOC 2 Type II, ISO 27001, GDPR and HIPAA compliant. Jumpcloud data is encrypted in transit, and a zero-persistent-storage architecture means records are not retained after a sync operation.

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
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