Skip to main content
Connect NinjaOne and Rallied’s agents can look at any managed device across all your organizations, figure out what’s going on, and take action: restart a stuck service, reboot a kiosk, run one of your library scripts against a whole customer, close out the alert, open a ticket. Your techs stop clicking through 30 screens to answer “is the print server up?” and start reviewing what the agent already found. Concrete wins after you connect:
  • Alerts triaged before your tech opens the ticket. When a NinjaOne alert fires, the agent already knows what device, what software, what recent activity, and what to try first.
  • Remediation without a swivel chair. The agent runs your existing NinjaOne library scripts on the right devices — no clicking through NinjaOne to launch them one at a time.
  • You always sign off on writes. Anything that changes state on a device (rebooting, running a script, dismissing an alert) needs technician approval by default. The agent shows exactly what it wants to do first.
NinjaOne is configured in MSP Settings → Integrations.

​
Connect NinjaOne

You’ll create an API app inside NinjaOne, paste the credentials into Rallied, and authorize the app in a NinjaOne consent popup. NinjaOne uses OAuth with a per-MSP app, so there’s no shared vendor app to consent to.
1

Create an API app in NinjaOne

Sign in to NinjaOne as an administrator and go to Administration → Apps → API → Add. Create a new app with:
  • Application platform — Web
  • Redirect URI — the callback URL shown on the Rallied connect form
  • Scopes — monitoring, management, control
Save the app and copy the Client ID and Client Secret. The secret is only shown once.
2

Paste the credentials into Rallied

In Rallied, go to MSP Settings → Integrations, find the NinjaOne card, and click Connect. Fill in:
  • Client ID and Client Secret from your NinjaOne API app
  • Region — the NinjaOne instance your tenant lives on (app.ninjarmm.com, us2.ninjarmm.com, eu.ninjarmm.com, oc.ninjarmm.com, or ca.ninjarmm.com)
Click Save.
3

Authorize the app

A popup opens against NinjaOne. Sign in if prompted and approve the requested scopes. Once NinjaOne redirects back, the card shows Connected.
Rallied refreshes the access token automatically. If someone revokes the API app in NinjaOne or rotates the client secret, the card will show as disconnected. Reconnect from MSP Settings → Integrations.

​
What the agent can do

The agent can read from any managed device — recent activity, installed software, running services, disks, volumes, alerts — without asking. For anything that changes state on a device it stops and asks for technician approval by default: restarting a service, rebooting a device, running a script, dismissing an alert, or updating a ticket. So a typical flow after an alert or a user request looks like: the agent identifies the right organization and device, gathers the context your tech would have collected anyway, drafts a plan, and either resolves it or hands you a one-click approval to run the fix.

​
Library scripts and built-in actions

The agent can run two kinds of automation on a device:
  • Library scripts — the custom scripts your admins have added under Administration → Library → Automation in NinjaOne.
  • Built-in actions — the actions NinjaOne ships with, like Reboot or Flush DNS.
The agent always checks what’s available on the device before running anything, and it identifies each entry by its ID rather than its name, so a renamed script never runs the wrong thing.
NinjaOne’s script library also lists “native” entries that sit behind the built-in actions. Those entries can’t be run as scripts through the API — they fail every time. The agent knows this and runs the built-in action itself instead. Your own custom library scripts run fine.
A few actions are OS-specific:
  • Restarting a service only works on Windows devices — Linux and macOS don’t have Windows services, and NinjaOne rejects the request on those platforms.
  • The one-click reboot works on Windows and macOS. Linux devices are rebooted through the built-in Reboot action instead; the agent checks the device’s OS first and picks the right route on its own.

​
Tickets

The agent can open and update NinjaOne tickets to leave a paper trail next to its device work:
  • When creating a ticket, it can set the type, priority, and severity, and link the ticket to a specific device. If it doesn’t specify a ticket form, the organization’s default form (or the first active one) is used.
  • When updating a ticket’s status, priority, or subject, everything else on the ticket is preserved. NinjaOne’s API replaces the whole ticket on update, so Rallied fetches the current ticket first and re-sends it with only the changes applied.

​
Running custom bash scripts (Linux and macOS)

Out of the box NinjaOne only lets you run scripts that already exist in your script library. If you want the agent to run ad-hoc bash on Linux or macOS endpoints (one-liners a tech would normally SSH in to run), set up a one-time bridge script and paste its ID into the NinjaOne integration page.
1

Create the bash runner script in NinjaOne

In NinjaOne, create a new Mac/Linux script with:
  • One String parameter
  • Body — echo "$1" | base64 --decode | bash
Save it and copy the numeric Script ID from the details page.
2

Paste the Script ID into Rallied

In Rallied, open MSP Settings → Integrations → NinjaOne and find the Bash Runner Script section. Paste the Script ID and click Save.
Once configured, the agent can run any custom bash on Linux or macOS devices through this bridge. To turn it off later, clear the Script ID field and save. Bash runs are asynchronous: NinjaOne doesn’t return the output directly. The agent reads the result from the device’s activity feed once the device reports back, usually within 10–30 seconds.
Custom bash runs as root by default, which makes it the highest-risk action in the integration. It always requires technician approval, and the exact script the agent wants to run is shown in the approval request. Review it before approving.
The bash runner is Linux and macOS only. For Windows devices, the agent uses your existing NinjaOne library scripts and built-in actions.

​
Approval settings

You control which NinjaOne actions the agent takes on its own vs. which need a technician sign-off, on the NinjaOne page under MSP Settings → Integrations. Defaults are read-freely, ask-for-writes:
  • Auto-approve — listing and inspecting devices, organizations, disks, volumes, software, services, activity, alerts, and scripts. Creating tickets. Reading ticket logs.
  • Needs approval — starting/stopping/restarting a service, rebooting a device, running a library script or ad-hoc bash, dismissing an alert, updating a ticket, and any generic write against the NinjaOne API.
See Approval settings for the bigger picture.