Skip to content
Security and identity ⇄ CRM

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

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

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

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

Stacksync syncs Notes, Products, Tags, Users in Nutshell with Systems (devices), System Groups, Applications (SSO), Policies 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 Write subscription or product data from internal systems into Nutshell so reps see account context.
  • 02 Mirror tasks and activities into ops tools for cross-team visibility.
  • 03 Read Directory Insights events into Postgres or a warehouse for access reviews, login analytics, and SOC 2 audit evidence beyond JumpCloud's retention window.
  • 04 Read Systems and System Group memberships into a database for device inventory, patch reporting, and conditional-access analysis.

Common sync patterns

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

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

Group and entitlement membership as CRM fields

Membership of a directory group or an entitlement in Jumpcloud maps to fields in Nutshell, such as product tier, plan, or internal team, so segmentation reflects real access rather than a manual guess.

Where a closed deal should provision access: Nutshell drives Jumpcloud

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

What you can sync between Jumpcloud and Nutshell

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 Nutshell objects How this pairing syncs
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. Activities Logged calls, meetings, and emails used for engagement reporting Applications (SSO) is specific to Jumpcloud and Activities to Nutshell — each maps to any object or custom field on the other side.
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. Tasks Rep to-dos mirrored into external work-management or reporting systems Policies is specific to Jumpcloud and Tasks to Nutshell — each maps to any object or custom field on the other side.
Commands Scripts and commands run on managed systems; full CRUD via v1 /commands, then triggered on target systems and groups for automation and remediation. Notes Free-text history attached to leads and contacts, replicated for a full timeline Commands is specific to Jumpcloud and Notes to Nutshell — 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. Products Line items attached to leads, used to sync sold products into billing Directory Insights events is specific to Jumpcloud and Products to Nutshell — 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. Tags Segmentation labels mapped to lists or filters in downstream tools System Users (Users) is specific to Jumpcloud and Tags to Nutshell — 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. Users Rep records used to resolve ownership when syncing assignments User Groups is specific to Jumpcloud and Users to Nutshell — each maps to any object or custom field on the other side.

How changes propagate between Jumpcloud and Nutshell

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 Nutshell Sub-second propagation

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

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

Nutshell Jumpcloud Sub-second propagation

DetectionNutshell notifies Stacksync of record changes through webhook events. Webhook subscriptions for record events, with polling as fallback.

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.
  • Nutshell: Subject to the platform's API rate limits.
What ships with Jumpcloud ⇄ Nutshell

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Jumpcloud ⇄ Nutshell 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 Nutshell.

How the Jumpcloud and Nutshell 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.

Nutshell

Integration surface
JSON-RPC API over HTTPS; a newer REST API is also offered
Authentication
HTTP Basic with account email and API key
Change detection
webhook subscriptions for record events, with polling as fallback
Capabilities
read · write · webhooks
Rate limits
subject to the platform's API rate limits
How it works

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

    Choose tables

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

Jumpcloud and Nutshell 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 418 integrations available for Jumpcloud and Nutshell.

Popular · 7 of 418
All Jumpcloud integrations All Nutshell 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