Connect NinjaOne
Keel reads the status of the NinjaOne tickets linked to a person’s onboarding or offboarding once a day. The status shows in the Tickets panel on the person’s page, and the Leaver tickets resolved within 7 days check looks at every offboarding ticket. Linking tickets is described in Onboarding records.
Keel signs in with a client ID and secret, sends only read requests for tickets, only to the instance you connect, and stores the secret encrypted.
The NinjaOne connection is in preview. It was built from NinjaOne’s published API description and is still being tested against live instances.
Time: about 5 minutes.
Before you start
Section titled “Before you start”- In NinjaOne: you are a system administrator, so you can create API applications.
- In Keel: you are an owner or admin of the workspace.
Create the API application
Section titled “Create the API application”- In NinjaOne, open Administration > Apps > API, then Client App IDs.
- Click Add.
- Application platform: API Services (machine-to-machine).
- Name:
keel-evidence. - Scopes: tick Monitoring. If tickets later show as unreadable with HTTP 403, edit the application and also tick Management; Keel still sends only read requests.
- Allowed grant types: tick Client Credentials.
- Click Save, then copy the Client ID and Client secret. NinjaOne shows the secret only once.
Connect it in Keel
Section titled “Connect it in Keel”- In Keel, open Integrations, find the NinjaOne card and click Connect.
- Under Credentials, fill in:
- Instance: the address you sign in at, for example
app.ninjarmm.comoreu.ninjarmm.com. - Client ID and Client secret: the values you copied.
- Instance: the address you sign in at, for example
- Click Save connection.
Evidence connector connected. Its credential is stored encrypted. means it worked.
See the first findings
Section titled “See the first findings”Open the Findings tab and click Collect now, or wait for the next daily run.
- An offboarding ticket passes when it was resolved or closed within 7 days of its creation, or when it is still open and inside those 7 days.
- NinjaOne does not report when a ticket was resolved. Keel records the date of the first daily check that finds it resolved after an earlier check found it open. A ticket that was already resolved when Keel first read it shows Resolved; NinjaOne did not report when.
- It fails when it was resolved later, or is still open after 7 days.
To leave a person out of the check, put them out of scope from Affected items.
Troubleshooting
Section titled “Troubleshooting”| What you see | What to do |
|---|---|
| Check the connection details and try again. | The instance, client ID or secret is wrong, or Client Credentials is not an allowed grant type. Check each and connect again. |
| A ticket shows Could not read the ticket (HTTP 403) | Add the Management scope to the application, as in step 5. |
Rotate or remove access
Section titled “Rotate or remove access”- Rotate: create a new application, disconnect and reconnect in Keel, then delete the old one.
- Remove: click Disconnect in Keel, then delete the application in NinjaOne.