> ## Documentation Index
> Fetch the complete documentation index at: https://kb.mspprocess.com/llms.txt
> Use this file to discover all available pages before exploring further.

# NinjaOne

> Connect NinjaOne to Triggr with an API Services (machine-to-machine) client app.

Triggr works with NinjaOne organisations, locations, devices, patches, scripts, users, tickets and documentation. Triggr connects to NinjaOne at `app.ninjarmm.com`.

## Set up NinjaOne

**1. Add a client app**

In NinjaOne, go to **Administration > Apps > API**, open Client App IDs and click Add. Set Application Platform to **API Services (machine-to-machine)** and Name to `Triggr`, and leave Redirect URIs empty.

**2. Choose scopes and grant type**

Under Scopes, tick Monitoring (read-only) and Management (changing devices and organisations, and running scripts); add Control only for remote access. Under Allowed Grant Types, tick **Client Credentials**.

**3. Copy the credentials**

Save the app and copy the client secret from the confirmation dialog, the only place NinjaOne shows it. Then copy the Client ID from Client App IDs.

See NinjaOne's [Register Machine-to-Machine Applications](https://app.ninjarmm.com/apidocs-beta/authorization/create-applications/machine-to-machine-apps).

## Connect it in Triggr

**1. Open the integration**

Go to **Integrations > NinjaOne 2.0** and click Configure on the Base Configuration card.

![The Base Configuration card with Status Not Configured, Admin Consent Not Required and a Configure button.](https://mintcdn.com/triggr/nyuVXZ1rouDTTEvu/images/integrations-common/base-configuration.png?fit=max\&auto=format\&n=nyuVXZ1rouDTTEvu\&q=85\&s=bb81acb082055015f91beda7b4876f35)

**2. Enter the app**

Enter the ClientID and ClientSecret, and the scopes you ticked in Scopes, in lower case and separated by spaces (for example `monitoring management`), then click Save Configuration.

![The NinjaOne 2.0 configuration window with ClientID, ClientSecret and Scopes fields, an Allow insecure TLS switch under Advanced, and a Save Configuration button.](https://mintcdn.com/triggr/nyuVXZ1rouDTTEvu/images/ninjaone/configure.png?fit=max\&auto=format\&n=nyuVXZ1rouDTTEvu\&q=85\&s=7b93793f331eb5b8ff5419a05d306fb1)

One app covers every NinjaOne organisation. Actions take the ID of the organisation, location or device they work on.

## Troubleshooting

> [accordion] Every action fails
>
> Often with `no access token in response`. Check ClientID and ClientSecret have no extra spaces, the app still has Client Credentials ticked, Scopes uses spaces (not commas) and only `monitoring`, `management` or `control`, and the app was created in the NinjaOne account you sign in to at `app.ninjarmm.com`.

> [accordion] Read actions work but changes fail
>
> Tick Management on the app in NinjaOne, then add `management` to Scopes in Triggr.

> [accordion] The client secret was lost
>
> Create a new client app, enter its details with Edit on the Base Configuration card, then delete the old app.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.