How can we help?
{{docApp.searchError}}
{{product.name}}
Searching in {{docApp.searchFilterBySpecificBookTitle}}
{{docApp.searchResultFilteredItems.length}} results for: {{docApp.currentResultsSearchText}}
in {{docApp.searchFilterBySpecificBookTitle}}
Search results have been limited. There are a total of {{docApp.searchResponse.totalResultsAvailable}} matches.
You have an odd number of " characters in your search terms - each one needs closing with a matching " character!
-
{{resultItem.title}}
{{resultItem.url}}
{{docApp.libraryHomeViewProduct.title || docApp.libraryHomeViewProduct.id}}
{{docApp.libraryHomeViewProduct.description}}
{{group.title || group.id}}
{{group.description}}
Operation Information
Create a Mobile Device within jamf.
This is a Premium Integration.
Authentication
This operation requires authentication, the details of which can be securely stored on your instance in a KeySafe Key of type Jamf.
To create a key of this type:
- In the Configuration area of your Hornbill instance, navigate to Platform Configuration > Security > KeySafe;
- Click on the + Create New Key button;
- On the resulting Create New Key form, choose Jamf in the Type pick list;
- Give the Jamf KeySafe key a Title (this is the name / identifier for the Jamf account as you will see it when using the cloud automation node in your workflows);
- Optionally populate the Description field;
- Populate the following fields accordingly, then click the Create Key button to create your new key:
Name | Type | Description |
---|---|---|
Username | string |
Jamf username |
Jamf Server | string |
The server name for your jamf instance this can be found in your url before '.jamfcloud.com' |
Password | string |
Your Jamf Password |
Revoking Access
If at any point you wish to revoke access to any of the above accounts from your Hornbill instance, just delete the relevant KeySafe key(s) from the KeySafe list.
Warning
This will revoke the rights of any existing Cloud Automation Node in your Hornbill Workflows that are using the revoked Jamf account, so you will need to manage these workflows accordingly.
Input Parameters
Display Name | ID | Type | Description | Required | Supported Values |
---|---|---|---|---|---|
Mobile ID | mobileId |
string |
The Unique ID of the Mobile Device | Yes | None provided |
Display Name | displayName |
string |
The Display Name for the Mobile Device | Yes | None provided |
Mobile Name | name |
string |
The Name of the Mobile Device | No | None provided |
Device Name | deviceName |
string |
The Device Name for this Mobile | No | None provided |
Computer Serial Number | serialNumber |
string |
The Serial Number of the Mobile | Yes | None provided |
Computer UDID | udid |
string |
The UDID of the Mobile | Yes | None provided |
Username | username |
string |
The Username of the Mobile user | Yes | None provided |
Real Name | realName |
string |
The Name of the Mobile user | No | None provided |
Email Address | emailAddress |
string |
The Email of the Mobile user | No | None provided |
Position | position |
string |
The Position of the Mobile user | No | None provided |
Phone | phone |
string |
The Phone of the Mobile user | No | None provided |
Phone Number | phoneNumber |
string |
The Phone Number of the Mobile user | No | None provided |
Department | department |
string |
The Department the Mobile is in | No | None provided |
Building | building |
string |
The Building the Mobile is in | No | None provided |
Room | room |
string |
The Room the Mobile is in | No | None provided |
Purchased Device | isPurchased |
boolean |
Was the Device Purchased | No | None provided |
Leased Device | isLeased |
boolean |
Is the Device on Lease | No | None provided |
PO Number | poNumber |
string |
The PO Number the Device was procured on | No | None provided |
Vendor | vendor |
string |
The Mobile Device vendor | No | None provided |
Apple Care ID | applecareId |
string |
The Apple Care ID for the Deivce | No | None provided |
Purchase Price | purchasePrice |
string |
The Amount the Mobile Device was obtained for | No | None provided |
Purchasing Account | purchasingAccount |
string |
The Account the Device was procured against | No | None provided |
Life Expectancy | lifeExpectancy |
string |
The Life Expectancy of the Device | No | None provided |
Purchasing Contact | purchasingContact |
string |
The Contact responsible for Purchasing the Device | No | None provided |
Output Parameters
Display Name | ID | Type | Description |
---|---|---|---|
Error Message | error |
string |
Any error message returned by jamf |
Status Code | status |
string |
The status of the operation, ok/failed |
Mobile ID | id |
string |
The unique identifier number for the created Mobile Device |
- Version {{docApp.book.version}}
- Node {{docApp.node}} / {{docApp.build}}
In This Document