RMM & Endpoint

Automox

Browse your Automox patch and endpoint estate from Dex - devices, policies, server groups, users, and events, scoped per customer.

Dex connects to the Automox Console API so admins can explore their patch and endpoint management estate conversationally - list and read devices (servers), inspect installed packages, review patch and configuration policies, browse server groups, and check users and events. Automox is an MSP global app: one Global API Key from Settings > Keys is shared across your account, and each Dex tenant is confined to its own Automox Organization via a numeric organization_id that forces the o= query parameter onto every allowed read. Reads are the shipped surface today - mutating queue and command writes are not exposed on a scoped connection.

Start free →See Dex Live

What Dex does with Automox

Dex handles both admin workflows and employee self-service — all policy-guardrailed and audit-logged.

For admins (Dex Pro)

List and read Automox devices (servers) for a customer Organization
Inspect the installed packages on a specific device
Review patch and configuration policies, and read a policy by id
Browse server groups and read a group by id
List the users and events recorded for an Organization
On the MSP master connection, list every Automox Organization to map each Dex tenant to its organization_id
Deploy as an MSP global app - one Global API Key, each customer confined to its Automox Organization via forced o=

Just ask Dex

Your team types a request in plain language. Dex investigates, plans, and executes — with the right guardrails.

Admin prompts

>List the Automox devices for this customer and flag any that look out of date
>Show me the packages installed on server 48213
>What patch policies are configured for this Organization?
>Read server group 1207 and tell me what devices it covers
>List the recent Automox events for this Organization
>On the master connection, find the organization_id for the customer named "Contoso"

Policy actions

Every action Dex can take on Automox is declared, scoped, and guardrailed. Admins control which apply, who approves them, and whether they're limited to self-service.

Action	What it does	Guardrails
`automox_list_servers`	List Automox devices (servers) for this Organization	—
`automox_get_server`	Read one Automox device by id	—
`automox_list_server_packages`	List packages for one Automox device	—
`automox_list_policies`	List Automox policies for this Organization	—
`automox_get_policy`	Read one Automox policy by id	—
`automox_list_servergroups`	List Automox server groups for this Organization	—
`automox_get_servergroup`	Read one Automox server group by id	—
`automox_list_users`	List Automox users for this Organization	—
`automox_list_events`	List Automox events for this Organization	—
`automox_list_orgs`	List every Automox Organization (master connection only)	—
`automox_get_org`	Read one Automox Organization by id (master-oriented; refused on a scoped child)	—

How to configure Automox

Onboarding takes minutes. Dex validates your credentials before saving them.

Setup steps

1
In the Automox console, go to Settings > Keys and create a Global (account-spanning) API Key for Dex.
2
On the MSP master connection in Dex, paste the Global API Key and leave organization_id blank.
3
Use the master connection to run GET /api/orgs and match each customer by name to its numeric organization_id.
4
On each tenant connection, save that customer's organization_id so Dex forces o= onto every allowed read.
5
Dex validates the connection with a live read before saving - the master probes /api/orgs and a scoped child probes /api/servers.

Credentials required

api_key: Automox Global API Key from Settings > Keys (account-spanning; kept secret and never surfaced)
organization_id: This tenant's numeric Automox Organization id (the o= value); leave blank on the MSP master connection

Requirements

•An Automox account with a Global API Key created under Settings > Keys
•The numeric organization_id for each customer, read from the console URL (o=) or GET /api/orgs on the master
•Read-only today - mutating queue and command writes are default-denied on a scoped connection
•For MSPs, deploy as a global app: one shared Global API Key, per-tenant scoping via organization_id