Before you begin
- An Enterprise plan or above. The Integrations hub is locked below Enterprise
- The Administrator role in Atlas to connect, configure or disconnect a connector. Integrations appears under Administration only for administrators
- A tenant selected in the tenant picker. Credentials are stored encrypted per tenant, so each tenant you manage connects its own account
- A ConnectWise Automate server whose web address is reachable from the internet (Atlas does not connect to private or internal addresses)
- A dedicated Automate user account for Atlas, without two-factor sign-in
- For Automate 2020.1 and later: an integration Client ID
What you can do
- See every Automate computer with its client, location, operating system, online status and last contact, and jump from a computer to the matching session host in Atlas.
- Track online and offline computers and unacknowledged alerts at a glance.
- Browse your clients and the locations under each one, with a computer count per location.
- Acknowledge Automate alerts from Atlas.
- Read and acknowledge Automate alerts from your own automation with an Atlas API key.
Step 1: Prepare Automate
- Create a dedicated Automate user for Atlas, with permission to view clients, locations, computers and alerts and to update alerts. Turn off two-factor sign-in for this account: Atlas signs in again on its own whenever its session expires (about once a day) and cannot answer a two-factor prompt.
- On Automate 2020.1 or later, get your integration Client ID (a GUID) from System → Configuration → Integration → API, or from ConnectWise's developer program. Older servers do not need one.
Step 2: Connect in Atlas
Once connected, the card shows Manage, which opens the ConnectWise Automate page, and Disconnect. The password and Client ID are stored encrypted.
- Select the tenant in the tenant picker.
- Go to Administration → Integrations and click Connect on the ConnectWise Automate card.
- Enter the Server URL (your Automate web address, starting with https://, for example https://automate.example.com), the Username and Password of the Atlas account, and the Client ID if your server needs one.
- Click Connect. Atlas signs in to Automate and reads your clients before saving anything; if Automate rejects the sign-in, nothing is stored.
What you see
- Overview: Total Computers, Online, Offline and Active Alerts, the computer online ratio, and how many clients and locations you have.
- Computers: name, client, location, OS, status and last contact. Search by name, client, location or OS, sort any column, and click the AVD link to open the matching session host. A computer links when its name matches a VM name exactly, or when its short name matches exactly one VM.
- Alerts: unacknowledged alerts with computer, severity, message and when they were raised. Search by message, and filter by Critical, Warning or Normal.
- Clients & Locations: each client with its locations and the number of computers at each.
Atlas reads Automate live each time you open a tab or click Refresh; it does not copy your RMM data into Atlas or sync it in the background.
Acknowledge alerts
Each alert row has an Acknowledge action, which marks the alert acknowledged in Automate straight away, with no confirmation step, and removes it from the list.
Use it from your own tools
An Atlas API key with the integration.cw_automate.read scope can list alerts at GET /api/integration/connectwise-automate/alerts, and one with integration.cw_automate.write can acknowledge an alert at POST /api/integration/connectwise-automate/alerts/{id}/acknowledge. See API Access for how keys are issued.
What the integration does not do
- It does not run scripts, open a remote session, reboot, patch or install software through Automate. Use Automate for those, or Atlas Reach.
- It does not create tickets. Use the ConnectWise Manage integration for ticketing.
- Its only change in Automate is acknowledging alerts; it does not resolve or clear them.
- It does not work with an Automate account that requires two-factor sign-in.
- It connects one Automate server per Atlas tenant, and cannot reach a server on a private network.
- Credentials cannot be edited in place: disconnect and connect again.
- Atlas Advisor can tell you whether Automate is connected, but does not answer questions about computers or alerts.
GCC High tenants
On a tenant or deployment in Azure Government (GCC High), calls to ConnectWise Automate are blocked by default, because they can carry VM, host-pool and tenant names to a service outside the Government boundary. Connect fails with an Azure Government (GCC High) egress boundary message and nothing is stored, and pages that read from ConnectWise Automate stay empty. The operator who runs your Atlas deployment can approve ConnectWise Automate as a destination that is allowed to receive that data; once approved, the connector works normally. Running in Azure Government does not by itself make a third-party integration GCC High or CMMC compliant.
Disconnecting
Click Disconnect on the card and confirm. Atlas deletes its stored credentials and signs out; nothing changes in Automate. Disable or delete the Atlas user in Automate too if you no longer need it. You can reconnect at any time.
Troubleshooting
- ConnectWise Automate rejected the supplied credentials: check the username and password, that two-factor sign-in is off for the account, and, on 2020.1 or later, that the Client ID is entered and valid.
- Could not connect to ConnectWise Automate — verify the server URL and credentials: check the address is your Automate web address, that it is reachable from the internet with a valid certificate, and that the server is up.
- The ConnectWise Automate server URL is not allowed: the address resolves to a private or internal IP address.
- serverUrl must be a valid https:// URL: include https://.
- The Computers or Alerts tab is empty when you expect data: click Refresh. An empty tab can also mean Automate returned an error; if it persists, disconnect and connect again to re-test the account.