Using Jamf Pro actions in action flows



What's my plan?






All Suites

Growth, Professional, Enterprise, or Enterprise Plus









Support

Team, Professional, or Enterprise







The Jamf Pro connector for action
builder is available as part of the
IT Asset Management EAP.


By connecting the
action builder
to external systems, such as Jamf Pro, admins
can integrate Zendesk with external systems in automated workflows, improving
collaboration and maintaining a seamless experience across multiple platforms.

Note: The
steps associated with external systems in action flows are referred
to collectively
as external actions.



This article contains the following topics:


Connecting Jamf Pro to action builder


Using Jamf Pro actions in action flows


Using templated action flows to synchronize assets with Jamf Pro





Connecting Jamf Pro to action builder


Before you can include external actions in your action flows, you
must connect the
action builder to the external system.


When connecting to external systems for use in action flows, the
following best practices are recommended:


All external actions performed by an action flow are attributed
to the user who connected the
external system. Therefore, it's a best practice to use a
dedicated service
account rather than personal credentials when connecting
to each external
system.


All integrations request access to necessary scopes. However,
it's important that you review and validate the scopes before
authorizing the connection to the external system.


When managing credentials for API key-based tools, such as
OpenAI, it's best to store keys in a secure vault or credential
manager.




To connect action builder to Jamf Pro


In Jamf Pro,
create a role
with the following
permissions:


Assign users to mobile devices


Read computer inventory collection


Read mobile devices


Update computers


Read computers


Assign users to computers


Read mobile device inventory collection


Read user


Update computer inventory collection


Read accounts




In Jamf Pro,
create an API client
and assign it
to the role with the listed permissions.


In Jamf Pro,
generate a client secret.


In Admin Center, click
Apps and integrations in the sidebar, then select Actions > Action
flows.


Create
or
edit
an action flow.

Open the step sidebar.

Under External actions, click
Jamf Pro.


Click Connect.


Use Jamf Pro to authenticate the account.

Use the Jamf URL, client ID,
and the generated client secret to authenticate.


Note: All external
actions performed by an action flow are attributed to
the user who
connected the external system. Therefore, it is a best
practice to use a
dedicated service account rather than personal credentials
when
connecting to each external system.





After you've connected to the system, you'll see an indicator that
it's connected and
details about the instance you're connected to, as well as the actions
available for
Jamf Pro.




Using Jamf Pro actions in action flows


Jamf Pro action steps can be used in action flows to streamline the
management of IT
assets, such as computer inventories and mobile devices.


The following Jamf Pro actions are available:


List computer
inventories


List mobile
devices





Listing computer inventories


Use the List computer inventories action
to retrieve a list of computer
assets.

This action has the following inputs and outputs:










Variables




Inputs
None


Output

Computer identification, hardware, purchasing,
location,
and user assignment data









Listing mobile devices


Use the List mobile devices action to retrieve
a list of mobile device
assets.

This action has the following inputs and outputs:










Variables




Inputs
None


Output

Device identification, hardware, purchasing,
location,
and user assignment data











Using templated action flows to synchronize assets with Jamf Pro



To make it as simple as possible to incorporate your IT asset data
into your Zendesk
workflows, the following pre-built but customizable action flow templates
are
provided to help you synchronize your asset data with Jamf Pro:


Jamf for computers


Jamf for mobile
devices



Note: The action flow steps required
to perform data synchronization with Jamf
Pro are only available through these templates during the EAP.
You must
connect your Jamf Pro account to
action builder
to access the templates.



To create a templated action flow


In Admin Center, click
IT assets in the sidebar, then select Assets > Overview.


Select the template you want to create:
Jamf for computers or
Jamf
for mobile devices.

An action flow is created with pre-populated
steps and values.


Connect your Jamf Pro account.

Activate
the templated action
flow.





Template: Jamf for computers


This workflow syncs Jamf computer (laptops and desktops) and
user data to Zendesk
IT assets.


The action flow template for synchronizing computer asset data
with Jamf Pro
consists of the following steps:


Action flow trigger: Schedule.
The action flow trigger, which
initiates the action flow on a daily basis.

