Skip to content
Book a demoStart free
Connectors

Jamf Pro connector

Set up the Jamf Pro connector in Kaivo: authentication, configuration, the 1 BigQuery tables it syncs, and answers to common questions.

Jamf Pro connector pricing, tier and credits on kaivo.io

Kaivo is a fully managed data platform that syncs your Jamf Pro data into a Google BigQuery warehouse and keeps it up to date automatically. There is no pipeline to build and no infrastructure to run, so you can spend your time analysing your data from Jamf Pro instead of moving it.

Sync your Jamf Pro device data into BigQuery with Kaivo to inventory and report on your managed computers.

CategoryTech
AuthenticationUsername and password
SetupSelf-service

Getting started with the Jamf Pro connector

Section titled “Getting started with the Jamf Pro connector”
  1. Sign up for Kaivo and create a workspace.
  2. Connect your Jamf Pro account.
  3. Choose which tables to sync.
  4. Wait for the initial sync to finish.
  5. Query your data in BigQuery or your favourite AI or BI tool.

Connect with your Jamf Pro login. You provide:

Field Description
Password
Your Jamf Pro password.

|

When you set up the connector, you provide:

Field Description
Subdomain
The unique subdomain for your Jamf Pro instance.

| | Username |

Your Jamf Pro username.

|

Kaivo syncs 1 table from Jamf Pro into a dedicated dataset in your BigQuery warehouse. Click any table to see its columns and types.

computers (29 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
general__declarative_device_management_enabled BOOL
general__enrolled_via_automated_device_enrollment BOOL
general__enrollment_method__id STRING
general__enrollment_method__object_name STRING
general__enrollment_method__object_type STRING
general__initial_entry_date STRING
general__itunes_store_account_active BOOL
general__jamf_binary_version STRING
general__last_contact_time STRING
general__last_enrolled_date STRING
general__last_ip_address STRING
general__last_reported_ip STRING
general__management_id STRING
general__mdm_capable__capable BOOL
general__mdm_profile_expiration STRING
general__name STRING
general__platform STRING
general__remote_management__managed BOOL
general__report_date STRING
general__site__id STRING
general__site__name STRING
general__supervised BOOL
general__user_approved_mdm BOOL
id STRING
last_contact_time STRING
name STRING
udid STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
Column Type Description
_kaivo_parent_id STRING Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo.
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
value STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: computers__general__extension_attributes

Section titled “Subtable: computers__general__extension_attributes”
Column Type Description
_kaivo_parent_id STRING Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo.
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
description STRING
data_type STRING
definition_id STRING
enabled BOOL
input_type STRING
multi_value BOOL
name STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: computers__general__extension_attributes__options

Section titled “Subtable: computers__general__extension_attributes__options”
Column Type Description
_kaivo_parent_id STRING Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo.
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
value STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: computers__general__extension_attributes__values

Section titled “Subtable: computers__general__extension_attributes__values”
Column Type Description
_kaivo_parent_id STRING Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo.
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
value STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: computers__general__mdm_capable__capable_users

Section titled “Subtable: computers__general__mdm_capable__capable_users”
Column Type Description
_kaivo_parent_id STRING Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo.
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
value STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

After the first load, Kaivo keeps your BigQuery warehouse up to date for you. Where Jamf Pro supports it, each sync pulls only new and changed records so it stays fast; otherwise it refreshes the whole table. Every record keeps its original ID, so you won’t get duplicate rows.

How long does the initial sync take for Jamf Pro?

Section titled “How long does the initial sync take for Jamf Pro?”

It depends on how much history is in your Jamf Pro account. Most initial syncs finish within minutes, while large accounts can take a few hours. After that, syncs only fetch new and changed records, so they’re much faster.

Yes. You pick which tables to sync when you set up the connection and can change the selection later. Tables you don’t select are never copied to your warehouse.

What happens when Jamf Pro’s schema changes?

Section titled “What happens when Jamf Pro’s schema changes?”

New fields are never added automatically. You choose which fields to sync, so data you haven’t selected (sensitive personal data, for example) never lands in your warehouse. When a new field appears, it becomes available for you to add. What happens to removed or renamed fields depends on a table’s sync mode: full-refresh tables always match what’s currently in Jamf Pro, so dropped fields disappear, while incremental tables keep their existing columns and history, so an old field stays and newly added fields fill in over time.

How do I handle GDPR or data deletion requests?

Section titled “How do I handle GDPR or data deletion requests?”

Your data lives in your own Kaivo-managed BigQuery warehouse, so the most direct option is to delete or anonymise specific records right in BigQuery. If you delete data in Jamf Pro instead, full-refresh tables drop it on the next sync, while incremental tables keep it, so you would remove the row in BigQuery or ask us to run a full refresh. To remove everything, delete the Jamf Pro connector in Kaivo and all of its synced data is deleted with it.

Use computers to report on your managed fleet and its configuration.

Analyse computer data to find devices that need updates or attention.

Bring device data into BigQuery to report on it next to your other IT data.

Once Jamf Pro data lands in your Kaivo-managed BigQuery warehouse, you can explore it with AI tools or any BI tool that connects to BigQuery. Here’s how the most common destinations work with Jamf Pro data.

Use Kaivo’s MCP server to give Claude secure, workspace-scoped access to your data. Setup guide →

Microsoft’s BI tool with a native BigQuery connector. Supports direct query and scheduled refresh. Setup guide →

Free Google BI tool with native BigQuery support. One-click connection to your Kaivo warehouse; great for SMB teams on Google Workspace. Setup guide →

The premium analytics standard, with native BigQuery integration. Setup guide →

Use Connected Sheets to query BigQuery directly from a spreadsheet, with no SQL. Setup guide →

Connect via Power Query’s BigQuery connector. Setup guide →

Open-source BI tool with strong BigQuery support. Setup guide →

See our pricing page for Jamf Pro connector pricing and plan details.

  • Adform: Sync Adform to BigQuery.
  • Amplitude: Sync Amplitude to BigQuery.
  • Auth0: Sync Auth0 to BigQuery.
  • Convex: Sync Convex to BigQuery.
  • GitHub: Sync GitHub to BigQuery.
  • GitLab: Sync GitLab to BigQuery.