JumpCloud
Let AI connect your sources for you
Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.
Connect JumpCloud to PostHog to sync your data into the PostHog data warehouse for analysis and modeling.
Enter your JumpCloud admin API key to sync your directory and activity data into the PostHog Data warehouse.
Find your API key in the JumpCloud Admin Portal: click your account initials in the top-right corner and select My API Key.
The events table requires a Directory Insights subscription. If you're an MSP/MTP admin managing multiple organizations, also enter the organization ID the key should act on.
Configuration
| Option | Type | Required |
|---|---|---|
API key | password | Yes |
Region | select | Yes |
Organization ID (optional, MSP/MTP only) | text | No |
Linking JumpCloud to PostHog
- Go to the Data pipeline page in PostHog
- Click New source and select JumpCloud
- Fill in the required configuration fields
- Click Next, select the tables you want to sync, and then press Import
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
users | User identities in the JumpCloud directory, including their account state and profile attributes. | Full refresh | — | _id |
systems | Devices (workstations and servers) managed by the JumpCloud agent. | Full refresh | — | _id |
user_groups | User groups used to grant collections of users access to resources (apps, systems, networks). | Full refresh | — | id |
system_groups | Device groups used to apply policies and access to collections of systems. | Full refresh | — | id |
applications | SSO applications configured in JumpCloud (SAML, OIDC, and bookmark apps). | Full refresh | — | _id |
events | Directory Insights activity events (console, SSO, RADIUS, LDAP, systems, and directory changes). Only syncs the last 90 days on initial sync, bounded by your Directory Insights retention | Incremental, Full refresh | timestamp | id |