NinjaOne tickets, opened for you when a site goes down
The SmartTile NinjaOne Ticketing integration creates the ticket on the right organization, keeps it current, and syncs your technicians’ comments both ways. Your RMM devices are never touched.
Your technicians live in NinjaOne. Network outages don’t show up there by themselves.
Today someone reads an alert and types the ticket. SmartTile opens it for you on the organization, form and location you choose, with the device, site and circuit already filled in, and keeps it current until the site is back.
What your team gets from the NinjaOne Ticketing integration
Incidents opened with the details filled in
A NinjaOne Incident at HIGH priority and MAJOR severity, with device, site and circuit details.
One ticket per outage
More devices failing at the same site add a comment to the open ticket.
Repeat outages reopen the same ticket
Within 48 hours, the last ticket reopens with a comment explaining why, so history stays together.
Internal comments by default
SmartTile and carrier updates post as internal comments signed by SmartTile. Make them public if you choose.
Comments synced both ways
Your technicians’ comments reach SmartChoice within 5 minutes, and SmartChoice’s journals come back as comments.
Ticketing only, RMM untouched
SmartTile monitors its own devices and never reads or changes your NinjaOne RMM inventory.
Where the technician’s time goes today
| The moment | Today | With SmartTile |
|---|---|---|
| A site goes down | Someone reads the alert and creates the ticket. | An Incident opens with device, site and circuit details. |
| More devices fail | Separate tickets per device. | The open ticket gets a comment naming the new devices. |
| It fails again within 48 hours | A new ticket, with history split. | The same ticket reopens with a comment. |
| Your technician comments | The NOC never sees it. | Synced to SmartChoice within 5 minutes. |
| The site comes back | Someone has to resolve it. | A restoration comment, and auto-resolve if you enable it. |
Why IT leaders add it to their stack
More from the NinjaOne you already pay for
Network outages land in the tool your technicians already use.
Public API v2, every region
Machine-to-machine or technician sign-in, across US, US2, EU, CA and OC.
Two kill switches, both off by default
Secrets are encrypted per company, and tokens go only to NinjaOne’s own domains.
No duplicates, no split history
One ticket per outage, reopened instead of recreated.
Live with one API app
- 1Create an API client appIn NinjaOne, choose API Services with Monitoring and Management scopes.
- 2Connect SmartTileEnter your region, client ID and secret, then test the connection.
- 3Pick the organization and formRead your settings and choose where tickets land.
- 4Test, then turn it onOpen a test ticket, run the Lab round-trip, and switch on Send tickets here.
Write-restricted instance? Switch to Connect NinjaOne: a technician signs in once and SmartTile keeps the refresh token.
Security and control
Learn exactly how it works
The two-page technical overview lists every NinjaOne API v2 call SmartTile makes, the default ticket settings, and how credentials and sessions are protected.
NinjaOne Ticketing integration FAQs
Will SmartTile import or change our RMM devices?
No. This is ticketing only. SmartTile monitors its own devices and never reads or changes your RMM inventory.
Our NinjaOne API is write-restricted. Will it work?
Yes. Switch to Connect NinjaOne: a technician signs in once and SmartTile keeps the refresh token.
Which NinjaOne regions are supported?
United States, US2, EU, Canada and Oceania.
Will tickets resolve themselves?
Only if you enable auto-resolve. By default, recovery adds a restoration comment and a technician resolves the ticket.
How does the NinjaOne ticketing integration avoid duplicate tickets?
New devices at the same site add a comment to the open ticket, and a site that fails again within 48 hours reopens its last ticket.
Works with the rest of your stack
The ticket your technicians would have typed is already in NinjaOne
See it in your own NinjaOne in a 30-minute demo.