/ /

JAMF Pro AirSync Connector

The JAMF Pro AirSync connector imports your IT asset management data from JAMF Pro into DevRev, making it available for search, linking, and collaboration alongside your product and engineering workflows.

JAMF Pro AirSync Connector

The JAMF Pro AirSync connector imports your IT asset management data from JAMF Pro into DevRev, making it available for search, linking, and collaboration alongside your product and engineering workflows. This connector performs a one-way sync — data flows from JAMF Pro into DevRev only.

What this connector does

The connector reads data from your JAMF Pro instance and creates or updates corresponding records in your DevRev org. It covers Computers, Mobile Devices, Users, Departments, Buildings, Computer Groups, Mobile Device Groups, Policies, macOS Configuration Profiles, iOS Configuration Profiles, Packages, and Scripts — giving your teams a unified view of your managed device fleet directly in DevRev.

What data gets synced

Devices & Users

Entity

Description

Computers

All Mac computers managed by JAMF Pro, with full hardware inventory including serial number, model, processor, RAM, storage, MAC address, IP address, asset tag, OS version, and last contact time.

Mobile Devices

All iOS and iPadOS devices managed by JAMF Pro, including iPhones, iPads, and Apple TVs. Includes battery level, storage capacity, OS version, ownership level, and last inventory update.

Users

JAMF Pro user records synced as DevRev user identities with name, email, phone number, and position.

Organization

Entity

Description

Departments

Organizational departments from JAMF Pro, mapped to DevRev tags.

Buildings

Physical locations and buildings from JAMF Pro, mapped to DevRev tags.

Computer Groups

Static and smart computer groups, mapped to DevRev tags.

Mobile Device Groups

Static and smart mobile device groups, mapped to DevRev tags.

Configuration & Deployment

Entity

Description

Policies

JAMF Pro policies with trigger, frequency, scope, packages, scripts, and self-service settings.

macOS Config Profiles

macOS configuration profiles with distribution method, level, scope, UUID, and self-service settings.

iOS Config Profiles

iOS/iPadOS configuration profiles with deployment method, level, scope, UUID, and self-service settings.

Packages

Software packages with filename, category, hash, OS requirements, priority, and deployment flags.

Scripts

Shell scripts with category, priority, OS requirements, and full script contents.

Prerequisites

Before you install the connector, make sure you have:

  • A DevRev account with permission to install snap-ins

  • A JAMF Pro account with API access (username and password)

  • Your JAMF Pro hostname (e.g. yourinstance.jamfcloud.com)

How to install

  1. Go to your DevRev org and open Settings > Snap-ins.

  2. Find JAMF Pro in the snap-in catalog and click Install.

  3. Follow the prompts to create a new connection (see How to configure below).

  4. Once the connection is verified, the snap-in activates and is ready to sync.

How to configure

Setting up the connection

The connector uses Basic Authentication with your JAMF Pro credentials.

  1. When prompted to create a connection, enter a name for this connection (for example, JAMF Pro Production).

  2. In the Subdomain field, enter your JAMF Pro hostname (e.g. yourinstance.jamfcloud.com). Do not include https://.

  3. In the Username field, enter your JAMF Pro API username.

  4. In the Password field, enter your JAMF Pro API password.

  5. Click Verify. DevRev calls the JAMF Pro Classic API to confirm the credentials are valid.

  6. If verification succeeds, the connection is saved and your JAMF Pro instance is identified as the sync unit.

Connection fields

Field

Description

Subdomain

Your JAMF Pro hostname, e.g. yourinstance.jamfcloud.com

Username

Your JAMF Pro API username

Password

Your JAMF Pro API password

Permissions the connector requires

The snap-in uses a DevRev service account with the following scopes:

Scope

Purpose

sync_unit:read

Reads the JAMF Pro instance scope to determine what to sync

sync_mapper_record:read

Reads entity mappings to support incremental sync

sync_mapper_record:write

Writes entity mappings as JAMF Pro records are imported

sync_snap_in:all

Manages the extraction lifecycle and connector state

How the sync works

Sync direction

This connector is forward-only: data flows from JAMF Pro into DevRev. Changes made in DevRev are not written back to JAMF Pro.

Sync phases

Each sync run goes through four phases in order:

  1. Sync unit discovery — The connector identifies your JAMF Pro instance as the sync scope.

  2. Metadata extraction — The connector pushes the field schema for all 12 entity types into DevRev.

  3. Data extraction — The connector fetches all records for each entity type from the JAMF Pro Classic API and imports them into DevRev.

  4. Attachments extraction — This phase completes immediately; the JAMF Pro Classic API does not expose binary file attachments.

Incremental sync

