Docs / Data sources / Jamf

Jamf

Business software

Built when you ask for it

Sync Jamf computer, mobile device, policy, and user data into your warehouse. Ingest builds this connector the first time a customer asks for it, then keeps the tables current in a data warehouse you own, on the schedule you choose.

The Jamf connector syncs your Apple device-management data into analytics-ready tables in your data warehouse. Pull computers, mobile devices, policies, and users from the Jamf Pro API, with Ingest handling auth, pagination, and retries so the tables stay current.

What you would get

Each of these arrives as its own table, kept current on the schedule you choose:

  • Computers
  • Mobile devices
  • Policies
  • Users

How it gets built

  1. Choose Jamf when you set up a pipeline, with the warehouse it goes to and a schedule.
  2. Ingest reads Jamf's documentation, and you choose the tables you want.
  3. Ingest builds the connector and tests it against Jamf itself.
  4. A person at Ingest reviews and publishes it, and your pipeline starts on its own.

What you will need

OAuth 2.0 (client credentials); Basic Auth also supported. An admin creates an API Role and API Client in Jamf Pro to get a Client ID/Secret, then exchanges it for a short-lived bearer token.

You enter it once, in a form in Ingest, and it is kept in a secret store set aside for your organization.

Questions

Does Ingest have a Jamf connector?
Not as a finished connector yet. Ingest builds it from Jamf's own documentation the first time a customer asks, tests it against the real service, and lists it once it passes.
Which warehouses can Jamf data go to?
Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL and Snowflake, in an account you own.
Do I need to write code?
No. Ingest builds, runs and maintains the connector. Someone with access to your warehouse connects it once, following a short guide.

Jamf API documentation: https://developer.jamf.com/jamf-pro/docs/client-credentials

Setting up the destination is its own short guide, one per warehouse or lake: Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL, Snowflake.

Other sources Ingest connects for SaaS teams: Asana, Jira, Airtable, Clockify, Facebook Ads, Frankfurter.

Request Jamf