Connect NinjaOne
NinjaOne uses OAuth with an app you create in your own NinjaOne account. There’s no shared vendor app to consent to.1
Create an API app in NinjaOne
Sign in to NinjaOne as an administrator, go to Administration → Apps → API, and add a client app.
Save the app and copy the Client ID and Client Secret. NinjaOne shows the secret only once.
2
Paste the credentials into Rallied
In Rallied, go to Settings → Integrations, find the NinjaOne card, and click Connect.
Click Connect.
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 NinjaOne stops accepting it, for example because someone revoked the API app, click Reauthorize on the NinjaOne detail page and approve the app again.If you rotate the client secret, update the connection with the new secret. Rallied opens the authorization popup afterwards if NinjaOne needs a fresh approval.Both options keep your approval settings and synced clients.
Library scripts and built-in actions
The agent can run two kinds of automation on a device:
The agent checks what’s available on the device before running anything. It identifies each entry by ID, not 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 run as scripts through the API, so the agent runs the built-in action instead. Your own custom library scripts run normally.
- Restarting a service works only on Windows devices. NinjaOne rejects the request on Linux and macOS.
- The one-click reboot works on Windows and macOS. The agent reboots Linux devices through the built-in Reboot action instead. It checks the OS and picks the right action.
Tickets
The agent can open and update NinjaOne tickets to record its device work.- When it creates a ticket, it can set the type, priority and severity, and link the ticket to a device. Without a specified form, NinjaOne uses the organization’s default form or the first active one.
- When it updates a ticket’s status, priority or subject, everything else on the ticket stays the same. NinjaOne’s API replaces the whole ticket on update, so Rallied fetches the current ticket first and re-sends it with only the changes.
Running custom bash scripts (Linux and macOS)
NinjaOne runs only scripts that already exist in your script library. To let the agent run ad-hoc bash on Linux or macOS endpoints, set up a one-time bridge script and paste its ID into Rallied.1
Create the bash runner script in NinjaOne
In NinjaOne, create a new Mac/Linux script with:Save it and copy the numeric Script ID from the details page.
- One String parameter
- This body:
2
Paste the Script ID into Rallied
In Rallied, open Settings → Integrations → NinjaOne and find the Bash Runner Script section. Paste the Script ID and click Save.
Default approval settings
You can change each default on the NinjaOne Policies tab under Settings → Integrations.Related
- Approval settings for how Auto, Approval needed and Disabled work
- Execute Mode for how approvals play out once a client is live
- Workflows to tell the agent how to handle common requests
- Integrations to update credentials or sync companies