For computers and mobile devices, the connector supports incremental sync. On subsequent runs, only devices that have checked in or been inventoried since the last sync are re-fetched, reducing API calls and sync time.

Resumable syncs

If a sync run is interrupted (for example, due to a timeout), the connector saves its completed entity state. When the next run starts, it skips already-completed entities and resumes where it left off.

How records map to DevRev objects

JAMF Pro entity

DevRev representation

Computers

Custom objects with full hardware inventory

Mobile Devices

Custom objects with full device inventory

Users

DevRev user identities (devu)

Departments

DevRev tags

Buildings

DevRev tags

Computer Groups

DevRev tags

Mobile Device Groups

DevRev tags

Policies

Custom objects

macOS Config Profiles

Custom objects

iOS Config Profiles

Custom objects

Packages

Custom objects

Scripts

Custom objects

Field reference

Computer fields synced to DevRev

JAMF Pro field

DevRev field

Name

Title

Serial Number

Serial Number

MAC Address

MAC Address

IP Address

IP Address

Asset Tag

Asset Tag

Platform

Platform

Supervised

Supervised

Site

Site

Model

Model

OS Version

OS Version

OS Build

OS Build

Processor Type

Processor Type

Processor Architecture

Processor Architecture

Number of Cores

Number of Cores

Total RAM (MB)

Total RAM (MB)

Storage Capacity (MB)

Storage Capacity (MB)

Storage Available (MB)

Storage Available (MB)

Owner Email

Owner Email

Department

Department

Building

Building

Room

Room

Last Contact Time

Last Contact Time

JAMF Pro URL

Item URL

Mobile Device fields synced to DevRev

JAMF Pro field

DevRev field

Name

Title

Serial Number

Serial Number

Model

Model

OS Version

OS Version

OS Type

OS Type

IP Address

IP Address

Capacity (MB)

Capacity (MB)

Available (MB)

Available (MB)

Storage Used (%)

Storage Used (%)

Battery Level

Battery Level

Ownership Level

Ownership Level

Site

Site

Owner Email

Owner Email

Department

Department

Building

Building

Managed

Managed

Supervised

Supervised

Last Inventory Update

Last Inventory Update

JAMF Pro URL

Item URL

Policy fields synced to DevRev

JAMF Pro field

DevRev field

Name

Title

Enabled

Enabled

Trigger

Trigger

Frequency

Frequency

Category

Category

Site

Site

Offline

Offline

Network Requirements

Network Requirements

Available in Self Service

Available in Self Service

Packages

Packages

Scripts

Scripts

Reboot Action

Reboot Action

Scoped to All Computers

Scoped to All Computers

Target Computer Count

Target Computer Count

Target Group Count

Target Group Count

Scope Departments

Scope Departments

Scope Buildings

Scope Buildings

Best practices

  • Use the Computer and Mobile Device custom objects for IT searches — All device fields including serial number, model, OS version, and owner are stored on these custom objects and can be searched and filtered in DevRev.

  • Use tags for device targeting — Departments, Buildings, Computer Groups, and Mobile Device Groups are all synced as DevRev tags. Use these to group and filter related device records quickly.

  • Filter policies by scope fields — The scope_all_computers, target_computer_count, and target_group_count fields on Policy objects help you quickly identify policies with broad or narrow impact.

  • Do not edit synced records directly in DevRev — Since this connector does not write back to JAMF Pro, any changes you make to synced records in DevRev are overwritten on the next sync. Make changes in JAMF Pro first.

  • Verify your credentials regularly — If the JAMF Pro credentials expire or are changed, the connector will fail authentication and the sync will stop. Update the connection settings in DevRev before credentials change.

Troubleshooting

The sync is not starting

  • Confirm the snap-in is in Active state in Settings > Snap-ins.

  • Verify the connection by editing it in Settings and clicking Verify again.

  • Check that your JAMF Pro credentials have not been changed or deactivated.

Devices or users are missing

  • Check that the sync has fully completed all four phases. Metadata extraction must finish before data records are created.

  • If a particular entity type is missing, the connector may have received an error from the JAMF Pro API for that endpoint. Check the snap-in logs for warnings about failed entities.

Custom object fields are empty

  • Confirm the field exists in JAMF Pro for that record — many fields like os_requirements or notes are optional and may be blank in your JAMF environment.

  • Fields containing only the value "None" or "-" are intentionally left empty in DevRev.

Authentication errors

  • Confirm your JAMF Pro username and password are correct.

  • Ensure the JAMF Pro user account has read access to the Classic API (/JSSResource/*).

  • Verify your JAMF Pro hostname does not include https:// — enter only the hostname (e.g. yourinstance.jamfcloud.com).

Related resources

Was this article helpful?