NinjaOne Ticketing is a beta integration. If it is not available in Settings > Integrations, contact support@msportal.ai.
This connection is separate from NinjaOne RMM. Setting up NinjaOne device sync does not enable ticketing, and this connection does not sync devices. Organizations are matched to companies separately on each connection.
Prerequisites
- NinjaOne system administrator access
- MSPortal.ai account with integration management permissions
- The URL you sign in to NinjaOne at, such as
https://app.ninjarmm.comorhttps://eu.ninjarmm.com - One NinjaOne Ticketing connection per MSPortal account. If another PSA is also connected, choose which one new tickets go to in Settings > Tickets.
Part 1: Create a NinjaOne API client
1
Open NinjaOne API settings
In NinjaOne, go to Administration > Apps > API > Client App IDs and add a client.
2
Create the application
Choose the application platform API Services (machine-to-machine) and give it a name such as “MSPortal”.
3
Grant scopes
Select the Monitoring and Management scopes, and set the allowed grant type to Client Credentials. Monitoring reads organizations. Management reads and writes tickets.
4
Copy the credentials
Copy the client ID and client secret.
Part 2: Connect NinjaOne Ticketing in MSPortal
The NinjaOne Ticketing connection page lists its tasks in the Setup guide: Connect, Permissions, Choose data, Import or match companies, Import or match users, Configure tickets and Review. Import or match users is optional.Open the connection page
1
Navigate to Integrations
In MSPortal.ai, go to Settings > Integrations.
2
Start Setup
On the Directory tab, find NinjaOne Ticketing and select Connect. If it is already connected, select Open on its row in Active to continue its tasks.
Connect
1
Enter API Credentials
Fill in the following fields:
Enter the instance address only, not a ticket link or an API path. MSPortal accepts NinjaOne’s own regional addresses.
2
Test Connection
Select Test connection to verify your credentials. A successful test does not save the connection. If you change a field after testing, select Test again.If the connection fails:
- Confirm the instance URL is the one you sign in at
- Check that the client ID and client secret are copied correctly
- Confirm the client uses API Services (machine-to-machine), the Client Credentials grant type and both the Monitoring and Management scopes
3
Save
Select Save and continue to create the connection. Credentials are stored in the vault and never shown again. Continue to Permissions.
Permissions
MSPortal checks what your NinjaOne API client is allowed to read, and shows the result for each area of data.1
Review the results
If the check has not run yet, select Run check. Each area of data is listed with its result, such as Granted, Not permitted or Could not verify.Every area is Required and must be granted before you can continue:
2
Grant anything missing
An area that is not permitted names the scope to add. Edit the client under Administration > Apps > API > Client App IDs, add the scope, then come back and select Re-check.
A Could not verify result usually means NinjaOne was slow or unavailable, so select Re-check before changing the client.
The check tests read access only. It does not prove that creating tickets, replying or changing status will succeed. Those also use the Management scope.
Choose data
Choose what to sync from NinjaOne. Changes save as you make them, and turning a dataset on starts its first sync.
Tickets sync only for organizations you have imported or matched to a company. A ticket with no organization in NinjaOne is not synced.
NinjaOne Ticketing has no opportunity, project, invoice or product sync, and does not import devices. Use NinjaOne RMM for devices.
Import or match companies
Open Import or match companies to link each NinjaOne organization to an MSPortal company. The list has Import, Suggested, Matched and Ignored views, and opens on Import, which lists organizations that are not matched yet.- Select Accept to save a suggested match, or Change to pick a different company. Accept N strong matches accepts every suggestion with 90% confidence or more after you confirm the list.
- For an unmatched organization, use Choose company… to link an existing company, or Import to create it as a new portal company.
- Use Ignore for organizations you do not want in MSPortal, and Restore to bring them back.
Import or match users
Import or match at least one company, then open Import or match users for its end users and contacts. You can leave other companies for later and return to import more users.- Select Import beside a contact, or select contacts and choose Import selected.
- In the review panel, choose the Role for the imported users and review the counts. Contacts without an email address are skipped; you can add an address before confirming.
- Confirm the import and check the result. Large selections run in batches.
A NinjaOne contact that belongs to no organization cannot be imported, because MSPortal would not know which company it belongs to.
Configure tickets
Set up how NinjaOne tickets behave in MSPortal. Each change saves straight away.1
Review new ticket defaults
New ticket defaults sets the values used for new tickets created in the portal. These are the same defaults as Settings > Tickets, and editing them requires the Ticket Settings permission.
2
Choose closed statuses
Under Ticket statuses, select the Closed statuses that mean a ticket is closed. Leave it empty to count Resolved, Closed and their custom statuses as closed. Statuses appear once the first sync has finished.
3
Place statuses in resolution stages
Resolution stages drive the visual indicator of ticket progress. Place each NinjaOne status in the stage it belongs to. A status can sit in one stage only.
Review and finish setup
Open Review and resolve any required task that is not done, then select Finish setup. Each task saves its own changes, so finishing setup does not apply a separate batch of pending imports.Finishing setup does not mean every sync has completed. Check Sync activity before treating an empty list as final.
Working with NinjaOne tickets
- Authors: NinjaOne records comments added through its API under the API client, so MSPortal puts the name of the person who wrote the reply at the top of the comment.
- Time: MSPortal shows the time NinjaOne has tracked on a ticket, but does not log time to NinjaOne.
- Attachments: files are not sent to or read from NinjaOne.
- Ticket forms: a ticket’s form is shown as its category. NinjaOne boards are saved views rather than queues, so MSPortal does not use them.
- Deleted tickets: a ticket deleted in NinjaOne is removed from MSPortal on the next sync.
Managing Your Integration
Open the connection from Settings > Integrations > Active. Then use:- Overview and Sync activity: Check the connection’s status and recent sync runs
- Run sync: Start a sync of All data or one dataset
- Choose data, Import or match companies and Import or match users: Change what syncs and import more records at any time
- More actions > Rename: Give the connection a nickname
- More actions > Disconnect…: Removes the stored credentials, the matches between NinjaOne organizations and your companies, and data synced from this connection. It does not revoke the API client in NinjaOne
Replacing your API client
In Connect, leave the masked credentials unchanged to keep them, or enter replacements, select Test connection and then Save changes. A test alone does not save replacement credentials. Confirm the saved connection works before you remove the old client in NinjaOne.Synchronization Process
- Turning a dataset on in Choose data starts its first sync
- New and changed tickets sync every five minutes; organizations and users every four hours; statuses daily
- The first ticket sync reads your ticket history and can take a while on a large account
- Contacts and tickets for an organization appear once that organization is imported or matched
Troubleshooting
Related Resources
NinjaOne RMM
Configure device synchronization from NinjaOne
Integrations Overview
Manage all MSPortal integrations