Linking JumpCloud as a source
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.
This source is currently in alpha. The interface and available tables may change.
The JumpCloud connector syncs users, systems, user groups, and more into the PostHog data warehouse, so you can analyze them alongside your product data.
Prerequisites
Credentials that can read the data you want to sync. PostHog only reads data, so read access is enough.
Adding a data source
- In PostHog, go to the Sources tab of the data pipeline section.
- Click + New source and click Link next to this source.
- Enter your credentials (see Configuration below) and click Next.
- Select the tables you want to sync, choose a sync method and frequency, then click Import.
Once the syncs are complete, you can start querying this data in PostHog.
Enter your JumpCloud admin API key to sync your directory and activity data.
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.
You'll be asked for:
- API key
- Region: choose between US (console.jumpcloud.com) and EU (console.eu.jumpcloud.com).
Sync modes
Each table can be synced in one of several modes, depending on what the source supports:
- Webhook (when available) – the source pushes changes to PostHog in real time. Fastest freshness, lowest ongoing cost, and the only mode that reliably captures updates and deletes.
- Incremental – only new or updated rows are synced on each run, using a cursor field (such as an
updated_attimestamp). Cheaper than a full refresh, but deletes aren't captured. - Append only – new rows are appended using a cursor field; existing rows are never updated. Ideal for immutable, append-only tables like event logs.
- Full refresh – the whole table is reloaded on every sync. Use it when a table has no reliable cursor or when you need deletions reflected.
See sync methods for a full explanation of how each mode works and how to choose between them.
All JumpCloud tables are full refresh. Each sync replaces the contents of the table.
Configuration
| Option | Type | Required |
|---|---|---|
API key | password | Yes |
Region | select | Yes |
Organization ID (optional, MSP/MTP only) | text | No |
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 |
user_group_members | Users that are members of each user group, one row per group and user. | Full refresh | — | group_id, id |
system_group_members | Systems that are members of each system group, one row per group and system. | Full refresh | — | group_id, id |
application_users | Users bound to each SSO application, directly or through a user group. | Full refresh | — | application_id, id |
application_user_groups | User groups bound to each SSO application. | Full refresh | — | application_id, id |
system_users | Users bound to each system, directly or through a user or system group, so they can log in to it. | Full refresh | — | system_id, 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 |
Troubleshooting
- If the connection fails with an authorization error, the API key is wrong, expired, or has been revoked. Create a new one, then reconnect the source.
- If a table syncs no rows, the credential may not have access to that data. Check its permissions, then reconnect the source.
If your sync is failing or data looks wrong, see the Data warehouse troubleshooting guide. If that doesn't help, contact support – we're happy to help.