ConnectWise Asio
Endpoints, policies, and the automation around them — your Asio estate, answerable.
ConnectWise RMM on the Asio platform watches your modern endpoint fleet. Connect it and a session reads the estate live — who's offline, what's installed, what's unpatched, what's exposed — plus the policy machinery behind it: which package applies where, what the effective policy on any one endpoint really is, and what the automation actually did on its last run. Forty-five capabilities, every one of them a read.
The story
What changes once it’s connected.
Asio holds the answer to most endpoint questions already. The cost is the getting there: a console, the right view, the right filter, and the knowledge of which of the platform's two id spaces the thing you're looking at lives in. Connect ConnectWise RMM here and the estate answers in plain English instead — offline endpoints by site, logged-on users and last boot, live CPU and memory and disk, installed applications across a whole company, patch state and CVE exposure per device.
The policy side comes with it, which is the part that usually takes a colleague. Policies and their settings, packages and where they're assigned, the policy-group hierarchy and its criteria, and the effective policy that an individual endpoint ends up running once all of that resolves — including the override document when someone left one in place. Alongside it: automation tasks with their run history and per-endpoint results, the fusion and shell script catalogues, device groups and their membership, the service ticket queue with its notes, and the alert-suspension rules that explain a quiet night before you call it a monitoring gap.
Nothing here writes. The client has no write method, and the tool registry can only express a read scope, so the boundary is structural rather than a permission someone could widen. It cannot run or schedule an automation task or a script, open or change a ticket, edit a policy, or create, extend, or lift a suspension — those tools were deliberately never built.
Things you can ask
Ask it like you’d ask a teammate.
Skills included
Every skill, in the open.
45 skills across 8 areas
Read-only by construction — the client has no write method and the tool registry cannot express a write scope. It cannot run or schedule an automation task or script, create or change a ticket, edit a policy, or create, extend, or lift an alert suspension.
Devices & endpoints12Find endpoints and read their detail — online state and last-seen, system info, live CPU/memory/disk, services, installed applications, patch state, and CVE exposure.⊘ Reads device state only — no reboot, no patch approval or deployment, no service start or stop.›
list_endpointsThe endpoint inventory grouped by company and site — device names and the ids every other device question needs.get_endpointFull system information for one endpoint, rather than the trimmed list row.endpoint_heartbeatOnline, offline, and last-seen — for whole companies, whole sites, or a named batch of endpoints in one call.endpoint_system_stateWho is logged on to a machine now, who was last, and when it last booted.endpoint_performanceCurrent CPU, memory, and disk pressure on one endpoint — needs the performance read scope, and comes back empty where no recent sample has landed.endpoint_servicesThe services and daemons on one machine, with a name filter for checking whether a specific one is there.unique_servicesEvery distinct service seen across the monitored fleet — the vocabulary before you go hunting for one.endpoint_applicationsInstalled applications across a company, a site, or a single endpoint, filterable by name and version.endpoint_patchesOne endpoint's patches with their KBs and install state — requires the patching read scope on the credential, or the tenant is refused.endpoint_vulnerabilitiesCVE exposure for a batch of endpoints, looked up in a single pass.hypervisor_hostsThe VMware vCenter and ESXi hosts under monitoring; a tenant that monitors no VMware simply has none.map_idsTranslate between Asio's two id spaces, public and private — how a lookup that came back empty gets retried correctly.
Policies9Policies, packages, and policy groups — including the effective policy actually applied to any given endpoint.⊘ Reads policy configuration only — it cannot edit a policy, assign a package, or change a group's criteria.›
list_policiesEvery policy available to the partner, filed by category and subcategory.get_policyOne policy opened out to its settings — the configured values, domain by domain, not just the name.policy_assignmentsWhere a policy actually lands: the packages and groups carrying it.list_packagesThe policy packages, including which one is default and which clients and sites each is assigned to.get_packageOne package and its assignments together — the definition and its reach in a single answer.list_policy_groupsThe policy-group hierarchy, parents and children in evaluation order.get_policy_groupA single group's criteria, the device group behind it, and the policy attached.effective_policyWhat one endpoint is really running once everything above it resolves — with the override document when someone left one in place.policy_categoriesThe categories and subcategories policies are organized under.
Automation7Automation tasks with their run history and per-endpoint results, plus the fusion and shell script catalogues.⊘ Catalogue and results only — there is no execute path, so it cannot run, queue, or schedule a task or script.›
list_automation_tasksEvery automation task defined for the partner — the catalogue, not a run button.tasks_summaryAutomation in aggregate: how many tasks exist and what state they're sitting in.task_instance_summaryOne task's run history — each execution and how it came out.task_instance_resultsA single run broken out machine by machine — which endpoints it worked on and which it didn't.endpoint_task_summaryThe automation that has touched one machine, as its own Automation tab shows it.list_scriptsThe fusion script catalogue from the Script Editor — what exists, read only.list_shell_scriptsThe shell scripts on the shelf, listed the same way.
Companies & sites5Companies and the sites beneath them — the shape of who you manage.›
list_companiesThe client list as Asio holds it — every company under your partner account.get_companyOne company's record in full.company_sitesThe sites under a single company — that client's offices and locations.list_sitesEvery site across every client at once, for when the question is about locations rather than companies.get_siteA single site's detail record.
Ticketing5Search service tickets, read their detail and notes, count them, and pull boards, statuses, and priorities.⊘ Read-only — the create, update, and note-writing endpoints are unreachable, so nothing here can open, change, or close a ticket.›
search_ticketsSearch the service queue by status, priority, or company, with the matching total alongside.get_ticketOne ticket's complete record.ticket_notesThe notes written on a ticket — the conversation behind the status.ticket_countsThe queue by the numbers for the partner as a whole.ticketing_referenceBoards, statuses, priorities, types, and sources in one call — the vocabulary the queue is described in.
Device groups3Device groups, their endpoint membership, and which groups a given endpoint belongs to.›
list_device_groupsEvery device group, and whether it is static, predefined, or dynamic.group_endpointsThe endpoints inside one group — worth knowing a group can span more than one company.endpoint_groupsThe reverse lookup: which groups a given endpoint has ended up in.
Alert suspensions2Alert-suspension rules — what's silenced, where, and until when.⊘ Reads the rules only — it cannot create, extend, or lift a suspension, or silence an alert itself.›
list_suspensionsEvery alert-suspension rule, and whether it is still active or has expired.get_suspensionOne rule in detail — what it silences, across which clients, sites, endpoints, or groups, and on what schedule.
Identity & limits2Who the session is signed in as, and the current API rate-limit state.›
rate_limitsThe token's live rate-limit state — the number to check before a fleet-wide sweep, since the published limits contradict each other.whoamiWhich Asio identity this connection uses, the scopes it holds, and whether its token is still good.
Connecting
Wire it in, in an afternoon.
How to connect
- 01Create OAuth client credentials for the Asio platform API in your ConnectWise partner account.
- 02Note the client id — its prefix picks your region automatically, so there's nothing to choose.
- 03Paste the client id and secret here; the token refreshes itself from then on.
Patch your stack in.
Start the Switchboard free trial against your own environment — read-only, traced answers, live in an afternoon. The apps are on the shelf when you want them.