NinjaOne Ticketing is currently a pilot integration, marked Credential intake on its setup page. The pilot establishes and validates the API connection; ticket synchronization and reporting features build on this connection as they become available. No tickets are imported yet. If the integration 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.
Prerequisites
- NinjaOne administrator access
- MSPortal.ai integration management permission
- The URL of your NinjaOne instance
Create a NinjaOne API Client
1
Open NinjaOne API settings
In NinjaOne, go to Administration > Apps > API.
2
Create the application
Create an API Services (machine-to-machine) application. Enable the Client Credentials grant type and the required Monitoring and Management scopes.
3
Copy the credentials
Copy the client ID and client secret, and note the HTTPS URL you use to access your NinjaOne instance.
Connect in MSPortal
1
Open the setup page
In MSPortal, go to Settings > Integrations, find NinjaOne Ticketing, and click Connect.
2
Enter the connection details
Enter the Instance URL, Client ID, and Client Secret.Use the HTTPS URL of your NinjaOne instance, not a ticket link or an API path.
3
Test the connection
Click Test Connection. MSPortal verifies the API client and reports the ticket boards it can access when available. This is a connection check, not a ticket import.
4
Save the connection
Click Secure credentials after the test succeeds. The client credentials are stored securely in Vault. A successful test alone does not save them.
Managing the Connection
1
Reopen the connection
Go to Settings > Integrations and click Configure on the NinjaOne Ticketing connection. Saved credentials appear masked.
2
Retest or replace credentials
To check access, click Retest Connection. To replace credentials, enter the new values, click Retest Connection, then click Update credentials. Changing any field clears the earlier test, and retesting alone does not save replacements.
3
Disconnect (optional)
Click Disconnect and confirm. This removes the MSPortal connection and its stored Vault credentials. It does not change or revoke the NinjaOne application.
Troubleshooting
Related Resources
NinjaOne RMM
Configure device synchronization from NinjaOne
Integrations Overview
Manage all MSPortal integrations