A default time at which
to initiate the action flow is preconfigured, but
can be
adjusted.



Utility: Repeat while conditions are met.
A looping step
configured to repeat the following actions while there
are additional
pages of computers:


External actions: Jamf Pro: Fetch computers.

Fetches
computer device data from Jamf.



Utility: Repeat for each.
A looping step configured to
repeat the following actions for each computer
asset returned by
the Fetch computers
step.


Utility: Custom code.
Custom JavaScript that maps
the Jamf computer data to the appropriate
asset type and
status in Zendesk.

The asset type is set to
Laptop if the
model name contains the word
"book;" otherwise, the asset type
is set to
Desktop.


If the device is assigned to
a user, the Zendesk asset status
is In use;
otherwise, the status is
Available.


Note:
Validate and customize
the pre-defined JavaScript as needed.



Zendesk actions: Create or update user.
A step
that checks whether the computer's assigned
user in Jamf
matches a Zendesk user record, and creates
the user's
record in Zendesk if it doesn't exist.


Zendesk actions: Import assets.
Creates or
updates asset records in Zendesk and
automatically maps
Jamf computer details to asset fields.










Template: Jamf for mobile devices


This workflow syncs Jamf mobile device (cellphones and tablets)
and user data to
Zendesk IT assets.


The action flow template for synchronizing mobile asset data
with Jamf Pro
consists of the following steps:


Action flow trigger: Schedule.
The action flow trigger, which
initiates the action flow on a daily basis.

A default time at which
to initiate the action flow is preconfigured, but
can be
adjusted.



Utility: Repeat while conditions are met.
A looping step
configured to repeat the following actions while there
are additional
pages of mobile devices:


External actions: Jamf Pro: Fetch mobile devices.
Fetches mobile device data from Jamf.


Utility: Repeat for each.
A looping step configured to
repeat the following actions for each mobile
device asset
returned by the
Fetch mobile devices
step.


Utility: Custom code.
Custom JavaScript that maps
the Jamf mobile device data to the appropriate
asset
type and status in Zendesk.

The asset type is set to
Mobile.


If the device is assigned to
a user, the Zendesk asset status
is In use;
otherwise, the status is
Available.


Note:
Validate and customize
the pre-defined JavaScript as needed.



Zendesk actions: Create or update user.
A step
that checks whether the mobile device's
assigned user in
Jamf matches a Zendesk user record, and
creates the
user's record in Zendesk if it doesn't
exist.


Zendesk actions: Import assets.
Creates or
updates asset records in Zendesk and
automatically maps
Jamf mobile device details to asset fields.











//
const ai_summary_style = document.createElement('style');
ai_summary_style.innerHTML = `#styled-article-body{padding:0 0 0}#article-body #docs-ai-summary{background-color:#f3f3f3;border:1px solid #d3d3d3;padding:10px 10px 6px;margin-bottom:16px}#article-body #docs-ai-summary #docs-ai-summary-toggle{font-size:.9em;font-weight:700;margin-bottom:4px;cursor:pointer;display:flex;justify-content:space-between;align-items:center}#article-body #docs-ai-summary #docs-ai-summary-toggle #up-triangle{margin-left:auto;padding-right:10px;display:none}#article-body #docs-ai-summary #docs-ai-summary-toggle #down-triangle{margin-left:auto;padding-right:10px}#article-body #docs-ai-summary #docs-ai-summary-content{font-size:.9em;padding-left:25px;padding-right:25px;margin-bottom:12px}`;
document.head.appendChild(ai_summary_style);

const toggleAISummary = () => {
const summary = document.getElementById("docs-ai-summary-content");
const upTriangle = document.getElementById("up-triangle");
const downTriangle = document.getElementById("down-triangle");
if (summary.style.display === "none") {
summary.style.display = "block";
upTriangle.style.display = "none";
downTriangle.style.display = "inline";
} else {
summary.style.display = "none";
upTriangle.style.display = "inline";
downTriangle.style.display = "none";
}
};

document.getElementById("docs-ai-summary-toggle").addEventListener("click", toggleAISummary);
//
