Automox
Visualize Automox services, teams, and users, map users to employees, and monitor changes through queries and alerts.
- Installation
- Data Model
- Types
- Release Notes
Installation
You will need an Automox Organization API key to connect this integration. To create and manage one, you must be a Full Administrator or hold a custom role with Organization: Read and Manage, and you must have the Personal API Key: Manage permission. See Automox's Managing Keys guide for more information.
An Automox API key inherits the permissions of the user who creates it, so the key you use for JupiterOne must belong to a role that grants at least Devices: Read, Groups: Read, Users: Read, and Organization: Read. The default Read Only role satisfies all four. For the full permission matrix, see Automox's Roles and Permissions reference.
Creating an Automox Organization API key
- In the Automox console, navigate to Settings > Secrets & Keys.
- Under Organization API Keys, click Add.
- Enter a unique name for the key, and optionally set an expiration date.
- Click Create, then copy the generated key for use in JupiterOne.
The Secrets & Keys page also lists your Account ID (the UUID for the account) alongside the account name, which you will need when configuring the integration in JupiterOne.
Configuration in JupiterOne
To install the Automox integration in JupiterOne, navigate to the Integrations tab in JupiterOne and select Automox. Click New Instance to begin configuring your integration.
Creating an instance requires the following:
-
The Account name used to identify the Automox account.
-
The Account ID of your Automox account.
-
The API Key you generated in Automox for use by JupiterOne.
-
A Description to assist in identifying the integration instance, if desired.
-
A Polling Interval that you feel is sufficient for your monitoring needs. You may leave this as
DISABLEDand manually execute the integration.
Click Create once all values are provided to finalize the integration.
Next steps
Now that your integration instance has been configured, it will begin running on the polling interval you provided, populating data within JupiterOne. Continue on to our Instance management guide to learn more about working with and editing integration instances.
Entities
The following entities are created:
| Resources | Entity _type | Entity _class |
|---|---|---|
| Account | automox_account | Account |
| Device | automox_device | Device |
| Device Group | automox_device_group | Group |
| User | automox_user | User |
Relationships
The following relationships are created:
Source Entity _type | Relationship _class | Target Entity _type |
|---|---|---|
automox_account | HAS | automox_user |
automox_account | MANAGES | automox_device |
automox_account | MANAGES | automox_device_group |
automox_device_group | HAS | automox_device |
Automox Account
automox_account inherits from Account
Automox Device
automox_device inherits from Device
| Property | Type | Description | Specifications |
|---|---|---|---|
compliant | boolean | ||
connected | boolean | ||
createdOn | number | ||
deleted | boolean | ||
lastProcessedOn | number | ||
lastRefreshedOn | number | ||
lastScanFailedOn | number | ||
macAddress | array of strings | ||
organizationId | number | ||
osFamily | string | ||
osVersionId | number | ||
serialNumber | string | ||
serverGroupId | number | ||
status.agentStatus | string | ||
status.deviceStatus | string | ||
status.policyStatus | string | ||
status.policyStatuses | array of numbers | ||
updatedOn | number |
Automox User
automox_user inherits from User
| Property | Type | Description | Specifications |
|---|---|---|---|
active | boolean | ||
samlEnabled | boolean | ||
ssoEnabled | boolean |
Release Notes
- 2026-04-08 — Improved OS name accuracy for Automox device entities, combining OS family and OS name into human-readable display values.