ConnectWise RMM is configured in 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 scopes for the tools you want the agent to use:A missing scope doesn’t block the connection. Instead, every tool that needs that scope fails with a “client has no access” error. If you connected before, add any missing scopes to your existing API Access in ConnectWise.Automation - Create lets the agent run scripts on devices. Script runs still follow your approval policy. Copy the Client ID and API Key shown after generation. The API key is only displayed once.
2
Open Integrations
In Rallied, go to 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, oreu, 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:- Resolves the device by name using
cw-rmm-list-devices(optionally scoped to the company). - Pulls health, patch status, or system state with
cw-rmm-get-device,cw-rmm-get-device-state, orcw-rmm-get-device-patches. - Inspects services or resource pressure with
cw-rmm-list-endpoint-servicesandcw-rmm-get-endpoint-usage, and checks reachability withcw-rmm-get-endpoint-heartbeatbefore and after taking action. - If remediation is needed, picks from three options:
- An existing shell script already in your ConnectWise RMM tenant and schedules it via the dedicated per-script tool (e.g.
cw-rmm-script-disk-cleanup). - A new inline script written for the task using one of the generic runner templates (PowerShell, Bash, or Command Prompt) via
cw-rmm-run-task. - Script runs go through your configured approval policy. In a workflow, they can be set to auto-run if pre-approved.
- An existing shell script already in your ConnectWise RMM tenant and schedules it via the dedicated per-script tool (e.g.
- When a script run requires approval, the technician sees a script analysis showing the proposed script content before deciding. See Execute mode for how approval and script analysis work.
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 namedcw-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.