Integrations # AI for NinjaOne NinjaOne already knows every device, alert, patch, script and installed app at every client. Connected to Control Center, that data runs automations, morning standards checks, client reports, and answers your team gets in Claude or ChatGPT. - 9 automations - 9 standards - 6 reports - 11 MCP questions ## Automations with NinjaOne Work that runs on its own, across your tools. A person approves the steps that matter. - ### Alerts become one ticket, with the fix attached NinjaOne alerts are grouped and duplicates dropped. One ConnectWise PSA ticket opens with the device, the user and the fix from IT Glue. With ConnectWise 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 NinjaOne, and the time lands on the ConnectWise PSA ticket. With ConnectWise PSA and IT Glue - ### Failed backups handled overnight When a Datto BCDR job fails, a ConnectWise PSA ticket opens with the error, the last good backup and the device’s health from NinjaOne. With Datto BCDR and ConnectWise PSA - ### Documentation that updates itself Devices from NinjaOne 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 ConnectWise PSA gets a checklist that tracks NinjaOne agents, SentinelOne coverage and Datto BCDR jobs until every device is done. With ConnectWise PSA, SentinelOne and Datto BCDR - ### Full disks cleaned up before anyone calls When NinjaOne flags a disk filling up, the cleanup script your team approved runs. A ConnectWise PSA ticket opens only if that doesn’t fix it. With ConnectWise PSA - ### Failed patches retried, then explained Devices that fail patching in NinjaOne get another try in the next window. If one fails again, a ConnectWise PSA ticket opens with the error and the device’s history. With ConnectWise PSA - ### Software requests installed on approval A software request in ConnectWise PSA installs through NinjaOne once a tech approves it, and the ticket closes with what was installed. With ConnectWise PSA - ### New devices set up to your standard When a new device checks in to NinjaOne, your baseline scripts run and the device is documented in IT Glue. With IT Glue ## Standards checked in NinjaOne Checked every morning, for every client. Fewer tickets, better security, and every gap is a project you can sell. - ### SentinelOne on every device Devices in NinjaOne without a healthy SentinelOne agent become a ticket. With SentinelOne - ### Patches inside your window Every device in NinjaOne, against the patch window you set. - ### Supported operating systems only Devices in NinjaOne on Windows or macOS versions past end of support. - ### Every server backed up Servers in NinjaOne with no Datto BCDR backup, or none that finished in the last 24 hours. With Datto BCDR - ### No stale devices or accounts Devices in NinjaOne that haven’t checked in for 30 days, and Microsoft 365 accounts unused for 90. With Microsoft 365 - ### Only approved software Software in NinjaOne’s inventory, checked against each client’s approved list. - ### No unapproved remote access tools Remote access software in NinjaOne’s inventory that isn’t on your approved list, at every client. - ### Every device has an owner Devices in NinjaOne that aren’t matched to a person in Microsoft 365. With Microsoft 365 - ### Every device documented Devices in NinjaOne that are missing from IT Glue. With IT Glue ## Reports from NinjaOne Numbers from your tools, in the client’s language. Build a report from any data you connect. - ### The whole QBR, drafted ConnectWise PSA, NinjaOne, SentinelOne and Datto BCDR in one QBR, written in the client’s business terms for your vCIO to approve. With ConnectWise PSA, SentinelOne and Datto BCDR - ### Patch compliance From NinjaOne, per device and per site. - ### Devices by age and operating system From NinjaOne, per client and per site, with the devices due for replacement. - ### Software inventory From NinjaOne, with unapproved software called out. - ### Alerts and what they cost Alert volume from NinjaOne per client, with the ConnectWise PSA time spent on them. For you, not the client. With ConnectWise PSA - ### A one-page monthly summary Tickets, devices, security and AI work from ConnectWise PSA and NinjaOne, on one page for the client’s owner. With ConnectWise PSA ## Ask about NinjaOne 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 SentinelOne?” Answered from NinjaOne and SentinelOne. - ### “What did we do for Meridian this month?” Answered from ConnectWise PSA and NinjaOne. - ### “Why does Harbor’s file server keep alerting?” Answered from NinjaOne alerts and ConnectWise PSA history. - ### “What changed at Northbridge this week?” Answered from ConnectWise PSA, NinjaOne and SentinelOne. - ### “Which servers at Northwind are low on disk space?” Answered from NinjaOne. - ### “Which patches failed at Meridian last night?” Answered from NinjaOne. - ### “Which computers still have the old VPN client?” Answered from NinjaOne’s software inventory. - ### “Which devices haven’t checked in this week?” Answered from NinjaOne. - ### “What can Sam at Northwind access, and which laptop is theirs?” Answered from Microsoft 365 and NinjaOne. - ### “Draft Northbridge’s QBR.” Built from ConnectWise PSA, NinjaOne and every other connected tool, for your vCIO to edit. - ### “Clean up the disk on Harbor’s file server.” Drafted as a NinjaOne script that a tech approves before it runs. ## What Control Center reads from NinjaOne Devices, alerts, patching, scripts and software inventory. Control Center connects to NinjaOne 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. The examples on this page use a typical MSP stack: ConnectWise PSA, IT Glue, Datto BCDR, Microsoft 365 and SentinelOne. Build your AI plan to see them with your own tools. [Connection details and what you need from NinjaOne](https://www.resultsiq.ai/docs/tools/ninja/) ## Questions about NinjaOne and Control Center ### Does Control Center work with NinjaOne? Yes. Control Center connects to NinjaOne 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 NinjaOne and AI? With Control Center, 9 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 NinjaOne with Claude or ChatGPT? Yes, through Control Center MCP. Your team connects Claude or ChatGPT once and can ask about NinjaOne at every client, with the same roles and client scopes as their login. For example: “Which devices at Northbridge don’t have SentinelOne?” ### 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.