Integrations # AI for Kaseya VSA Kaseya VSA already manages every device, alert, patch, script and installed app across your clients. Connected to Control Center, alerts become one ticket with the fix attached, your standards are checked every morning, and your team can ask about any device in Claude or ChatGPT. - 10 automations - 9 standards - 6 reports - 11 MCP questions ## Automations with Kaseya VSA Work that runs on its own, across your tools. A person approves the steps that matter. - ### Alerts become one ticket, with the fix attached Kaseya VSA alerts are grouped and duplicates dropped. One Autotask ticket opens with the device, the user and the fix from IT Glue. With Autotask PSA and IT Glue - ### Known fixes run when a tech approves For a repeat issue, the fix your team wrote in IT Glue runs through Kaseya VSA, and the time lands on the Autotask ticket. With Autotask PSA and IT Glue - ### Failed backups handled overnight When a Datto BCDR job fails, a Autotask ticket opens with the error, the last good backup and the device’s health from Kaseya VSA. With Datto BCDR and Autotask PSA - ### Documentation that updates itself Devices from Kaseya VSA and users from Microsoft 365 sync into IT Glue every night, with changes flagged. With IT Glue and Microsoft 365 - ### New clients onboarded on rails A new client in Autotask gets a checklist that tracks Kaseya VSA agents, Datto EDR coverage and Datto BCDR jobs until every device is done. With Autotask PSA, Datto EDR and Datto BCDR - ### Full disks cleaned up before anyone calls When Kaseya VSA flags a disk filling up, the cleanup script your team approved runs. A Autotask ticket opens only if that doesn’t fix it. With Autotask PSA - ### Failed patches retried, then explained Devices that fail patching in Kaseya VSA get another try in the next window. If one fails again, a Autotask ticket opens with the error and the device’s history. With Autotask PSA - ### Software requests installed on approval A software request in Autotask installs through Kaseya VSA once a tech approves it, and the ticket closes with what was installed. With Autotask PSA - ### New devices set up to your standard When a new device checks in to Kaseya VSA, your baseline scripts run and the device is documented in IT Glue. With IT Glue - ### Broken agents reinstalled When an Datto EDR agent stops reporting, Kaseya VSA reinstalls it with your script once a tech approves. With Datto EDR ## Standards checked in Kaseya VSA Checked every morning, for every client. Fewer tickets, better security, and every gap is a project you can sell. - ### Datto EDR on every device Devices in Kaseya VSA without a healthy Datto EDR agent become a ticket. With Datto EDR - ### Patches inside your window Every device in Kaseya VSA, against the patch window you set. - ### Supported operating systems only Devices in Kaseya VSA on Windows or macOS versions past end of support. - ### Every server backed up Servers in Kaseya VSA with no Datto BCDR backup, or none that finished in the last 24 hours. With Datto BCDR - ### No stale devices or accounts Devices in Kaseya VSA that haven’t checked in for 30 days, and Microsoft 365 accounts unused for 90. With Microsoft 365 - ### Only approved software Software in Kaseya VSA’s inventory, checked against each client’s approved list. - ### No unapproved remote access tools Remote access software in Kaseya VSA’s inventory that isn’t on your approved list, at every client. - ### Every device has an owner Devices in Kaseya VSA that aren’t matched to a person in Microsoft 365. With Microsoft 365 - ### Every device documented Devices in Kaseya VSA that are missing from IT Glue. With IT Glue ## Reports from Kaseya VSA Numbers from your tools, in the client’s language. Build a report from any data you connect. - ### The whole QBR, drafted Autotask, Kaseya VSA, Datto EDR and Datto BCDR in one QBR, written in the client’s business terms for your vCIO to approve. With Autotask PSA, Datto EDR and Datto BCDR - ### Patch compliance From Kaseya VSA, per device and per site. - ### Devices by age and operating system From Kaseya VSA, per client and per site, with the devices due for replacement. - ### Software inventory From Kaseya VSA, with unapproved software called out. - ### Alerts and what they cost Alert volume from Kaseya VSA per client, with the Autotask time spent on them. For you, not the client. With Autotask PSA - ### A one-page monthly summary Tickets, devices, security and AI work from Autotask and Kaseya VSA, on one page for the client’s owner. With Autotask PSA ## Ask about Kaseya VSA in Claude or ChatGPT Questions your team asks in Claude or ChatGPT, answered from every tool and client. Any answer can become a report or an automation. - ### “Which devices at Northbridge don’t have Datto EDR?” Answered from Kaseya VSA and Datto EDR. - ### “What did we do for Meridian this month?” Answered from Autotask and Kaseya VSA. - ### “Why does Harbor’s file server keep alerting?” Answered from Kaseya VSA alerts and Autotask history. - ### “What changed at Northbridge this week?” Answered from Autotask, Kaseya VSA and Datto EDR. - ### “Which servers at Northwind are low on disk space?” Answered from Kaseya VSA. - ### “Which patches failed at Meridian last night?” Answered from Kaseya VSA. - ### “Which computers still have the old VPN client?” Answered from Kaseya VSA’s software inventory. - ### “Which devices haven’t checked in this week?” Answered from Kaseya VSA. - ### “What can Sam at Northwind access, and which laptop is theirs?” Answered from Microsoft 365 and Kaseya VSA. - ### “Draft Northbridge’s QBR.” Built from Autotask, Kaseya VSA and every other connected tool, for your vCIO to edit. - ### “Clean up the disk on Harbor’s file server.” Drafted as a Kaseya VSA script that a tech approves before it runs. ## What Control Center reads from Kaseya VSA Devices, alerts, patching, scripts and software inventory. Control Center connects to Kaseya VSA through its public API. You add it once, then choose which clients it covers and which API operations it can use. The key goes in Control Center’s vault, never in a chat. What you need: An administrator creates an API token. Requests go to your own VSA server address. The examples on this page use a stack MSPs often run with Kaseya VSA: Autotask PSA, IT Glue, Datto BCDR, Microsoft 365 and Datto EDR. Build your AI plan to see them with your own tools. [Connection details and what you need from Kaseya VSA](https://www.resultsiq.ai/docs/tools/vsa/) ## Questions about Kaseya VSA and Control Center ### Does Control Center work with Kaseya VSA? Yes. Control Center connects to Kaseya VSA through its public API and uses devices, alerts, patching, scripts and software inventory. You add it once, then choose which clients it covers. ### What can an MSP automate with Kaseya VSA and AI? With Control Center, 10 automations, including: alerts become one ticket, with the fix attached; known fixes run when a tech approves; failed backups handled overnight; documentation that updates itself; new clients onboarded on rails; full disks cleaned up before anyone calls. A person approves the steps that matter. ### Can I use Kaseya VSA with Claude or ChatGPT? Yes, through Control Center MCP. Your team connects Claude or ChatGPT once and can ask about Kaseya VSA at every client, with the same roles and client scopes as their login. For example: “Which devices at Northbridge don’t have Datto EDR?” ### What does it cost? $1,750 a month for the Control Center platform plus $75 a month per billable workflow, with the first 90 days at no cost. ## Related integrations [AI for NinjaOne](https://www.resultsiq.ai/integrations/ninjaone/) [AI for Datto RMM](https://www.resultsiq.ai/integrations/datto-rmm/) [AI for N-able N-central](https://www.resultsiq.ai/integrations/n-able-n-central/)