Linking Jamf Pro as a source
This source is currently in alpha. The interface and available tables may change.
The Jamf Pro connector syncs your Apple device management data – computer inventory, mobile devices, groups, buildings, departments, categories, sites, scripts, and packages – into PostHog.
Prerequisites
You need a Jamf Pro instance (cloud-hosted like yourcompany.jamfcloud.com, or self-hosted) and either an API client or a user account with read access to the objects you want to sync.
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.
When linking Jamf Pro, you'll need your Jamf Pro URL (e.g. yourcompany.jamfcloud.com) and one of the following:
Option 1: API client (recommended)
- In Jamf Pro, go to Settings > System > API roles and clients.
- On the API roles tab, create a role with read privileges for the objects you want to sync, for example: Computers, Mobile Devices, Buildings, Departments, Categories, Sites, Smart Computer Groups, Static Computer Groups, Scripts, and Packages.
- On the API clients tab, create a client, assign it the role, and click Enable API client.
- Copy the client ID and generate a client secret. The secret is only shown once.
Option 2: Username and password
Use a Jamf Pro user account with read access to the objects you want to sync. PostHog only uses the credentials to mint short-lived API tokens.
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.
The computers table supports incremental syncs using the inventory report date, so only computers that submitted inventory since the last sync are fetched. Jamf collects device inventory once a day by default, so syncing more often than every few hours rarely surfaces new data.
Configuration
| Option | Type | Required |
|---|---|---|
Jamf Pro URL | text | Yes |
Authentication method | select | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
computers | Inventory record for each managed computer, including general, hardware, operating system, user and location, security, disk encryption, purchasing, storage, and group membership sections. | Incremental, Full refresh | report_date | — |
mobile_devices | Managed mobile devices (iPhone, iPad, Apple TV) with their identity fields. | Full refresh | — | — |
buildings | Buildings defined in Jamf Pro, used to organize devices and users by physical location. | Full refresh | — | — |
departments | Departments defined in Jamf Pro, used to organize devices and users organizationally. | Full refresh | — | — |
categories | Categories used to organize policies, packages, scripts, and configuration profiles in Jamf Pro. | Full refresh | — | — |
sites | Sites defined in Jamf Pro, used to segment devices, users, and settings across organizational units. | Full refresh | — | — |
computer_groups | Smart and static computer groups defined in Jamf Pro. | Full refresh | — | — |
scripts | Scripts stored in Jamf Pro for use in policies, including their full contents. | Full refresh | — | — |
packages | Software packages stored in Jamf Pro for distribution to managed devices. | Full refresh | — | — |
Troubleshooting
If a sync fails with a permissions error, check that the API role grants the read privilege for each object you selected – Jamf Pro privileges are granted per object type.
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.