How to back up Action1 data
RMMBackup keeps a separate, read-only history of supported Action1 organizations, endpoints, software, updates, vulnerabilities, configuration, reports, and activity. Use the guide below to connect Action1 and verify your first snapshot.
Back up supported Action1 endpoints, software, vulnerabilities, configuration, reports, and activity data.
On this page
Choose an Action1 backup method
| Method | Useful for | Important limitation |
|---|---|---|
| Native report export | Export a selected report to CSV or HTML; export the Audit Trail to CSV | Output is report- and permission-scoped, not a complete enterprise archive |
| API script | Retrieve documented JSON resources, report rows, and audit events | Your script must manage OAuth, organization scope, pagination, retry, storage, and completeness |
| RMMBackup | Take repeatable snapshots of selected Action1 data, browse history, and download snapshot ZIPs | Coverage is limited to the supported data below |
Action1's report guide documents CSV and HTML exports. Its API overview describes JSON resources and recommends its official scripting path. A one-time report and a recurring independent snapshot solve different problems.
See the Action1 integration for the Action1 data RMMBackup can back up.
What RMMBackup backs up from Action1
| Collection group | Captured data | Boundary |
|---|---|---|
| Scope and endpoints | Organizations, managed endpoints, endpoint groups and membership | Every organization visible to the OAuth credential is in scope |
| Security inventory | Installed software, missing updates, vulnerabilities, remediation history | Results depend on documented availability and permission scope |
| Configuration | Enterprise and advanced settings, setting templates, custom scripts and data sources, users and roles | Read-only; scripts and settings are never executed or changed |
| Deployment and automation | Agent deployment configuration, deployers, software repository, automation schedules and action templates | Automation launches are excluded |
| Reports and history | Report definitions, subscriptions, cached rows and errors, drill-down data, automation history | RMMBackup does not requery reports; cached or retained source history can be limited |
| Operations | Audit events, diagnostic logs, license and usage metadata | Source retention and role permissions can limit history |
RMMBackup keeps organization relationships and the original returned data. Action1 backups do not label missing records as deleted, because a permissions change can also hide information from the connection.
Set up recurring Action1 backups
- Create and verify a RMMBackup account.
- Use the Action1 OAuth credential guide to create a client in the correct region with the required read permissions and organization assignments.
- In Settings > Integrations, choose Action1, select the region, enter the client ID and secret, and choose collections.
- Save and validate the connection. Compare discovered organizations with the intended scope before enabling it.
- Start a manual backup, inspect each collection result, and compare representative endpoints and settings with Action1.
- Download the ZIP and retain a native report export as an independent coverage check.
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 this vendor, 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. See pricing.
Browse history and export captured data
Successful captures can be browsed as native records and compared with earlier accessible versions. Snapshot ZIPs contain JSON records, a manifest, and original API responses. They are not Action1 CSVs or an importable restoration bundle. Follow the Action1 export guide for native report options.
If part of a backup fails, RMMBackup marks it failed instead of treating it as an empty result or a new comparison baseline. Action1 backup history, browsing, and ZIP downloads remain separate from other integrations.
Preserve Action1 data before a migration
Capture all required organizations while the credential still has access. Export critical reports and the audit trail separately, record filters and time windows, then verify endpoint identifiers in both the native files and RMMBackup snapshot. Use the RMM migration checklist; RMMBackup does not import records into a replacement platform.
Review historical endpoint records
An accessible backup can show endpoint data captured before the endpoint stopped appearing. Use deleted-record guidance to understand how missing records are handled, and check backup retention when planning long-term access.
Frequently asked questions
Can Action1 reports be exported?
Yes. Action1 documents CSV and HTML export for report data, but each output remains limited to that report, its scope, fields, permissions, and available history.
Does RMMBackup run Action1 automations or remote actions?
No. It excludes automation execution, report requeries, remote sessions, endpoint changes, and other provider writes.
Can RMMBackup prove that a missing Action1 endpoint was deleted?
No. Action1 deletion detection is disabled because organization and permission scope changes can also make records disappear.