> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt

# Linking Jamf Pro as a source

Canonical URL: https://posthog.com/docs/data-pipelines/sources/jamf-pro

> **Cloud region:** This page uses US Cloud hosts. For an EU Cloud project, use `https://eu.posthog.com` instead of `https://us.posthog.com` or `https://app.posthog.com` (app host for links).

## On this page

- [Prerequisites](#prerequisites)
- [Adding a data source](#adding-a-data-source)
- [Sync modes](#sync-modes)
- [Configuration](#configuration)
- [Supported tables](#supported-tables)
- [Troubleshooting](#troubleshooting)

**Beta release**

This source is currently in **beta**. It works end to end, but you may still hit rough edges. [Let us know](https://us.posthog.com/#panel=support%3Asupport%3Adata_warehouse%3A%3Atrue) if you do.

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_9608fcca70)

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_dark_a92b0e022d)

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.

`npx @posthog/wizard warehouse`

![PostHog Wizard hedgehog](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)

![](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)Let AI connect your sources for you

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

1.  In PostHog, go to the [Sources tab](https://app.posthog.com/data-management/sources) of the data pipeline section.
2.  Click **\+ New source** and click **Link** next to this source.
3.  Enter your credentials (see [Configuration](#configuration) below) and click **Next**.
4.  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)

1.  In Jamf Pro, go to **Settings** > **System** > **API roles and clients**.
2.  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.
3.  On the **API clients** tab, create a client, assign it the role, and click **Enable API client**.
4.  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_at` timestamp). 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](https://posthog.com/docs/data-pipelines/sources.md#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 | — | — |
| `users` | Users in the Jamf Pro inventory, the people that computers and mobile devices are assigned to. | Full refresh | — | — |
| `mdm_commands` | MDM commands Jamf Pro sent to managed devices, with each command's state and result. | Incremental, Full refresh | dateSent | — |
| `managed_software_update_statuses` | Status of managed software (OS) updates on each computer and mobile device. | Incremental, Full refresh | updated | — |
| `patch_software_title_configurations` | Patch management software titles configured in Jamf Pro, with their patch source and packages. | Full refresh | — | — |
| `patch_reports` | Patch report for each software title configuration: one row per computer with the version it has installed. | Full refresh | — | — |
| `patch_summaries` | Patch compliance summary for each software title configuration: latest version and up-to-date versus out-of-date counts. | Full refresh | — | — |
| `patch_policies` | Patch policies that deploy software title updates, with their deployment counts by status. | Full refresh | — | — |
| `patch_policy_logs` | Deployment log for each patch policy: one row per device with its latest deployment status. | Full refresh | — | — |
| `mobile_device_groups` | Smart and static mobile device groups defined in Jamf Pro. | Full refresh | — | — |
| `mobile_device_smart_group_memberships` | Membership of each smart mobile device group: one row per group and member device. | Full refresh | — | — |
| `mobile_device_static_group_memberships` | Membership of each static mobile device group: one row per group and member device. | 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](https://posthog.com/docs/data-warehouse/troubleshooting.md). If that doesn't help, [contact support](https://us.posthog.com/#panel=support%3Asupport%3Adata_warehouse%3A%3Atrue) – we're happy to help.