Skip to main content
Connect ConnectWise RMM so the agent can look up devices, run automation scripts on managed endpoints, view patch status, and create or read service tickets across every client in your Asio tenant.
ConnectWise RMM is configured in MSP Settings → Integrations.

​
How to connect

ConnectWise RMM uses API credentials issued from the Asio platform. You’ll generate them in the ConnectWise admin UI before starting.
1

Generate API credentials in ConnectWise

In the Asio platform UI (auplatform.connectwise.com, itsupport247.net, or euplatform.connectwise.com depending on your region), go to Integrations → API Access → Generate API Access.Select the following scopes at minimum:
  • Devices — Read
  • Automation — Read + Create
  • Companies — Read
  • Agent — Read
  • Assets — Read
The more write scopes you grant, the wider the range of actions the agent can take. Copy the Client ID and API Key shown after generation. The API key is only displayed once.
2

Open MSP Integrations

In Rallied, go to MSP Settings → Integrations.
3

Connect ConnectWise RMM

Find the ConnectWise RMM card and click Connect. A credentials form appears.
4

Enter your credentials

Fill in:
  • Client ID — the Client ID from the Asio API Access page
  • Client Secret — the API key generated alongside the Client ID
  • Region — au (default), na, or eu, matching your ConnectWise instance
5

Save and confirm

Click Save. Rallied authenticates against the Asio OAuth2 endpoint, stores the access token, and the card shows Connected when complete.
After connecting, Rallied automatically discovers every active shell script in your ConnectWise RMM tenant and registers each one as a per-script tool. Each script gets its own policy you can tune (auto, approval-needed, never) from the integration detail page.

​
How the agent uses it

When a user asks about a server, workstation, or company managed in ConnectWise RMM (“is DC01 healthy?” or “run the disk cleanup script on Maria’s laptop”), the agent:
  1. Resolves the device by name using cw-rmm-list-devices (optionally scoped to the company).
  2. Pulls health, patch status, or system state with cw-rmm-get-device, cw-rmm-get-device-state, or cw-rmm-get-device-patches.
  3. Inspects services or resource pressure with cw-rmm-list-endpoint-services and cw-rmm-get-endpoint-usage, and checks reachability with cw-rmm-get-endpoint-heartbeat before and after taking action.
  4. If remediation is needed, picks the right shell script and schedules it on the next agent check-in via the per-script tool (e.g. cw-rmm-script-disk-cleanup).
The agent also reads and creates tickets in the same RMM tenant so it can leave a paper trail alongside automation runs.
Device and task tools call the Asio v2 API. Unlike v1, v2 returns device names directly, so the agent doesn’t have to cross-reference IDs to work out which machine a response refers to.

​
Tools

​
Static tools

​
Dynamic script tools

Every active shell script in your ConnectWise RMM tenant is also registered as its own tool named cw-rmm-script-<slug>. Each one accepts the script’s published parameters plus a list of target endpoint UUIDs (or a company ID if you set targetType: COMPANY). The agent’s policy classifier picks a default policy per script based on its name and description. You can override it from the ConnectWise RMM integration detail page.

​
Policies

Per-tool and per-script policies are configured on the ConnectWise RMM integration detail page (open it from MSP Settings → Integrations). See Approval settings for an overview.