Skip to content
Security and identity ⇄ Data warehouse

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

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

Land the users, groups, and access events from Jumpcloud in Snowflake continuously for security analytics, and write computed results back — without building or maintaining a pipeline.

Jumpcloud is the record of who exists and what they can reach; Snowflake is where the business measures everything else. The two overlap on people and their access — the same users, groups, roles, and events that Jumpcloud governs are what security, compliance, and analytics teams want to query in Snowflake. Getting them there usually means a brittle export that runs overnight and hands auditors a snapshot that is already out of date.

Stacksync syncs User Groups, Systems (devices), System Groups, Applications (SSO) from Jumpcloud into tables in Snowflake in real time, and the connection works in both directions: values computed in Snowflake, such as risk scores or access-review decisions, can be written back to attributes in Jumpcloud where the identity team acts on them. Schema changes are handled, API limits are managed, and the sync is something you configure rather than a pipeline you keep alive.

Common use cases

  • 01 Activate modeled Snowflake tables by syncing scores and attributes back into CRM fields sales can act on
  • 02 Keep a customer 360 table aligned with its source systems in both directions instead of one-way reverse ETL
  • 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

Queryable history for audit and compliance

A continuously synced copy in Snowflake gives you a durable, queryable record of identity and access state for access reviews, SOC 2, and audit questions.

Risk and review results back on the account

Risk scores, anomaly flags, or access-review outcomes computed in Snowflake write back to attributes on the matching user in Jumpcloud, where the identity team can act on them.

Directory data in the warehouse, minus the pipeline

Users, groups, and roles from Jumpcloud arrive in Snowflake as queryable tables, current within seconds instead of a nightly directory export.

What you can sync between Jumpcloud and Snowflake

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 Snowflake 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. Tasks Scheduled SQL used to transform synced data after it lands. Commands is specific to Jumpcloud and Tasks to Snowflake — 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. VARIANT Columns Semi-structured JSON payloads stored alongside relational columns. Directory Insights events is specific to Jumpcloud and VARIANT Columns to Snowflake — 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. Virtual Warehouses The compute a sync's queries run on, sized independently of storage. System Users (Users) is specific to Jumpcloud and Virtual Warehouses to Snowflake — 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. Databases Top-level containers that scope which data a sync can touch. User Groups is specific to Jumpcloud and Databases to Snowflake — 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. Schemas Namespaces within a database used to organize synced tables. Systems (devices) is specific to Jumpcloud and Schemas to Snowflake — 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. Tables The main landing and activation target for synced records. System Groups is specific to Jumpcloud and Tables to Snowflake — each maps to any object or custom field on the other side.

How changes propagate between Jumpcloud and Snowflake

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

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

DeliveryEach detected change is applied to Snowflake as a row-level write, with types converted between the two schemas.

Snowflake Jumpcloud Sub-second propagation

DetectionChanges in Snowflake are captured at the source via change data capture — no polling loop against its API. The setup script grants "create stream" on synced schemas (Snowflake streams), but the docs do not name the change-capture mechanism.

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.
  • Snowflake: No conventional API rate limits; cost and throughput are governed by virtual warehouse size and running time.
What ships with Jumpcloud ⇄ Snowflake

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

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

Snowflake

Integration surface
SQL via JDBC/ODBC and native drivers, plus the Snowflake SQL REST API
Authentication
Dedicated Snowflake service user + role with RSA key-pair authentication (Stacksync-provided public key), created via a setup script requiring SECURITY_ADMIN and ACCOUNTADMIN roles
Change detection
Not explicitly stated; the setup script grants "create stream" on synced schemas (Snowflake streams), but the docs do not name the change-capture mechanism
Capabilities
read · write · CDC
Rate limits
No conventional API rate limits; cost and throughput are governed by virtual warehouse size and running time
Snowflake setup guide
How it works

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

    Choose tables

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

Jumpcloud and Snowflake 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 545 integrations available for Jumpcloud and Snowflake.

Popular · 7 of 545
All Jumpcloud integrations All Snowflake 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