How to export Automox device inventory to CSV
Open Automox Device Explorer, build the device query you need, choose the visible columns and select Export CSV. Use separate reports for patch or activity history, and RMMBackup when you need dated copies of supported records to review later.
Export Automox Device Explorer results to CSV, choose query filters and visible columns, and validate device inventory separately from patch-history reports.
On this page
Export a targeted device spreadsheet
The Automox tools comparison separates report/history exports from vulnerability CSV inputs; importing scanner findings does not import old RMM device history.
- Select the intended organization, then open Devices > Device Explorer.
- Build a query with the attributes, conditions and values needed for the inventory. Without a query, the table shows that organization's devices.
- Open Columns and show the fields you need.
- Select Export CSV to download the query results with those visible columns.
See Device Explorer. Software and Disks results depend on associated query attributes; do not assume every queryable attribute becomes a CSV field.
The roles and permissions guide distinguishes Queries: Read for viewing/building queries from Queries: Manage for saving and managing them in custom roles. Organization-level roles apply within that organization. Ask your administrator to confirm access if Device Explorer is unavailable.
Validate the device CSV
Our suggested check is to compare the CSV with the entire query result, then sample device UUIDs, names, serials and group context where included. Check headers against the visible columns, preserve leading zeros in identifiers, and inspect nested disk/network values before flattening them. Keep the original, query, organization and export time with the validation checklist. A current device list does not establish patch history or policy configuration.
Export the relevant native history report
From Reports, choose View for the report you need. Automox's reporting guide separates Activity Log events, Patch History extracts, API Activity and policy results. Choose the relevant time range and use the selected report's available download controls; formats and permissions can differ.
Our suggested check is to verify the organization, first/last timestamps and a known event or policy run. Preserve the range with the original file. A Device Explorer CSV's scope does not define these reports' history coverage.
Choose the correct API key scope
Automox documents organization and Global API Keys. An organization key is limited to its organization. A Global API Key can target every organization in the account where its owner has the required role permissions. Use a dedicated Global API Key for RMMBackup and grant only the read permissions needed by the selected sources.
RMMBackup validates authentication by listing accessible organizations before enabling the connection. A successful check proves access to the returned scope; it does not prove that the owner can read organizations or resource types hidden by role assignments.
Free allows one accepted manual backup attempt per rolling 24 hours across the MSP account, keeps the latest fully successful snapshot accessible, and does not schedule automatic backups. Full Access allows two accepted manual attempts per rolling 24 hours for Automox, keeps ongoing accessible history, and adds a daily automatic schedule after the first fully successful backup. Full Access is free during open beta; contact support to activate it. Review pricing.
What the integration exports
The integration captures organization records, detailed devices, hardware and software inventory, device packages, groups, saved searches, policies, schedules, filters, custom Worklet evaluation and remediation code, Cloud Worklet metadata and execution history, patch state, policy-run results, organization events, audit events, approvals, webhook definitions, and available delivery history.
List responses that omit important data are followed by documented detail reads. Custom policy detail is the source for readable evaluation and remediation code. Cloud Worklets are a separate API and the public response currently documents metadata and execution history, not equivalent script-body fields.
Keep Worklet versions in Git with Worklet Warden
For a DIY code-history workflow, Automox publishes Worklet Warden and an example backup workflow. They save policy JSON separately from evaluation/remediation code and commit changes to Git, making earlier code and diffs available for review.
Review the sample and maintain its credentials, dependencies and schedule before adoption. Its policy listing requests limit=500, page=0; verify larger accounts, every intended organization and saved policy IDs before calling a run complete. Keep the original JSON and code together. Worklet Warden also has write/update operations: those belong to that separate tool, while RMMBackup preserves supported records for browsing, comparison and export.
Pagination, rate limits, and history
Automox list APIs use zero-based page and limit parameters, generally with a maximum of 500. RMMBackup continues until a short terminal page and rejects repeated stable IDs. Each Audit Trail backup covers the rolling 31-day range allowed by the API and follows every cursor returned for that range. Webhook reads follow their documented cursors. The device list is paced below its documented 30-request-per-minute ceiling, and all requests honor Retry-After with bounded retries.
The first snapshot performs full retrieval for every selected source and requests all history the API returns without imposing an arbitrary lookback. Later snapshots remain full logical captures because the public contracts do not provide one safe incremental model for every supported collection. Vendor retention, permissions, licensing, and endpoint-specific limits can still bound available history.
Snapshot and deletion safety
Each successful snapshot ZIP contains the original captured records, a contents summary, and archived source responses. If part of a collection cannot be captured, RMMBackup marks it partial and keeps the last complete version as the comparison baseline. This prevents incomplete results from appearing as deleted records.
Deleted-device detection applies only after two complete device inventories for the same MSP and Automox connection. If organization visibility is reduced, stop and restore the expected Global API Key scope before treating missing devices as confirmed deletions.
Using your saved Automox records
RMMBackup never executes Worklets, installs patches, starts policy actions, changes devices or groups, approves patches, creates extracts, registers webhooks, or writes configuration. Snapshot ZIP files are backup artifacts, not Automox import or restore packages.
Official references
Plan the next step
For a move, review destination import options, then use the RMM migration checklist. Check the selected native tool before transforming files; an export is not automatically a destination import package. The migration use case explains how successfully captured records remain useful as a separate reference within your plan's accessible history.